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 67851a3a25 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] discards 2b8500e71c 197: onsuccess: #2348: 1: Success after linux: 190 commits discards 066c8652d4 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] discards ce931d86e7 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] discards 3d4a5acfc9 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] discards 8132e02cdf 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] discards 3117d32adf 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] discards 981a72a170 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards 8a736e702e 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] discards ebd5463179 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] discards 5f9691a066 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] discards 27b9f6cfde 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] discards a09fd91123 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] discards 132b6bdaf2 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] discards d011156889 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] discards eaefdfdc2a 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] discards 907b3e2275 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] discards 78feedb726 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] discards ddec1f30a8 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] discards d5eb583956 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] discards 77c7f0cdb3 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 1629808b51 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards bbcaa150f5 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 0bd017d6ca 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 7ea64ab81f 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] discards 7c7b9f4850 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 41ff22f501 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 44972995f6 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards 37e10ba978 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards 32713b1c3e 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards e421a67116 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards aadd80c320 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards 4c9cac08cd 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards 905525e38c 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 76ddde8e86 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards cf16d25c97 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards 18164824a2 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards 2445d2b49b 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards 0b8e35c4a1 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 3dca5797fd 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards 17468a7192 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 5fb259007a 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards 77a4fb329a 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards fc344932e2 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards e7021505fa 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards f7fceb41d6 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 21a45b8b0a 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 424e975f68 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards f2b4907206 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 73a41822aa 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards e28b7c7c7c 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 5948e8d582 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 1caa1cda6a 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 456f928c91 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 25d6a28532 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards a6725ed2cb 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 7249a32999 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards d436353eb5 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 4c4c49fd61 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 8f4a5d3545 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards cd349df131 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards a53f1e1e46 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 8b547b9ab4 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards f3345d0c37 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards c9b5f609d4 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 1c4c2781a4 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 31419a566b 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards b18606808e 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 2efe8b00c9 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards f26b8fb3d9 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 4142716f3f 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 0c1c01472b 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 151fabde82 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 1451fef41b 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards a1cd563d03 124: onsuccess: #2159: 1: Success after linux: 23 commits discards d752cd8086 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 82e670ba8c 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 80d8e31893 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 0db98ef53c 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 3665a98b5a 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 9219635765 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 764767072a 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards e1bfb5bc1b 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards c3c161a27d 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 4394cc2d1c 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards cd3277c532 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 3e16397dfd 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards e3700260d5 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 73760d1d30 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards e0122567ac 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 716b8ae25a 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards abce38dea2 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards c922352e3b 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 94fe858e39 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards d538494860 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 91ebf37f82 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 317c8f565b 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards daed771369 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 7af235f696 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards ff7c2100e0 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards c33b2b6814 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 05161f1435 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 6956918f50 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 64ca8cf6d7 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new e761148c67 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 0af274f051 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new b627346eb8 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 0b99cc09a7 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new e48e07129f 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 752664b25f 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 1f80318ae8 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 43dd5df153 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 27a9f48cc0 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 09fd6501ee 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 64c01f7c76 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new fe0d5620ba 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 4fa30726af 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new a9639ba093 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 0168873f43 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 840ad32455 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new e6afb6600a 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new dbbfcb4553 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 50a611f231 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new a8e391989a 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new c6d0065608 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 0bbae261e0 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new bee24c36da 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 44f978faa1 124: onsuccess: #2159: 1: Success after linux: 23 commits new 745b76fcb9 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 6621af8bad 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 68cb2a8645 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 2a86e42539 128: onsuccess: #2163: 1: Success after linux: 23 commits new 85ae69ba59 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 49989eac24 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new ec6201f0ec 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 26aa2787ba 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 1541cbdf8d 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new eae13e0390 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new accd56b868 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 5a6581d4f5 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 917aadf7c7 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 4d269acfcd 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 319dbee9d0 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 8a54143a36 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 9b4ba5b235 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new a45c6d5b82 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new b1af3bdfe1 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new f1ced28e94 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new df3475edd1 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 63a7897e83 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new d84cfdcaf6 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new c25a80f559 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new aa2b27893c 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new ea6d58e90f 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 9c6ec3cb84 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 8c4223f52f 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 0ad837890f 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new bb717a4a9e 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 46158e37f3 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 12e44d2c99 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 06c6fcb083 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new 0f3b8a7c7d 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 01cfc18165 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new bbcde2fec0 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 193fa1a003 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new 060955ee0d 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new c764fdf401 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new 407a22dd70 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new 9c25076912 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 4f55c23551 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new ac36101f7b 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new 5db8e72e47 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new aae87a16b7 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new ee2f001119 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new bcc3515800 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new e88cd9316f 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new b70dd9813b 173: onsuccess: #2208: 1: Success after gcc: 10 commits new c69d75d5b9 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new 55cc7e1708 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 053ae92e31 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 88ebdc8f44 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new f11c252510 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 217639cd39 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] new 507d51780a 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] new 8962d5fadc 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] new 947cfc8e36 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] new 181e634c4f 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] new eef72ea961 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] new c5c07c5881 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] new 68e25d9771 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] new 69c3773e5d 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] new 7abda79115 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] new 9b5fd3f94c 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] new 454c705954 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] new 44a2dd0fdc 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new aad591d4c2 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] new 43c4c74be1 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] new 3507b5b03e 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] new 66dccdbbb3 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] new be1d237b4a 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] new 6871dfc41b 197: onsuccess: #2348: 1: Success after linux: 190 commits new fdf2365058 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] new 7eb90b4a3e 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/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 (67851a3a25) \ 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 1728 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30696 -> 30436 bytes 04-build_abe-stage1/console.log.xz | Bin 73000 -> 72616 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8340 -> 8612 bytes 07-build_abe-glibc/console.log.xz | Bin 244268 -> 244268 bytes 08-build_abe-stage2/console.log.xz | Bin 203532 -> 203504 bytes 09-build_abe-gdb/console.log.xz | Bin 37876 -> 37804 bytes 10-build_abe-qemu/console.log.xz | Bin 31300 -> 31664 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3900 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2836 -> 2672 bytes 13-check_regression/console.log.xz | Bin 11600 -> 14048 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 77 +- 13-check_regression/mail-body.txt | 179 +- 13-check_regression/results.compare | 109 +- 13-check_regression/results.compare2 | 2246 +++++++++++---- 13-check_regression/results.regressions | 109 +- 14-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 181 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 109 +- sumfiles/g++.log.xz | Bin 3438172 -> 3459628 bytes sumfiles/g++.sum | 1816 ++++++------ sumfiles/gcc.log.xz | Bin 3057456 -> 3048728 bytes sumfiles/gcc.sum | 4616 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1039284 -> 1034916 bytes sumfiles/gfortran.sum | 96 +- sumfiles/libatomic.log.xz | Bin 2300 -> 2292 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213648 -> 213544 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 428312 -> 428904 bytes sumfiles/libstdc++.sum | 20 +- 45 files changed, 5314 insertions(+), 4368 deletions(-)