This is an automated email from the git hooks/post-receive script.

tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 in repository toolchain/ci/base-artifacts.

discards 7d60283e7 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/gd [...] discards 8913edfb8 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards e1ed18bc3 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gdb [...] discards 6014d1d83 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 6c474ef2e 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards c20b8f97e 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 0dc503788 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 8b019f700 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards b13ded5db 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 1607bbf39 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards deb635068 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 1b9f572d6 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 0dad3734f 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards fb385ee87 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 97a616627 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 6e9ec34f7 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards b4a6dbf8f 84: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 446cee3f8 83: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 6e3c7e0dc 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards f48fb3bfb 81: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 4059c6a96 80: onsuccess: 7: Successful build after linux: 44 commits discards 03af0b178 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards d4403b4b9 78: onsuccess: 7: Successful build after gcc: rs6000: Allow c [...] discards df35b7692 77: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards d9b78f164 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards 4faf04066 75: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards db67b19ad 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 46d3b6467 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 920f4bef0 72: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 668c8ad24 71: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 25ac47808 70: onsuccess: 7: Successful build after gcc: 4 commits discards d1f7caeb2 69: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 393dbc567 68: onsuccess: 7: Successful build after linux: 6 commits discards 22d2c2247 67: onsuccess: 7: Successful build after glibc: Revert "Detec [...] discards 1309d5ddb 66: onsuccess: 7: Successful build after gcc: libstdc++: Some [...] discards d38a931dd 65: onsuccess: 7: Successful build after binutils: 3 commits discards f97222746 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards b96ba227f 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 8041f9d0f 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards e25c357ba 61: onsuccess: 4: Successful build after gcc: 5 commits discards d87148fc1 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards d5c38ef3c 59: force: 7: Successful build after gcc: 3 commits discards 2215ce4f9 58: onsuccess: 7: Successful build after glibc: 2 commits discards a87337c22 57: onsuccess: 7: Successful build after gcc: 7 commits discards 0da869861 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards c64e7e29c 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 9c709b12f 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards cd3a315a6 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 11 [...] discards a7d87d54e 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 commits discards faff256ec 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards a46f802f4 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards c60a176d6 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 520c4a479 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards 6f984d10a 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 6a53c7300 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards d3ec6b9d3 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards b27955a26 44: onsuccess: 7: Successful build after linux: 34 commits discards 4ee2a19a7 43: onsuccess: 7: Successful build after gcc: 2 commits discards be6421e04 42: onsuccess: 7: Successful build after baseline build: no n [...] discards 08e551b48 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards e9feb0c0a 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 82199f7e6 39: onsuccess: 7: Successful build after gcc: 2 commits discards 2a82c6520 38: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 379175187 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards d0007c28c 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 1313fdc75 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 9f01f3595 34: onsuccess: 7: Successful build after gcc: 3 commits discards 6e584b0f0 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards ad530a9e3 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards f8efe90e4 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 13b9d2664 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits discards aed5af69c 29: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 610634a1b 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards f3b9e75e6 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards cc2eb6e0c 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards af8ba09f1 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards dafd87fb8 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 41650f9ef 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards f44675187 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e429a5b94 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 6a3f9a67a 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 98ec7f37d 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 21f14e454 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d9f48f965 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 4ae4f4255 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 1c2f07c35 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e1b0f28cc 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 27c5d39c9 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards e59dbe547 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 0d3102c42 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d676a3648 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 7b518572c 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 51ed7925b 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards a02d8abe4 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 6d7b726c6 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d9cd2e96e 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 7d3b95141 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 7cb53d7a3 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 6fb4ac334 2: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 821543304 1: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d0a64e95b 0: update: binutils-gcc-linux-glibc-gdb-qemu: 7 new 13f0bc87d 0: update: binutils-gcc-linux-glibc-gdb-qemu: 7 new 900b301e7 1: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 33bd67873 2: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3e5ff2beb 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 98556eef6 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2115f53a6 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e31269ca0 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2b3c18078 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 7fc68fbf6 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2e3bfed72 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 8a90e59dd 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e4a96ea81 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new f135ff1bc 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 529d03ec6 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 364b5a2bf 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new ef835aac6 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new cd01220aa 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 41e6643a7 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 33ba3947c 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d99dadea9 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 0d38bdc9d 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e70362f0e 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 7a49c738b 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 84241de92 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 68307da47 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new bab5aeb4f 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 4c8ae036e 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 38648390d 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 7037f07a8 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 64b586bf7 29: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 73fb51892 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits new dead36f3b 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new e74a7c86a 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new 3688a2b76 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 5515d767e 34: onsuccess: 7: Successful build after gcc: 3 commits new 17be3f9b9 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 3b002b32c 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new f2e8005b1 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new e99dbf403 38: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 0f5d0fc01 39: onsuccess: 7: Successful build after gcc: 2 commits new 459d1867b 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 63643e3af 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 40ca4f26e 42: onsuccess: 7: Successful build after baseline build: no n [...] new c6ecfd6e9 43: onsuccess: 7: Successful build after gcc: 2 commits new a9ce961d9 44: onsuccess: 7: Successful build after linux: 34 commits new e1457deb7 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 6ce471764 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 5a2888666 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 22d576ad4 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new 08d1390a9 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 302a09977 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 824c408c1 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 86181159f 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 commits new 2e71654d7 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 11 [...] new 63cd7c715 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new b7735d03e 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 53bd3358c 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 9b7e5b922 57: onsuccess: 7: Successful build after gcc: 7 commits new 03db4d123 58: onsuccess: 7: Successful build after glibc: 2 commits new 34b1cad5a 59: force: 7: Successful build after gcc: 3 commits new b8ac76b5d 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new 87906779f 61: onsuccess: 4: Successful build after gcc: 5 commits new d6187382c 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 46953a45a 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 4ad477ce0 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new 9a6792bb9 65: onsuccess: 7: Successful build after binutils: 3 commits new 3aa974ac9 66: onsuccess: 7: Successful build after gcc: libstdc++: Some [...] new 228216f27 67: onsuccess: 7: Successful build after glibc: Revert "Detec [...] new 4d90e2603 68: onsuccess: 7: Successful build after linux: 6 commits new c5556c9a5 69: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 165f9b82c 70: onsuccess: 7: Successful build after gcc: 4 commits new 17cf3c029 71: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new e0e3d3c5b 72: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 4c7ee5717 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 83a31cee1 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 7c625b4b8 75: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new c26d5aad7 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new 3652a78aa 77: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 879c8c829 78: onsuccess: 7: Successful build after gcc: rs6000: Allow c [...] new 8d5c1e1f0 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 1fc7df99b 80: onsuccess: 7: Successful build after linux: 44 commits new 298c9edba 81: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 3d99837c1 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new ed331f3e2 83: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 940f44e6e 84: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 504706edc 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new d29eb0d23 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 92fabd53e 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new a82831fce 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 79776c340 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 9492770c1 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 6d19af9ad 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 498c01c75 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 1072ba046 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new deacd10bc 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 1ef044f2f 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new f6247618c 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 6ac18e021 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new e1461fa73 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gdb [...] new 2261e740b 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new e0cb0877d 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/gd [...] new 7618dccce 101: onsuccess: #1547: 7: Success after binutils: 82 commits

This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:

* -- * -- B -- O -- O -- O (7d60283e7) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...]

You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.

Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.

The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.

Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1644 -> 1632 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2736 bytes 04-build_abe-binutils/console.log.xz | Bin 30460 -> 30492 bytes 05-build_abe-stage1/console.log.xz | Bin 73156 -> 72732 bytes 06-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 07-build_abe-linux/console.log.xz | Bin 9084 -> 8464 bytes 08-build_abe-glibc/console.log.xz | Bin 239568 -> 239436 bytes 09-build_abe-stage2/console.log.xz | Bin 204016 -> 202852 bytes 10-build_abe-gdb/console.log.xz | Bin 37788 -> 37616 bytes 11-build_abe-qemu/console.log.xz | Bin 31916 -> 31832 bytes 12-check_regression/console.log.xz | Bin 3108 -> 1892 bytes 13-update_baseline/console.log | 39 +++++++++++++++++++++++--- dashboard/dashboard-generate.sh | 6 ++-- dashboard/dashboard-push.sh | 8 ++++-- dashboard/squad/dashboard-push-squad.sh | 14 --------- dashboard/squad/score/results-functional.json | 1 + dashboard/squad/summary-annotation.txt | 0 dashboard/squad/test/results-functional.json | 4 --- dashboard/squad/test/results-metadata.json | 12 -------- dashboard/squad/test/results-metrics.json | 3 -- git/binutils_rev | 2 +- jenkins/dashboard-push.sh | 7 +++++ mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 31 +++++++++----------- 26 files changed, 68 insertions(+), 65 deletions(-) delete mode 100755 dashboard/squad/dashboard-push-squad.sh create mode 100644 dashboard/squad/score/results-functional.json delete mode 100644 dashboard/squad/summary-annotation.txt delete mode 100644 dashboard/squad/test/results-functional.json delete mode 100644 dashboard/squad/test/results-metadata.json delete mode 100644 dashboard/squad/test/results-metrics.json create mode 100755 jenkins/dashboard-push.sh