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_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts.

discards 4e4736de9 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/gd [...] discards 0ded324dd 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/gd [...] discards 4cbde58eb 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/gd [...] discards 59faa85ad 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/gl [...] discards adbc862ff 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/gd [...] discards 397b5a02e 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 7fd70efc1 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 626f345c3 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards d4f4eb28f 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/gd [...] discards 8086e4fd8 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] discards 36b70af86 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 5be214ca2 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] discards 47e57e340 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] discards 65a4f24fe 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 4455e2ebf 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] discards a2cf0dad0 99: onsuccess: #2074: 1: Success after baseline build: no new [...] discards df9e3b356 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 22902e540 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 5107263cd 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards e3c76b7a8 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] discards eae0feadf 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] discards b4d3337f5 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards d04d8646d 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 292c4b743 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 1bbfc8f34 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 7a3578446 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards ef4aa1140 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards dcbb68c6f 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 4a5b2a881 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 1c3bc8e30 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards dac818a27 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 54f29b0f3 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 912a86ed7 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards 0cc9250e9 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits discards 6ab0c4981 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 7782212ab 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 11cfbf7be 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 70612a5f9 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits discards c7f26f047 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 5c0840568 75: onsuccess: 1: Successful build after linux: 44 commits discards 7b858ed67 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards e87f54e29 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7e4442642 72: onsuccess: 1: Successful build after linux: 12 commits discards 904d479d0 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards dd04dc007 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 1f14a1da6 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards d624e16bb 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards fb5c09dea 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] discards a5f25cbf6 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards c3309a7a0 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 8a2de5467 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 2a22bded3 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 2b34d64a3 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] discards 9ef32dec9 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 8ffb9f39a 60: onsuccess: 1: Successful build after glibc: 2 commits discards f298d4009 59: onsuccess: 1: Successful build after binutils: 2 commits discards 0f2943e83 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] discards dd7e913bc 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards a549c20c4 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 29bd93db2 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] discards ae09e4918 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 4ee829b01 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 7afe02efc 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits discards 6fb0b9658 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 3624c02a2 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards cf8f7ef94 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 0ec3af9db 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 6169b4923 47: onsuccess: 1: Successful build after linux: 10 commits discards 6e223668a 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 1805d01c0 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 6cf0c6973 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 73954d358 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards c104b2f8e 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] discards a9c114966 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a25826e14 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards d96e5c31f 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 98b15bd02 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards 0670d0b3b 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards b8fa65dce 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 14e41293c 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 9ee0ae88f 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 47a0402bd 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 5bd2597b1 32: onsuccess: 1: Successful build after gcc: 7 commits discards 5c2d084a0 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 8df63be7b 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 9e9dc21db 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 4d6bfcc24 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards d23e8d055 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] discards 7575bb1f2 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ea00214c9 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 256b8b227 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 963cf5d27 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 453727fec 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 8950f7ca6 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b208c0870 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 7d828e8be 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 05276b493 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 12c3ec638 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 1944bc2fa 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b59cb0c86 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 76b5496b8 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 111ce3329 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 71aea626b 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6fbe01c19 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 510b198e6 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c2a7fc2c6 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new abb905616 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f092ed643 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new eb6c3f43e 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d4cec0d20 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new cd82b898d 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e55c20c2c 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 0fd4418cc 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 7ace53ebb 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 871e44dbe 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] new 6d90c453d 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 403ab8e45 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 801ce40e3 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new e2bf42611 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 2dbceec75 32: onsuccess: 1: Successful build after gcc: 7 commits new 836b8cd67 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c7f052a3c 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 348855d02 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new de1d1d0cc 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 71bc5ed95 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 7f9697145 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new af4a25f60 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 3258f8c05 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new dc5462864 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e48b8ec2b 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] new 8ae4cfb4b 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new a732c939b 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 264bcfe35 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 3965a24c8 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new f6cbf55b0 47: onsuccess: 1: Successful build after linux: 10 commits new bd3c56879 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 0299b574a 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 4b19e96dd 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 8d0c5dc7b 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 4fdc7f0d4 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits new ca7688d98 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new b63dc201b 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 32e0d1360 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] new c77a6d6ea 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 066a43881 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 581d054f2 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] new 9371baf8c 59: onsuccess: 1: Successful build after binutils: 2 commits new a3a501b0c 60: onsuccess: 1: Successful build after glibc: 2 commits new 244e24aa3 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 5a94864ff 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] new 4c1f3d84c 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 1293e46e2 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 001f70a1d 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new aacfa1d8f 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 0a0134d63 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] new 5a4bf97b9 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 761f9921e 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new 4b53de69e 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new c69057fbb 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 671a4f11c 72: onsuccess: 1: Successful build after linux: 12 commits new 9513374ae 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 5ffb7b149 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 0410e7674 75: onsuccess: 1: Successful build after linux: 44 commits new ac4437895 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 02ad0dfbe 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits new fd0feedbe 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new f8cd7c98c 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new feb2a5a61 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 91c69e348 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits new 8025eb64e 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new b4291e2fb 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 77529d1dc 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 16168588d 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new a7e50604e 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 362f50bb1 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 99dd8169d 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 7f1ab2696 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 70fd88d0f 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new f13468ee6 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 0a6894c92 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new bd101ea78 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new af0319924 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] new 4b3b879ca 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] new 33417f948 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 1e44983b9 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new c8f43e4e9 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 590d2716a 99: onsuccess: #2074: 1: Success after baseline build: no new [...] new 17b52ee7a 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] new 983e0078b 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 6e90689b3 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] new 063c6a17d 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] new 590803e0d 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 47d0a0ef1 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] new 20c6d422e 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/gd [...] new b3df9c156 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 780459db2 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new e622ed6c7 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new bff3eeb62 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/gd [...] new 6f56c266f 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/gl [...] new 9c8c13af3 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/gd [...] new d90fe5494 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/gd [...] new 91464cc5f 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/gd [...] new 9cdfca1bf 115: onsuccess: #2147: 1: Success after binutils/linux/glibc/ [...]

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 (4e4736de9) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...]

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 1708 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30268 -> 30456 bytes 04-build_abe-stage1/console.log.xz | Bin 72492 -> 72500 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8584 -> 8584 bytes 07-build_abe-glibc/console.log.xz | Bin 239288 -> 239968 bytes 08-build_abe-stage2/console.log.xz | Bin 203488 -> 202608 bytes 09-build_abe-gdb/console.log.xz | Bin 37464 -> 37532 bytes 10-build_abe-qemu/console.log.xz | Bin 31264 -> 31880 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2672 -> 2684 bytes 13-check_regression/console.log.xz | Bin 32812 -> 23140 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 167 +- 13-check_regression/mail-body.txt | 244 +- 13-check_regression/results.compare | 722 +-- 13-check_regression/results.compare2 | 8335 +++++++++++-------------------- 13-check_regression/results.regressions | 164 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 246 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 164 +- sumfiles/g++.log.xz | Bin 3396252 -> 3410080 bytes sumfiles/g++.sum | 3516 ++++++++----- sumfiles/gcc.log.xz | Bin 3022208 -> 3013788 bytes sumfiles/gcc.sum | 4876 +++++++++--------- sumfiles/gfortran.log.xz | Bin 1027216 -> 1030388 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202104 -> 201992 bytes sumfiles/libgomp.sum | 21 +- sumfiles/libitm.log.xz | Bin 2664 -> 2652 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 426948 -> 416088 bytes sumfiles/libstdc++.sum | 16 +- 45 files changed, 8239 insertions(+), 10402 deletions(-)