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 7398c9ef7a 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 9d66a90960 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 234254afcd 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 685121532d 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 168e545b0f 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards ca8cb98958 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 830a742cb6 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards d6622ff03c 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards c05acae243 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 11af5b3761 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards e621330cfc 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 0f873d5884 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 522b6758fe 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 7446cb1f47 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards a629077412 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 5bb9475ff3 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 53267de14f 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards ec3fd1267d 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards eac2efc280 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 4dc66b83c9 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 2154dbc9b0 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards c3f4942fd9 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards d24d390516 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 4c7dd7ece8 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards bd3ee65013 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 2b307df706 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 9dfbdd7311 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 6159085217 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards a0a34fc74d 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 692f2dc25c 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 7af997fef9 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 6ecf0698d2 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards dc5c0885d4 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 078afcf7ee 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards e6963b9b40 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 96620d686b 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 525c55016b 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards ba03b965ba 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 8a8a06c0a2 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 1770b87729 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 23e364f375 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 225b629f5d 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 1b27613c65 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 27fa22280b 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards c880c3302e 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 03be8b6424 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards d9e17f20f9 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2ef46d2a6e 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 889a6bf076 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 15409e7866 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 71f4c39cb6 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c27cb850fd 75: onsuccess: 1: Successful build after linux: 44 commits discards e961de9b83 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 33400b072e 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ac2db92ff5 72: onsuccess: 1: Successful build after linux: 12 commits discards e8e7762060 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 41b58ddae1 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 11cf3d0d36 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards e548447aa7 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8ba0ffb1ae 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards fedbf3aa0a 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 2f63d43944 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a9aa6f7e04 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 70de96faf7 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 7b37ca48b1 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 7c7cabbe28 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 667e4e4e48 60: onsuccess: 1: Successful build after glibc: 2 commits discards f077496a8f 59: onsuccess: 1: Successful build after binutils: 2 commits discards 3c6eeaf12b 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards abb9b71719 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 49fbd2dadb 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards efc3dacd6d 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards b51813d2e6 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards df9db953f6 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 59830293c5 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards b8e69a2be9 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 31e07434b2 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ca2e9b33f7 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards ad15a44f4f 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c93f3338f9 47: onsuccess: 1: Successful build after linux: 10 commits discards 9e64ab725b 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 6f35fa5fdc 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b819d6822b 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards d401564393 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards d2eafa30d3 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards f8c9a1e0e0 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5f625c669e 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards 43564239d5 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 4364cb16e0 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards 4c85568556 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 421ece6990 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 73ab8ef110 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 17fedaacbe 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2a10412459 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards eb83a04bdb 32: onsuccess: 1: Successful build after gcc: 7 commits discards 52b0f68c8b 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 9652ad97f0 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 7a41c557b6 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e0dd0e76f6 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 310008f7bf 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards e7bd6c200d 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c5ad403a52 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c3a6c1184c 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 722f534308 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 6df1057457 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 75c585ab2b 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 7929e2b22b 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ebf3600571 32: onsuccess: 1: Successful build after gcc: 7 commits new a0c343b33d 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 65809ee9f9 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 04fafe275e 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0332da96cb 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new de1dd49adb 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 17bc107a18 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new c71beef93a 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 7e4a13dfcc 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new 51bb2ad42d 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 348495b81e 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new 05c99aeda7 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 4adf019850 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 3d0a81cbe3 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6cbfac6eb8 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 743a6b44f9 47: onsuccess: 1: Successful build after linux: 10 commits new 7ac59cf51f 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9b85c461a9 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new cdc41acf0b 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 90bfefc24f 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 51048f5cd7 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new c6f779c249 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new ff0c600bb5 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new d234819837 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 01252187a6 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7f2bf93b94 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 791f28f6bc 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new f898a2a8ad 59: onsuccess: 1: Successful build after binutils: 2 commits new d5da5257d4 60: onsuccess: 1: Successful build after glibc: 2 commits new d447fd8bd5 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new fe19b0fc25 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 35f9d016bc 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 6169662f7e 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b13d331792 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 469c329fb0 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new bf03d09766 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 24ee5de0f9 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4aacfd28d6 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 3b1783027a 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 81a51cf9d3 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new f742c2f18b 72: onsuccess: 1: Successful build after linux: 12 commits new 2d46ee1faf 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b6b25c8b62 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 155fbdb2b2 75: onsuccess: 1: Successful build after linux: 44 commits new 1fa2f105bb 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fd5997f2ac 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new a48c13be98 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new f51c93f233 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new ee87f56831 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 20aced68bc 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 8cf09ff864 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 6bf8d1bd76 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 42023fc28c 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 5b43ed60dc 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 75769551d2 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 7d605e9ca0 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 24c0d84f21 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 77651ba5f8 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new a470b747b0 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new cf7a655f03 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 2f39bcd0b4 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 37bdf91a4b 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new d98550b35a 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 3d8fb56421 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 942f13746b 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 59945b3fa1 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 85f0f35ecd 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 3aea75f813 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 50a43eb4f7 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 78985b8781 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 40cebb770a 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 1fb4a04d24 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 1725c00de9 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new e5d1f8eb76 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new d5453e82ea 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 7cb3b260e9 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new ae80fcbd6c 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new dd8bc8962c 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new cd5fd3ced9 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 4e408870d1 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 5c46d9485d 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new f666ccd97c 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 1d2a4c621b 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 02d927a194 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new ec3b6066c2 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 4e747155ec 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 788f1dea76 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 64afae6b98 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 76ef6aac5b 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 4aa9f49cdd 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 612c4ec723 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 5426f12bdd 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 393ed254c7 124: onsuccess: #2159: 1: Success after linux: 23 commits new 0bc73929b9 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 648e4028d9 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 2b91244e05 127: onsuccess: #2162: 1: Success after gcc: 9 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 (7398c9ef7a) \ 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 1724 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30312 -> 30132 bytes 04-build_abe-stage1/console.log.xz | Bin 72436 -> 72428 bytes 06-build_abe-linux/console.log.xz | Bin 8664 -> 8668 bytes 07-build_abe-glibc/console.log.xz | Bin 240864 -> 239660 bytes 08-build_abe-stage2/console.log.xz | Bin 202968 -> 203664 bytes 09-build_abe-gdb/console.log.xz | Bin 37420 -> 37180 bytes 10-build_abe-qemu/console.log.xz | Bin 31440 -> 31232 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2612 -> 2888 bytes 13-check_regression/console.log.xz | Bin 5984 -> 7384 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 32 +- 13-check_regression/mail-body.txt | 100 +- 13-check_regression/results.compare | 57 +- 13-check_regression/results.compare2 | 309 +- 13-check_regression/results.regressions | 57 +- 14-update_baseline/console.log | 68 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 102 +- mail/mail-subject.txt | 2 +- manifest.sh | 22 +- results | 57 +- sumfiles/g++.log.xz | Bin 3401364 -> 3438748 bytes sumfiles/g++.sum | 191 +- sumfiles/gcc.log.xz | Bin 3028260 -> 3009796 bytes sumfiles/gcc.sum | 4705 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1028752 -> 1026840 bytes sumfiles/gfortran.sum | 236 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202152 -> 202204 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2660 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 429248 -> 418544 bytes sumfiles/libstdc++.sum | 8 +- 40 files changed, 3376 insertions(+), 2584 deletions(-)