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 962710cd09 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 0bbd5931ed 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards ac027a5379 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 2629127dfd 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 3ef2e50ed2 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards c4bb930f58 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 74e750a253 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards da26c4225c 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 7b46598973 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 712ef0fa0c 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards d74fb0c3d0 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 4a47e8326f 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 3839bd8400 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards d953fd9fb2 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards be6625f241 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 8f4ff3a3ba 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 8f6e73787f 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 3a6dce358a 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards e16bb40ebb 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards b173cd758d 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 1bb356551a 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 35b4657f68 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards e22df442d2 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 0549e0abb8 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 9086f63c2b 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 1878b7f755 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 32d6d49e0c 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 741cf3d87d 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 7e4fa19aa6 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 34e8c1386d 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards f4740634cf 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards db14ea16ee 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 660da9b568 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 5664e56e1e 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 316602853c 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 50912fd468 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards fc2598cba6 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1df35e12ba 75: onsuccess: 1: Successful build after linux: 44 commits discards 2c784794bf 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 4338679e4d 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9c98b1d1a9 72: onsuccess: 1: Successful build after linux: 12 commits discards 7c0fcb4b73 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards aaa96f8566 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 7c4891b532 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 2c4641bd1b 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9acd549d92 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards b4a3fac70d 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 9515cae6c5 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b6644be1ca 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 586f07ba07 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards d06b222c2b 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards a68f0fa784 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards f42c7bbb5d 60: onsuccess: 1: Successful build after glibc: 2 commits discards c698ccbd87 59: onsuccess: 1: Successful build after binutils: 2 commits discards 618e3d8e04 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards c1abdb267d 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 775a44fa38 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards aa01cc0ca3 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards a828b55c12 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards db8c4c863b 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards bc53bc6308 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards e3a6904054 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 96572a485c 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards cab8106516 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards b7186f5e7c 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 21a30877c8 47: onsuccess: 1: Successful build after linux: 10 commits discards c6fc943fc2 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 1142b60962 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6a23276420 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 41b054a225 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards e8b88e490c 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards 6d8056f60b 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0adf98e656 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards 586f6f6ac6 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards e0686e370a 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards f144fc9785 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 4a049d3251 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 06e10dba86 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d8889d2524 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c3608ce1ed 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 38afbc2161 32: onsuccess: 1: Successful build after gcc: 7 commits discards e20ceb88ec 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 06a51fd5f6 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 77a645721e 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2647743d6f 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 63fd6f01fc 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards a0fa50e774 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ae54648fbc 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 834b25ba72 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 3fdc7d0ea4 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ad374c0343 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f5accfabb2 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 132fedab17 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 8f08668643 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9922de837c 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 37c15e44b5 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards db44eee928 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5bd40189bb 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 674b74364a 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c1c9bec63b 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 39339671e8 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6a0f01bb0b 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 834f4cb5dd 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e2a21b8eeb 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a2ed40cc4f 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f5e4f495af 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 01c5e05dab 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c01d98bd57 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b8ea61b877 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2da53b316e 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f55ed9ebc3 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a846b62d8e 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 7f7a2676af 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4c088258f2 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 535a464b62 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 12e9db7734 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ca132b2844 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 1b4e92fb89 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b0173c74c9 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 825d75ea49 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new c0f379888f 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 40187dbc5c 32: onsuccess: 1: Successful build after gcc: 7 commits new 0baeeb62f8 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b99b2bfb76 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d97205c390 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b2c1b11f70 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 784be32c5e 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 8296b92c54 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new 59fb7dd0c7 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 675e14c743 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new ae3caa0a69 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b9af34dc59 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new bb75eb2030 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 02ab4bb458 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 9ed71a364b 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 75857f86b3 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new dd5ca38720 47: onsuccess: 1: Successful build after linux: 10 commits new 6b75dcc36c 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0bafd65482 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new d774ddfee4 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 6ebc588873 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 272c251367 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 6abe05f2e1 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new cf680d33f1 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new e03f7152d4 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new e62ea6332a 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4bdf577aa5 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 6418f9f57e 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 46c5f3876e 59: onsuccess: 1: Successful build after binutils: 2 commits new d89dca92d2 60: onsuccess: 1: Successful build after glibc: 2 commits new 2b22076740 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new a8a8119a24 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 5120d32242 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 66137bf6d1 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fc6e9eabbc 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 72054d2795 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 73430a4c27 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new cdc8d24a54 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7f064315c1 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new fc83feac18 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 86a6277c35 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new b4518438c9 72: onsuccess: 1: Successful build after linux: 12 commits new f973713274 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0ed1bb3461 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 417f657ada 75: onsuccess: 1: Successful build after linux: 44 commits new 05c47cce58 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3db47de372 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 8635343de2 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new a13af89e7d 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new dea5c17967 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new cc65f24475 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new da132e6d86 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 2ac2557d9e 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new ed624ff44b 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 4ec0985ec9 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 063280d48e 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 3102e45da4 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 9249afd90d 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new f24f5ad2bb 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new e25005cfa9 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 6435cb139b 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 397281c37d 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 30324ebc25 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 09934e304b 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 763e37f57d 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new ea4cd3eeee 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new b518131791 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new b70cd855aa 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 0900136c9d 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 2adf370299 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new fd1fc72533 101: onsuccess: #2130: 1: Success after binutils: 81 commits new d42c8054b6 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new c93b2d532d 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 65a4e010dc 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new a95793fd5a 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 74ef9a3153 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new b035ffc0a6 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new c5536f87da 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new cbfc38059e 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new f869f3a11b 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 7287bcccc5 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 1c1f3ce9bd 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 81db82c2e5 113: onsuccess: #2145: 1: 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 (962710cd09) \ 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 1756 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 30060 -> 30988 bytes 04-build_abe-stage1/console.log.xz | Bin 72140 -> 73504 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8628 -> 8600 bytes 07-build_abe-glibc/console.log.xz | Bin 239952 -> 240152 bytes 08-build_abe-stage2/console.log.xz | Bin 202296 -> 206912 bytes 09-build_abe-gdb/console.log.xz | Bin 37392 -> 38468 bytes 10-build_abe-qemu/console.log.xz | Bin 31180 -> 31544 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3928 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2452 -> 3452 bytes 13-check_regression/console.log.xz | Bin 5312 -> 21468 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 542 ++- 13-check_regression/mail-body.txt | 131 +- 13-check_regression/results.compare | 597 ++- 13-check_regression/results.compare2 | 3449 ++++++++++++- 13-check_regression/results.regressions | 104 +- 14-update_baseline/console.log | 58 +- 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 | 133 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 104 +- sumfiles/g++.log.xz | Bin 3428868 -> 3421100 bytes sumfiles/g++.sum | 223 +- sumfiles/gcc.log.xz | Bin 3005388 -> 2986720 bytes sumfiles/gcc.sum | 8031 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1028812 -> 1024924 bytes sumfiles/gfortran.sum | 67 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2296 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201956 -> 201916 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2656 -> 2660 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 426316 -> 426136 bytes sumfiles/libstdc++.sum | 94 +- 44 files changed, 9177 insertions(+), 4436 deletions(-)