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 a3a1e4eefc 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards fff0f9787f 124: onsuccess: #2159: 1: Success after linux: 23 commits discards cebf7285b4 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards b2a81e80b2 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards c8ec99db87 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 4b05c9322d 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 2b4281f17e 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 0c8bc4a054 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 39842d531e 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 76ff89c8d0 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 8a659a8722 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards ffb4412d36 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards da9fd314b8 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards dfe7732a80 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 5896286337 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 42c546951f 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards eb9a7317e1 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards acb121d703 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 230a7cae0a 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards dad85823bc 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 5e2b7e8225 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards a33321d67d 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 819df42ca2 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 113ea1e2cf 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 74811c3235 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards e3039a6188 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards e16e99fd88 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 5ed5f20bcb 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards e0ed65decc 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 4ec56644df 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards eec0268d2d 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards bdcbf60663 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 10dbc80279 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards e41f6081f9 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 50d9b7f461 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards d0e64cf2e0 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards fc97cd7643 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards c4baadd7b6 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards c7b2a455b9 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards aac0539fc5 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 71a7614d4a 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards d2ccb1c0e9 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards a1c8cbb475 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 5720c3145e 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 242bbac42c 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 663576ef23 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ce117ef138 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 1372019d46 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards b0703aaae5 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards f017ad3e37 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dbf21dff70 75: onsuccess: 1: Successful build after linux: 44 commits discards ce4fcadf37 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards b9a8e43603 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a226172834 72: onsuccess: 1: Successful build after linux: 12 commits discards 5cb0e9ec50 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards f885c6c37f 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards eaedf22485 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 88595acd34 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8d673d8c42 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards a4ab6d6b3f 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards dd25daa6a9 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7040effe9b 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6047bf6f17 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 2c0bd44bac 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 1b72a80e8a 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 5526706972 60: onsuccess: 1: Successful build after glibc: 2 commits discards d408a8f0d2 59: onsuccess: 1: Successful build after binutils: 2 commits discards a8feedc7fc 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 4b7138bb9c 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d3d0985a93 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b4b9461797 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 035ac8cdcd 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 38bc67f4ba 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 1c69824fca 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 422945859e 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dd3e264408 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 95970ced2d 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 2c170665b5 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a41a39c403 47: onsuccess: 1: Successful build after linux: 10 commits discards 447aebf2f1 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 7916d41dd6 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d136447259 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 689c3e5723 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards 53ac2935c1 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards cbe282539c 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4d61bc61c9 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards e2247072c3 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 9345cc3d18 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards 639e335cc0 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 42d27cc6dd 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7957fae7a3 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 6031d09932 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d1e01f3919 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards abed66615a 32: onsuccess: 1: Successful build after gcc: 7 commits discards bc41245124 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 4fe2f2f4de 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 053222461c 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ee8fd854c9 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 069c10806c 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 17033be1fb 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b268ed6759 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 85c343535b 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e7bd6c200d 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 310008f7bf 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new e0dd0e76f6 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 7a41c557b6 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9652ad97f0 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 52b0f68c8b 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new eb83a04bdb 32: onsuccess: 1: Successful build after gcc: 7 commits new 2a10412459 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 17fedaacbe 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 73ab8ef110 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 421ece6990 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4c85568556 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4364cb16e0 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new 43564239d5 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 5f625c669e 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new f8c9a1e0e0 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d2eafa30d3 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new d401564393 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new b819d6822b 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 6f35fa5fdc 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9e64ab725b 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new c93f3338f9 47: onsuccess: 1: Successful build after linux: 10 commits new ad15a44f4f 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ca2e9b33f7 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 31e07434b2 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b8e69a2be9 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 59830293c5 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new df9db953f6 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new b51813d2e6 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new efc3dacd6d 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 49fbd2dadb 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new abb9b71719 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 3c6eeaf12b 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new f077496a8f 59: onsuccess: 1: Successful build after binutils: 2 commits new 667e4e4e48 60: onsuccess: 1: Successful build after glibc: 2 commits new 7c7cabbe28 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 7b37ca48b1 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 70de96faf7 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new a9aa6f7e04 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2f63d43944 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new fedbf3aa0a 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 8ba0ffb1ae 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new e548447aa7 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 11cf3d0d36 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 41b58ddae1 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new e8e7762060 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new ac2db92ff5 72: onsuccess: 1: Successful build after linux: 12 commits new 33400b072e 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e961de9b83 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new c27cb850fd 75: onsuccess: 1: Successful build after linux: 44 commits new 71f4c39cb6 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 15409e7866 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 889a6bf076 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 2ef46d2a6e 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d9e17f20f9 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 03be8b6424 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new c880c3302e 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 27fa22280b 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 1b27613c65 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 225b629f5d 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 23e364f375 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 1770b87729 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 8a8a06c0a2 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new ba03b965ba 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 525c55016b 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 96620d686b 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new e6963b9b40 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 078afcf7ee 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new dc5c0885d4 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 6ecf0698d2 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 7af997fef9 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 692f2dc25c 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new a0a34fc74d 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 6159085217 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 9dfbdd7311 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 2b307df706 101: onsuccess: #2130: 1: Success after binutils: 81 commits new bd3ee65013 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 4c7dd7ece8 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new d24d390516 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new c3f4942fd9 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 2154dbc9b0 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 4dc66b83c9 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new eac2efc280 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new ec3fd1267d 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 53267de14f 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 5bb9475ff3 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new a629077412 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 7446cb1f47 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 522b6758fe 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 0f873d5884 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new e621330cfc 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 11af5b3761 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new c05acae243 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new d6622ff03c 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 830a742cb6 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new ca8cb98958 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 168e545b0f 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 685121532d 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 234254afcd 124: onsuccess: #2159: 1: Success after linux: 23 commits new 9d66a90960 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 7398c9ef7a 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...]
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 (a3a1e4eefc) \ 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 1712 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30208 -> 30312 bytes 04-build_abe-stage1/console.log.xz | Bin 72188 -> 72436 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8696 -> 8664 bytes 07-build_abe-glibc/console.log.xz | Bin 240300 -> 240864 bytes 08-build_abe-stage2/console.log.xz | Bin 202972 -> 202968 bytes 09-build_abe-gdb/console.log.xz | Bin 37340 -> 37420 bytes 10-build_abe-qemu/console.log.xz | Bin 31412 -> 31440 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2452 -> 2612 bytes 13-check_regression/console.log.xz | Bin 6172 -> 5984 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 9 +- 13-check_regression/mail-body.txt | 69 +- 13-check_regression/results.compare | 43 +- 13-check_regression/results.compare2 | 53 +- 13-check_regression/results.regressions | 43 +- 14-update_baseline/console.log | 68 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 71 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 43 +- sumfiles/g++.log.xz | Bin 3435088 -> 3401364 bytes sumfiles/g++.sum | 181 +- sumfiles/gcc.log.xz | Bin 3013276 -> 3028260 bytes sumfiles/gcc.sum | 4274 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1024616 -> 1028752 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202012 -> 202152 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2656 -> 2660 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 421072 -> 429248 bytes sumfiles/libstdc++.sum | 18 +- 41 files changed, 2570 insertions(+), 2408 deletions(-)