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 f2c6b9d324 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 9bd67aff97 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards f337e5d67f 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards 091332cdea 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards 96bad34052 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards 84b3f0ff89 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards 7e5d68d745 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards b3274b9709 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 87beb7bf08 102: force: #1551: 1: Failure after gcc: 306 commits discards ff626c5b85 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 6aae3d5ffe 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards 71d19d9d69 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 1f5f911a25 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards 72bff5878d 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards c032aa8932 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2db29c86ee 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2fe53c072d 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards d38472b36a 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 53fee6e8b6 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards a0464e7892 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards abafba6cc9 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 57eb508fcf 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 2b1f29acee 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 6f476d94d0 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 4720da81f2 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards b792ddad96 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 8b67d35cf8 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 304b1b6545 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 19506e513f 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 94bfb485e1 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards cf36134368 80: onsuccess: 7: Successful build after linux: 44 commits discards 4ce0a23bc2 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards c8a882b99d 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards 4048c97498 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 0b55e4250a 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 5d9354a780 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards da3015c5e2 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards bafe2b7a5a 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 0c0a9e8304 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 4e3d1ecfff 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards fe22a746b4 70: onsuccess: 7: Successful build after gcc: 4 commits discards 36ca4ced8d 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 1cb895892f 68: onsuccess: 7: Successful build after linux: 6 commits discards a073144617 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards c306c152a3 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards 3c3e75b739 65: onsuccess: 7: Successful build after binutils: 3 commits discards 2c14f8091e 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards b286c365ca 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards b9518ea689 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 6c55c9f640 61: onsuccess: 4: Successful build after gcc: 5 commits discards ddeed78242 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards a1ecc77145 59: force: 7: Successful build after gcc: 3 commits discards 61c27c1e4e 58: onsuccess: 7: Successful build after glibc: 2 commits discards 656bf37e7a 57: onsuccess: 7: Successful build after gcc: 7 commits discards ad4ab2cae0 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards db9bfc5f60 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 84e904712c 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards efe50cf725 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 28336ba5b0 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] discards 90ff3615bd 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards d2c618147b 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 2ec1475cc9 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards fd628386d3 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards e777f6c8f7 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 739b1c96d0 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards a917baf16d 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 00ff2a0dad 44: onsuccess: 7: Successful build after linux: 34 commits discards f587f41977 43: onsuccess: 7: Successful build after gcc: 2 commits discards db8ada5d8d 42: onsuccess: 7: Successful build after baseline build: no [...] discards 5ede48f65a 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 02ce4a3737 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ee610ea371 39: onsuccess: 7: Successful build after gcc: 2 commits discards 17d8427d87 38: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 79728aa955 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 7daa140e0b 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards f48a215b97 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 40b545f86f 34: onsuccess: 7: Successful build after gcc: 3 commits discards ee2c08ff98 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 459f9ad33a 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards 2424442574 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 0a3d210e5e 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits discards 7b622eca9f 29: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 96565ec014 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 95489e8fa7 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 0737f71391 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards dbd9d3a0bd 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 6ec3f826af 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 06e56e0e7e 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 28494ff615 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 41eaad7a1d 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards a7c7fce2d4 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 5561d54288 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards f1446a0124 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 609daa642e 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards b4ad671c1a 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards ebba5aed26 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 90b9f57ea5 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards d138a16ef5 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 234277154c 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 1df2a50911 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 9270915a32 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 9d1ecf0035 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new dcb21bc796 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 8516917cc4 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 79004da673 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new dc4367a826 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 4d6c9be2ed 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new cf03db319e 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 978ff580e4 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 64b14b58bd 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 37fdea69a8 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new b40bbbf0c3 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 2f334b5bde 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 3ed759e733 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 24306c776e 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 4d5e712b19 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 6704c1a6a0 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 8c51160741 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 72c15317f7 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new b4db98943d 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new c7e2d67a93 29: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f247d03c86 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits new f48d805d53 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 011f27616e 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new a05a10e561 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 585c490996 34: onsuccess: 7: Successful build after gcc: 3 commits new 51a8de3c96 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 31cd992554 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 8653f41edb 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 3ceab95801 38: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 0c24958c5c 39: onsuccess: 7: Successful build after gcc: 2 commits new e1c891127d 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new a0b5b35e30 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f66d3add42 42: onsuccess: 7: Successful build after baseline build: no [...] new 186d6ece70 43: onsuccess: 7: Successful build after gcc: 2 commits new 8386509e62 44: onsuccess: 7: Successful build after linux: 34 commits new 163ae93bd9 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 1b3189ea1c 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new 8836310d03 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 6359eee4e9 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new 48773cc62d 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 283a05aa8e 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 400ba62866 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 5f37dfe18b 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] new f7942646ae 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 5f6328775f 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 4327e10712 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 047725fff2 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b4b6f99598 57: onsuccess: 7: Successful build after gcc: 7 commits new 5590048b80 58: onsuccess: 7: Successful build after glibc: 2 commits new 68a7337936 59: force: 7: Successful build after gcc: 3 commits new 319188ac1f 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 3165b0b0f6 61: onsuccess: 4: Successful build after gcc: 5 commits new 4ecc87f64f 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 142e3ff64f 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 7b93de590c 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 867caa38af 65: onsuccess: 7: Successful build after binutils: 3 commits new b0b6a3a5fd 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new 9d4eca10f3 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new 7e67108c03 68: onsuccess: 7: Successful build after linux: 6 commits new 13e08927aa 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 27ba49c558 70: onsuccess: 7: Successful build after gcc: 4 commits new e83b6eb889 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 1c1e882e5a 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 329ed95ee2 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f644fccb8c 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 303c5ac29d 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new f1431152db 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 8791970cd6 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new e49ff4b9c1 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new f467746db7 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new c526094508 80: onsuccess: 7: Successful build after linux: 44 commits new 4228e89e48 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b739b638e3 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 3cee134707 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new d9fcb8491a 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 55bf1e106e 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new add7324a5e 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 6949aff172 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 9d7b4827ca 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 7fd36c96b1 89: onsuccess: 7: Success after gcc/glibc: 8 commits new ee0303f5e6 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new e6ef38a694 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 0fd8615724 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 745a40d35a 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new d39e7bd746 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new d346515a94 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 8f9e505e8f 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 6b078baf99 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 11a1e085d8 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 05b1b07438 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new d58af15a85 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new 6fc0c47007 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 3308ab3c71 102: force: #1551: 1: Failure after gcc: 306 commits new fcd19076f7 103: onsuccess: #1552: 1: Success after gcc: 5 commits new 5a7a3480c5 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new f6b8d52359 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new e83fb9c87c 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 47797c5da8 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new 9ab8f7c9a6 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new 9601cedc28 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 8b89b31675 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 2b760c5e4e 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...]
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 (f2c6b9d324) \ 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 1664 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 30172 -> 30144 bytes 05-build_abe-stage1/console.log.xz | Bin 72280 -> 72208 bytes 07-build_abe-linux/console.log.xz | Bin 8276 -> 8284 bytes 08-build_abe-glibc/console.log.xz | Bin 238840 -> 240020 bytes 09-build_abe-stage2/console.log.xz | Bin 203988 -> 203140 bytes 10-build_abe-gdb/console.log.xz | Bin 37584 -> 37464 bytes 11-build_abe-qemu/console.log.xz | Bin 32120 -> 31564 bytes 12-check_regression/console.log.xz | Bin 2324 -> 3244 bytes 13-update_baseline/console.log | 40 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 ++++++++++++++--------------- 20 files changed, 45 insertions(+), 45 deletions(-)