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 7de3160310 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 65a64e3dd9 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards 760930ca19 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards c0e13678c7 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards e50f6cac74 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards 9a41f4b785 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards f0935da924 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards ad862e2481 102: force: #1551: 1: Failure after gcc: 306 commits discards 3caade25f8 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 564b51afd1 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards 84358c735b 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards c7112967c5 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards 71d76618da 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards b522affbea 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards b1bc775d81 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 59e52b74c2 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 458b1a5b0d 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 6ec52b65ac 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 2e22e38159 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards b13c45c3a1 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards ade0d8c386 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards c410f27809 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards f37ea46227 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards ff673d424e 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 6f61681308 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 6206299331 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards fbae6215c2 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 7c46930294 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 5141bcb1f1 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards d5a8832a44 80: onsuccess: 7: Successful build after linux: 44 commits discards 8212919a59 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards b613f5eb2f 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards 59c6505253 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 57dfd693b0 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards e5f4f4c6b5 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 66ab8a3c73 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 97fe101d9e 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards acedbf70e4 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 6ad2e38311 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 03027de737 70: onsuccess: 7: Successful build after gcc: 4 commits discards 8627cc70c1 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 5b78343e50 68: onsuccess: 7: Successful build after linux: 6 commits discards 208d81dfe7 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards 8990aad9cf 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards 0f3b941324 65: onsuccess: 7: Successful build after binutils: 3 commits discards 3133a4864c 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards beffe27685 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards fb0366f352 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 009846821e 61: onsuccess: 4: Successful build after gcc: 5 commits discards 896f5ca469 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 45e5ae6787 59: force: 7: Successful build after gcc: 3 commits discards 580b27f556 58: onsuccess: 7: Successful build after glibc: 2 commits discards fcb7546aa8 57: onsuccess: 7: Successful build after gcc: 7 commits discards 32fc3de448 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 3217ddded2 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 79f0854f6e 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards 6d17fb792a 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards b9ba60ad4c 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] discards ed8e957632 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 6bdcec8367 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards b1c455a544 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards ef4e365a33 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards df79197b3f 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards d02273b012 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 003bd20b34 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 56a12911e4 44: onsuccess: 7: Successful build after linux: 34 commits discards 349c942470 43: onsuccess: 7: Successful build after gcc: 2 commits discards 65afd7e594 42: onsuccess: 7: Successful build after baseline build: no [...] discards 5b10492d43 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ac83a4167c 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 77fe266c2a 39: onsuccess: 7: Successful build after gcc: 2 commits discards 99bc56a4a5 38: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 16a3c8ac56 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 8e16909be2 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards a80cde56ad 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 7afaeecfad 34: onsuccess: 7: Successful build after gcc: 3 commits discards 76182b157c 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 437147d818 32: onsuccess: 7: Successful build after gcc/linux: 17 commits discards f57ad6d3c8 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards c18d8eb058 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits discards f8f4a33177 29: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards bad877eeb5 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards d7e956c1a5 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards a58bd6d3e5 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 3e56e8e606 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards beb502f9b9 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 32f839dd9f 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards dbbaf62630 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 5e35bb71f9 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 04214bbde5 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 4e799fb873 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 759f11b7d7 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 5d43904a29 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards cc3d06ab95 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 14291b58ad 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 54a83190f0 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 90a94e2d36 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards dabbec2ebb 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards cc71ce5039 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 680910ebd1 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 discards 1bfc1d98f8 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 83d3a56cc4 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 9270915a32 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 1df2a50911 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 234277154c 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new d138a16ef5 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 90b9f57ea5 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new ebba5aed26 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new b4ad671c1a 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 609daa642e 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new f1446a0124 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 5561d54288 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new a7c7fce2d4 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 41eaad7a1d 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 28494ff615 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 06e56e0e7e 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 6ec3f826af 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new dbd9d3a0bd 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 0737f71391 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 7 new 95489e8fa7 27: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 96565ec014 28: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 7b622eca9f 29: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 0a3d210e5e 30: onsuccess: 7: Successful build after gcc/qemu: 3 commits new 2424442574 31: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 459f9ad33a 32: onsuccess: 7: Successful build after gcc/linux: 17 commits new ee2c08ff98 33: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 40b545f86f 34: onsuccess: 7: Successful build after gcc: 3 commits new f48a215b97 35: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 7daa140e0b 36: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 79728aa955 37: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 17d8427d87 38: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ee610ea371 39: onsuccess: 7: Successful build after gcc: 2 commits new 02ce4a3737 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5ede48f65a 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new db8ada5d8d 42: onsuccess: 7: Successful build after baseline build: no [...] new f587f41977 43: onsuccess: 7: Successful build after gcc: 2 commits new 00ff2a0dad 44: onsuccess: 7: Successful build after linux: 34 commits new a917baf16d 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 739b1c96d0 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new e777f6c8f7 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new fd628386d3 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new 2ec1475cc9 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new d2c618147b 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 90ff3615bd 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 28336ba5b0 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] new efe50cf725 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 84e904712c 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new db9bfc5f60 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ad4ab2cae0 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 656bf37e7a 57: onsuccess: 7: Successful build after gcc: 7 commits new 61c27c1e4e 58: onsuccess: 7: Successful build after glibc: 2 commits new a1ecc77145 59: force: 7: Successful build after gcc: 3 commits new ddeed78242 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 6c55c9f640 61: onsuccess: 4: Successful build after gcc: 5 commits new b9518ea689 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new b286c365ca 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 2c14f8091e 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 3c3e75b739 65: onsuccess: 7: Successful build after binutils: 3 commits new c306c152a3 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new a073144617 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new 1cb895892f 68: onsuccess: 7: Successful build after linux: 6 commits new 36ca4ced8d 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new fe22a746b4 70: onsuccess: 7: Successful build after gcc: 4 commits new 4e3d1ecfff 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 0c0a9e8304 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new bafe2b7a5a 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new da3015c5e2 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 5d9354a780 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 0b55e4250a 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 4048c97498 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new c8a882b99d 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new 4ce0a23bc2 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new cf36134368 80: onsuccess: 7: Successful build after linux: 44 commits new 94bfb485e1 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 19506e513f 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 304b1b6545 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 8b67d35cf8 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new b792ddad96 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 4720da81f2 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 6f476d94d0 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 2b1f29acee 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 57eb508fcf 89: onsuccess: 7: Success after gcc/glibc: 8 commits new abafba6cc9 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new a0464e7892 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 53fee6e8b6 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new d38472b36a 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 2fe53c072d 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 2db29c86ee 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new c032aa8932 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 72bff5878d 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 1f5f911a25 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 71d19d9d69 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 6aae3d5ffe 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new ff626c5b85 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 87beb7bf08 102: force: #1551: 1: Failure after gcc: 306 commits new b3274b9709 103: onsuccess: #1552: 1: Success after gcc: 5 commits new 7e5d68d745 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new 84b3f0ff89 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new 96bad34052 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 091332cdea 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new f337e5d67f 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new 9bd67aff97 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new f2c6b9d324 110: onsuccess: #1559: 7: Success after gcc: 4 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 (7de3160310) \ 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 1732 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 30184 -> 30172 bytes 05-build_abe-stage1/console.log.xz | Bin 72108 -> 72280 bytes 07-build_abe-linux/console.log.xz | Bin 8280 -> 8276 bytes 08-build_abe-glibc/console.log.xz | Bin 239356 -> 238840 bytes 09-build_abe-stage2/console.log.xz | Bin 201968 -> 203988 bytes 10-build_abe-gdb/console.log.xz | Bin 37432 -> 37584 bytes 11-build_abe-qemu/console.log.xz | Bin 31684 -> 32120 bytes 12-check_regression/console.log.xz | Bin 2412 -> 2324 bytes 13-update_baseline/console.log | 68 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 ++++++------- 17 files changed, 51 insertions(+), 51 deletions(-)