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 2b760c5e4 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/gd [...] discards 8b89b3167 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 9601cedc2 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 9ab8f7c9a 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-272 [...] discards 47797c5da 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/gd [...] discards e83fb9c87 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/gd [...] discards f6b8d5235 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddeed [...] discards 5a7a3480c 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/gl [...] discards fcd19076f 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 3308ab3c7 102: force: #1551: 1: Failure after gcc: 306 commits discards 6fc0c4700 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards d58af15a8 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/gd [...] discards 05b1b0743 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 11a1e085d 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gdb [...] discards 6b078baf9 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 8f9e505e8 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards d346515a9 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards d39e7bd74 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 745a40d35 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 0fd861572 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards e6ef38a69 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards ee0303f5e 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 7fd36c96b 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 9d7b4827c 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 6949aff17 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards add7324a5 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 55bf1e106 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits discards d9fcb8491 84: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 3cee13470 83: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards b739b638e 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits discards 4228e89e4 81: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards c52609450 80: onsuccess: 7: Successful build after linux: 44 commits discards f467746db 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards e49ff4b9c 78: onsuccess: 7: Successful build after gcc: rs6000: Allow c [...] discards 8791970cd 77: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards f1431152d 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits discards 303c5ac29 75: onsuccess: 7: Successful build after gcc: Require fgraphi [...] discards f644fccb8 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits discards 329ed95ee 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 1c1e882e5 72: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards e83b6eb88 71: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 27ba49c55 70: onsuccess: 7: Successful build after gcc: 4 commits discards 13e08927a 69: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 7e67108c0 68: onsuccess: 7: Successful build after linux: 6 commits discards 9d4eca10f 67: onsuccess: 7: Successful build after glibc: Revert "Detec [...] discards b0b6a3a5f 66: onsuccess: 7: Successful build after gcc: libstdc++: Some [...] discards 867caa38a 65: onsuccess: 7: Successful build after binutils: 3 commits discards 7b93de590 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] discards 142e3ff64 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 4ecc87f64 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 3165b0b0f 61: onsuccess: 4: Successful build after gcc: 5 commits discards 319188ac1 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] discards 68a733793 59: force: 7: Successful build after gcc: 3 commits discards 5590048b8 58: onsuccess: 7: Successful build after glibc: 2 commits discards b4b6f9959 57: onsuccess: 7: Successful build after gcc: 7 commits discards 047725fff 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 4327e1071 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 5f6328775 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards f7942646a 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 11 [...] discards 5f37dfe18 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 commits discards 400ba6286 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 283a05aa8 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 48773cc62 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 6359eee4e 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits discards 8836310d0 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 1b3189ea1 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 163ae93bd 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 8386509e6 44: onsuccess: 7: Successful build after linux: 34 commits discards 186d6ece7 43: onsuccess: 7: Successful build after gcc: 2 commits discards f66d3add4 42: onsuccess: 7: Successful build after baseline build: no n [...] discards a0b5b35e3 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards e1c891127 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 0c24958c5 39: onsuccess: 7: Successful build after gcc: 2 commits discards 3ceab9580 38: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 8653f41ed 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 31cd99255 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 51a8de3c9 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 585c49099 34: onsuccess: 7: Successful build after gcc: 3 commits discards a05a10e56 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards 011f27616 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards f48d805d5 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards f247d03c8 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits discards c7e2d67a9 29: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] discards b4db98943 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] discards 72c15317f 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] discards 8c5116074 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 6704c1a6a 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 4d5e712b1 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 24306c776 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 3ed759e73 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 2f334b5bd 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards b40bbbf0c 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 37fdea69a 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 64b14b58b 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 978ff580e 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards cf03db319 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 4d6c9be2e 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards dc4367a82 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 79004da67 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 8516917cc 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards dcb21bc79 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 6afb1b807 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 1063c201b 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 52cd81486 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 681af7248 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3cf2ee4a8 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e6427281b 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 576cbe754 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e50e74916 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 1dfb8efa2 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new c50ab5205 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 25458d4f9 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new e771a52f5 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 0c56a836c 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a2f8f8729 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 5df73c529 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new de0d27d06 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a98e7e417 27: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new a71b7b49e 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new cbf620450 29: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new b9d75d337 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits new aeb62bab2 31: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 1da837a2d 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new 18f57378b 33: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 3e5dba439 34: onsuccess: 7: Successful build after gcc: 3 commits new f42175aff 35: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 40b0da681 36: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 2c51d8fbf 37: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 397df7e0b 38: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 536b49d90 39: onsuccess: 7: Successful build after gcc: 2 commits new c1c882679 40: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 4d927c3a1 41: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new b233c5ad3 42: onsuccess: 7: Successful build after baseline build: no n [...] new ec1461176 43: onsuccess: 7: Successful build after gcc: 2 commits new 7478c2f57 44: onsuccess: 7: Successful build after linux: 34 commits new 96b9ad39b 45: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 9802ad34c 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new c10633c03 47: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new f79685358 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 commits new aaa88f1ee 49: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 9c110ed28 50: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new e05e24bb1 51: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new 329fdfec6 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 commits new 042fb2433 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 11 [...] new 6ac1646d6 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new b4c896b7e 55: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 1a845c1df 56: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 5b6ed6b08 57: onsuccess: 7: Successful build after gcc: 7 commits new 018363953 58: onsuccess: 7: Successful build after glibc: 2 commits new 7bbe5be7b 59: force: 7: Successful build after gcc: 3 commits new bd3f8b0bc 60: force: 4: Regression after gcc: libstdc++: Optimize opera [...] new 468496467 61: onsuccess: 4: Successful build after gcc: 5 commits new 86831fce5 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 91c2a2618 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qem [...] new 7bcb9736b 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 23 [...] new 61a970129 65: onsuccess: 7: Successful build after binutils: 3 commits new 4a2a52d31 66: onsuccess: 7: Successful build after gcc: libstdc++: Some [...] new 787d378b7 67: onsuccess: 7: Successful build after glibc: Revert "Detec [...] new 7997c3ef7 68: onsuccess: 7: Successful build after linux: 6 commits new 9c22aad57 69: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new ffa9ae514 70: onsuccess: 7: Successful build after gcc: 4 commits new a3d609453 71: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new c519bb1dd 72: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new ac4ad7a2d 73: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 9e90af73a 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 commits new 4e11f291e 75: onsuccess: 7: Successful build after gcc: Require fgraphi [...] new 825f5de57 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 commits new ae9aa2211 77: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 031c5db7e 78: onsuccess: 7: Successful build after gcc: rs6000: Allow c [...] new 995b5a0ac 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new d9f216713 80: onsuccess: 7: Successful build after linux: 44 commits new fd4130a58 81: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new be5ed259c 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 commits new 4d4db5123 83: onsuccess: 7: Successful build after binutils/gcc/linux/g [...] new 81c9e25a4 84: onsuccess: 7: Successful build after binutils/gcc/glibc/g [...] new e72499634 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 commits new d89f41c07 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new ce48391ce 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 03d4cb64c 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 3acd1a13a 89: onsuccess: 7: Success after gcc/glibc: 8 commits new e2ae5088e 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new d9369df81 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new b676fc6a1 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 8d1d8448a 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 0004c5b73 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new fe90a6331 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new fe240ae41 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 0945b2e02 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 7aa110dbb 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gdb [...] new 3361ff59a 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new c4047a368 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/gd [...] new 32111668e 101: onsuccess: #1547: 7: Success after binutils: 82 commits new c0155e339 102: force: #1551: 1: Failure after gcc: 306 commits new 2936eb565 103: onsuccess: #1552: 1: Success after gcc: 5 commits new 51715212c 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/gl [...] new c12f44d36 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddeed [...] new 52eba0e3e 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/gd [...] new 4dc182b10 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/gd [...] new 472b12f2a 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-272 [...] new 9605eb067 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 9584033d7 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 6adc2749b 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/gd [...] new 4f4ce1f34 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/gl [...]

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 (2b760c5e4) \ 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 1724 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2752 bytes 04-build_abe-binutils/console.log.xz | Bin 30144 -> 30328 bytes 05-build_abe-stage1/console.log.xz | Bin 72208 -> 72268 bytes 06-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 07-build_abe-linux/console.log.xz | Bin 8284 -> 8564 bytes 08-build_abe-glibc/console.log.xz | Bin 240020 -> 238992 bytes 09-build_abe-stage2/console.log.xz | Bin 203140 -> 202320 bytes 10-build_abe-gdb/console.log.xz | Bin 37464 -> 37504 bytes 11-build_abe-qemu/console.log.xz | Bin 31564 -> 31716 bytes 12-check_regression/console.log.xz | Bin 3244 -> 3444 bytes 13-update_baseline/console.log | 42 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 ++++++++++++++++----------------- 22 files changed, 50 insertions(+), 50 deletions(-)