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 06f59b34a 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/gd [...] discards 9922dba2d 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] discards 61664b549 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 9d53340ef 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] discards 600b24b60 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] discards 7a317d265 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 81b453d15 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] discards eb538367a 99: onsuccess: #2074: 1: Success after baseline build: no new [...] discards 852189791 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards d782b69a3 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards e0187b1e9 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 60d5133c1 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] discards c85fe6bf2 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] discards 8ad1bea64 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards b3b286588 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 5b115ea76 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards efb79c56a 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards ff30f54fa 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards becdabdd4 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 5e442502c 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 17e81e985 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 711643c5a 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 77372cd14 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 171b0cd4f 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 01f3615e0 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards 596dcb99c 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits discards b41cb0be6 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 036dc66e9 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards c264160e9 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards cc7bc622f 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits discards 373449c31 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7c4831688 75: onsuccess: 1: Successful build after linux: 44 commits discards 2aed1a99c 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards d4d328cc0 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards c6714f523 72: onsuccess: 1: Successful build after linux: 12 commits discards 1aaaa2056 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 7ff50b960 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 69aa6bf37 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 98143605c 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 810b98eea 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] discards 3d1beffeb 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 3f2626f1e 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards c919b02e0 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 040117f59 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 6cd682b75 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] discards 417a32484 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 4863b712b 60: onsuccess: 1: Successful build after glibc: 2 commits discards f5c8bbcfe 59: onsuccess: 1: Successful build after binutils: 2 commits discards 2b0e5db0c 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] discards 4ddce5a5e 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards e8572c9fc 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f4fb8009b 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] discards 30164f4f2 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 50446c867 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 699db4ecc 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits discards 3665e6506 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 1f93bfda9 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 204be1c8f 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards b9aecdd00 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards faeaa9c76 47: onsuccess: 1: Successful build after linux: 10 commits discards 0095d9535 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 483719db9 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f4ed93a3f 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 20a97e0ff 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards 128047938 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] discards b2d4a2305 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 62f78d282 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards 1a7e099f6 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards b86d7d8be 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards de1a031fb 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards c7bd62601 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 19b0ae831 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 22668ce26 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 3b3a0cc37 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 8d7005652 32: onsuccess: 1: Successful build after gcc: 7 commits discards 94a09ae15 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards dc4b4453d 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 70ccd1706 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b9d6afdc0 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards dccbb606d 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] discards a12344612 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 1d2773d11 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e6d389c82 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards dcbb15b34 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9cc93272a 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b19cf4c7d 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 376e87b40 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 345f937ac 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b42bd8e02 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 8bc969403 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9668e4dd5 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e1275fa8c 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 955de72fd 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 123c27910 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards cfa6e7cc4 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 4e5edcd95 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 0d2f54193 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f55753c6e 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 48e912b7c 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 26e3e529c 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 6a60242ea 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 363285449 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 624496d8c 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f05b28e3d 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 3741a81da 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 686e61210 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 39934fa0b 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 21dfb544b 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 1faeaabe2 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 43f85b2f2 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new eed29c4f5 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8e508fd46 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f98475877 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d0343751c 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5144ee1ea 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new efc23b5b5 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new dc3f087f0 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 1e1ab7709 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new cd872822f 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 784278090 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 433d1e422 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e4050fc5e 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4e5d05e4e 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] new 7ae8dc7a1 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new acc3b54b4 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 821030dcd 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new c1959c3a4 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 58f355441 32: onsuccess: 1: Successful build after gcc: 7 commits new ef2b87bd0 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 29d7df31d 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new c62b4b2e6 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 6ac3514a5 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new b92b7c487 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 7afa1eede 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new 51db3509c 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 6b8b316fc 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new 5cdb9c856 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 3e439555e 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] new b9b95ea1d 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 39f2831bb 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 8a3976bec 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 9d4f18caa 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 9834cab65 47: onsuccess: 1: Successful build after linux: 10 commits new ffb4da601 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e4a23f26a 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new a34e5b90a 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new c24b46515 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 14e72b375 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits new 4111b409d 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new f65df45bf 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new b1456bd3e 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] new b78d9f1e1 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2c7eb20b5 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 1e4c28d13 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] new 4b0d5fd3d 59: onsuccess: 1: Successful build after binutils: 2 commits new c06c83470 60: onsuccess: 1: Successful build after glibc: 2 commits new 9008bf7f2 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new d9f79836c 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] new 03601dadd 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 7af305e92 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e549dfb0f 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a68305050 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 87c5648e1 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] new de1523952 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new ca767a80b 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new 6a4be8ca0 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 29c0d0fcc 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new b4c9ced72 72: onsuccess: 1: Successful build after linux: 12 commits new 4e3d61b94 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c0933daaf 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 1ecf4f2b2 75: onsuccess: 1: Successful build after linux: 44 commits new 20643375b 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a6afd9bb5 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits new d29528eb9 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new a098db2d3 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new bb9ae965c 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new aa4d6b8f9 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits new 26075481d 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new b1ab5095c 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 8146e8b44 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 005f1677e 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new d733f889b 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 4fd57f85a 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 4b2ade4bd 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 366a1785f 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 0ddcd9a6c 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new c68c53abf 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 373dab9f5 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 3594bbfeb 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 4d94f6300 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] new 6a92026f8 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] new 03986490d 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 5c78900df 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 493d3ca5a 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 1e6a48a2e 99: onsuccess: #2074: 1: Success after baseline build: no new [...] new da1702944 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] new ef74ada7a 101: onsuccess: #2130: 1: Success after binutils: 81 commits new b1142c295 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] new 7719e0c6c 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] new 3392a0c3f 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new f34f00460 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] new 5b8e0f9b7 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/gd [...] new 9416a86be 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 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 (06f59b34a) \ 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 1800 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30412 -> 30304 bytes 04-build_abe-stage1/console.log.xz | Bin 72528 -> 72232 bytes 06-build_abe-linux/console.log.xz | Bin 8308 -> 8332 bytes 07-build_abe-glibc/console.log.xz | Bin 239664 -> 240112 bytes 08-build_abe-stage2/console.log.xz | Bin 203284 -> 203184 bytes 09-build_abe-gdb/console.log.xz | Bin 37580 -> 37436 bytes 10-build_abe-qemu/console.log.xz | Bin 31660 -> 31564 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3932 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2812 -> 2660 bytes 13-check_regression/console.log.xz | Bin 5300 -> 18840 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 565 ++- 13-check_regression/mail-body.txt | 147 +- 13-check_regression/results.compare | 583 ++- 13-check_regression/results.compare2 | 3314 +++++++++++++- 13-check_regression/results.regressions | 122 +- 14-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 149 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 122 +- sumfiles/g++.log.xz | Bin 3419000 -> 3396056 bytes sumfiles/g++.sum | 113 +- sumfiles/gcc.log.xz | Bin 3000224 -> 2984812 bytes sumfiles/gcc.sum | 7462 ++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1025580 -> 1027268 bytes sumfiles/gfortran.sum | 54 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201860 -> 202228 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 423064 -> 426180 bytes sumfiles/libstdc++.sum | 10 +- 42 files changed, 8361 insertions(+), 4392 deletions(-)