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 94a8dfb354 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards c41bcd5a4c 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 2cea14d8fc 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 26a44b3327 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards a42c02ed3b 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 9b996ef221 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 02a0373fa5 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 2238dfbe7a 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 395b8e572b 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 8191665fbd 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 53f4612f96 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 16bf50f5db 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards d9c9eb17e2 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards efc986358b 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards ea9d6efa8c 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards ce5c22ba5a 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 6ca751b273 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 56da04e308 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards d4e450c97a 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards c82962e77f 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards b9b8d61998 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 099d0c3aa0 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards f9ca15fdac 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 4751ef482c 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards ca9d1d7638 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 14b9726055 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 80f25fd609 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 5a103a4145 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 9a9743974e 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards ab25cc8955 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 236c722e7a 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 3b783d6937 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards d966e59ff0 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards c0f33b38b3 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 93f5b4c207 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 51f4ddb933 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards de85709f9b 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 2a1cb4c4b1 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards e85a12d4c4 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 7f38d2f678 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 087c7eec76 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 283457d96d 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e80579d106 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b26fce3287 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 3b3316afab 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 7b647c8dc4 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 414633c88b 75: onsuccess: 1: Successful build after linux: 44 commits discards 21dead7c5e 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards af1f40acfe 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a8e95f6ed9 72: onsuccess: 1: Successful build after linux: 12 commits discards c9674fda8b 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards add2fa3235 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards e50c6d4c93 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards c1cc3dd5dd 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9385215b66 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards c3eedd3a68 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards a1452c6a93 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7649969296 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards db42fa2271 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 2f682f693d 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 40d89c7dd7 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards e37c6e409f 60: onsuccess: 1: Successful build after glibc: 2 commits discards 8353c09444 59: onsuccess: 1: Successful build after binutils: 2 commits discards ecf6e70cb3 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 9cddc7233d 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards f2e44cdae5 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0fdc9d1dd7 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 0598beba3b 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards c0a8dd4ac3 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards d2e8149b01 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 42d7d88cbf 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 020bb64890 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b01cc47790 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards c588a28d62 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e4206687dd 47: onsuccess: 1: Successful build after linux: 10 commits discards 73b7d379bc 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 3c34e5e115 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 20b65fe4a2 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 686cd2a69d 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards 691f412538 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards 7660b79e0e 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2b6c95fa1c 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards c55bc547fc 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards ed09cb8c05 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards 2422c73d69 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards cfb18c6765 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 49c2175757 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 5dc3b772fd 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 8f591c56ff 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5aa2fce1fa 32: onsuccess: 1: Successful build after gcc: 7 commits discards 6b3de43fdd 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 79c6d9e413 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 88222fa270 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 94a0d88930 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2c83096f26 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 42ff3ab2b2 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c13750e1f0 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e0fa32c283 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 7be08e90ac 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2bd813101f 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 741d00536c 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 1a85cf02b4 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e531414c60 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f870cbe6c5 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e9469cdcfd 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 90b86f510d 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2bd7f48c90 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 832372cf79 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new ed46be486f 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 55ed90a622 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8c590af119 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 9b078be1e4 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 185a42876e 32: onsuccess: 1: Successful build after gcc: 7 commits new 1cc99d6de1 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d6c8f371e5 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0e1cd5f40e 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 80bc170814 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 457a5e0a10 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 88df5a7d63 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new 7642d25146 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 18860ec347 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new 6df17c9ef5 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2fa8eacf02 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new 0676b0a647 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 515351a855 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 5aeaf681ec 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9d382cdb97 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new fb7706f369 47: onsuccess: 1: Successful build after linux: 10 commits new 2b073d33b9 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b232c9ba4d 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 16c4a7ec78 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 000272c4d6 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9e049155ab 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 8ee8b0549f 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new a52710b82c 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 1886864481 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 982668f64e 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f2e35fb29e 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 3da89673b1 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 2d690d2120 59: onsuccess: 1: Successful build after binutils: 2 commits new 9685c4969b 60: onsuccess: 1: Successful build after glibc: 2 commits new 44723d2c6e 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new fdb6c1e72e 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new eb07ae788f 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 70ef48e125 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2ba3d54ed4 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7dff385b77 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new f8b1f73863 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new e8bc9503ce 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2b474f4f68 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new f6b06504fb 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 62609a844e 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new f57b1a9352 72: onsuccess: 1: Successful build after linux: 12 commits new 04cc44caa7 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3231d7a1b5 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 3b55e073bf 75: onsuccess: 1: Successful build after linux: 44 commits new 3777669df2 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 94c50038cc 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 68163fe3e3 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 15a21bb874 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d56a4c349c 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 558ba61e7a 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 644898eac5 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new b6adea1a40 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new ce9422661f 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 17548ef44a 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 2c8460314f 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new d26490aafa 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new fd890e289a 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 19440b1314 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 1b36c876e4 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 37f4770b12 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 5bcaaf497d 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 0caf937690 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new c3955ab95c 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 95f897f385 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 9d220de1c0 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 3f55498d3c 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 9967dc2e72 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new f406929eaa 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new d162682d1a 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 3fb18f4cdf 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 520f626004 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new f8fb3e5a13 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 302efe03ba 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 70f822d000 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new bc82a4af18 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new a70250b523 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new d2b1ada7ec 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new e30a34ea00 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 2195142926 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 8bbe5d4453 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 94db267807 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 5b139598db 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 3af5a56825 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 70ff20be62 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 1779b44c86 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 12ab650e4e 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 78ccd8ce15 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 2b264694bd 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new d7ea4fe558 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 95dd549be3 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 3de12d5bbe 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 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 (94a8dfb354) \ 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 1704 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 31048 -> 30624 bytes 04-build_abe-stage1/console.log.xz | Bin 72216 -> 72936 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8840 -> 8832 bytes 07-build_abe-glibc/console.log.xz | Bin 239936 -> 239812 bytes 08-build_abe-stage2/console.log.xz | Bin 203024 -> 203132 bytes 09-build_abe-gdb/console.log.xz | Bin 38328 -> 37768 bytes 10-build_abe-qemu/console.log.xz | Bin 31268 -> 31372 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2444 -> 3136 bytes 13-check_regression/console.log.xz | Bin 7280 -> 6308 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 19 + 13-check_regression/mail-body.txt | 39 + 13-check_regression/results.compare | 46 +- 13-check_regression/results.compare2 | 745 +---- 13-check_regression/results.regressions | 39 + 14-update_baseline/console.log | 58 +- 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 | 41 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 39 + sumfiles/g++.log.xz | Bin 3405888 -> 3445444 bytes sumfiles/g++.sum | 321 +- sumfiles/gcc.log.xz | Bin 3032792 -> 3005912 bytes sumfiles/gcc.sum | 5210 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1029764 -> 1028604 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201860 -> 202020 bytes sumfiles/libgomp.sum | 22 +- sumfiles/libitm.log.xz | Bin 2660 -> 2660 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 422808 -> 428724 bytes sumfiles/libstdc++.sum | 16 +- 43 files changed, 3180 insertions(+), 3514 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions