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 3920d93326bc 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/q [...] discards e0a361875528 232: onsuccess: #2480: 1: Success after binutils/gcc/linux [...] discards 1684c468e945 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/q [...] discards 5281c09e6ba5 230: onsuccess: #2477: 1: Success after binutils/gcc/linux [...] discards 6fea4d022fab 229: onsuccess: #2476: 1: Success after binutils/gcc/linux [...] discards 2c304c6a5a39 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/q [...] discards 20ffee17a251 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards bed3f20976a2 226: onsuccess: #2473: 1: Success after binutils/gcc/linux [...] discards 0305867565f7 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards ce5b27a1413a 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: [...] discards 304c145903f7 223: onsuccess: #2470: 1: Success after binutils/gcc/linux [...] discards 5a8c3974c1d1 222: onsuccess: #2469: 1: Success after binutils/gcc/linux [...] discards 6da52110e7dd 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards 507d5b536199 220: onsuccess: #2465: 1: Success after linux: 572 commits discards 8654ca1e6d27 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards 085db6b0e7c3 218: onsuccess: #2461: 1: Success after linux: 916 commits discards e28ccc238a05 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards 2b51e21bc0c5 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards e3cd8b02d8ae 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards 0faf97a2de06 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc [...] discards 1f9e29294936 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: [...] discards 828f6ccd7c31 212: onsuccess: #2451: 1: Success after binutils/gcc/linux [...] discards 60657d20013c 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards 145cf55cfe59 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: [...] discards ce93923de972 209: onsuccess: #2448: 1: Success after binutils/gcc/linux [...] discards 2b321bfe0fb1 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: [...] discards 686bb691496d 207: onsuccess: #2446: 1: Success after binutils/gcc/linux [...] discards f54f9db3948d 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc [...] discards 39f22d8afa23 205: onsuccess: #2444: 1: Success after binutils/gcc/linux [...] discards dc727fb608d8 204: onsuccess: #2435: 1: Success after linux: 3 commits discards de57565ba26c 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards 1ac1d7887636 202: onsuccess: #2431: 1: Success after linux: 944 commits discards d3e67fdf3afd 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards e106017ae43a 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards 0fa2e500a2db 199: onsuccess: #2363: 1: Success after binutils/gcc/linux [...] discards a40edc298082 198: onsuccess: #2360: 1: Success after binutils/gcc/linux [...] discards ef70baed61f1 197: onsuccess: #2348: 1: Success after linux: 190 commits discards da9d76830a7d 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: [...] discards 1bbee6225568 195: onsuccess: #2341: 1: Success after binutils/gcc/linux [...] discards 8d1fa7deaf20 194: onsuccess: #2340: 1: Success after binutils/gcc/linux [...] discards 62c3a5f70495 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc [...] discards 4cd6828bcde8 192: onsuccess: #2338: 1: Success after binutils/gcc/linux [...] discards 6f169e1029df 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards 0b9688854c53 190: onsuccess: #2330: 1: Success after binutils/gcc/linux [...] discards c08aa138e38b 189: onsuccess: #2299: 1: Success after binutils/gcc/linux [...] discards e86e9b3ffcf3 188: onsuccess: #2295: 1: Success after binutils/gcc/linux [...] discards 6deb4aa4a9f0 187: onsuccess: #2294: 1: Success after binutils/gcc/linux [...] discards 39f8d697c5cd 186: onsuccess: #2291: 1: Success after binutils/gcc/linux [...] discards 2169f8321ca9 185: onsuccess: #2290: 1: Success after binutils/gcc/linux [...] discards 9b2f421da0d9 184: onsuccess: #2288: 1: Success after binutils/gcc/linux [...] discards 8304d271f33b 183: onsuccess: #2270: 1: Success after binutils/gcc/linux [...] discards fa60c2c23125 182: onsuccess: #2247: 1: Success after binutils/gcc/linux [...] discards 9510ea580f3c 181: onsuccess: #2239: 1: Success after binutils/gcc/linux [...] discards d2943be5a315 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc [...] discards bfe690db4bd1 179: onsuccess: #2230: 1: Success after binutils/gcc/linux [...] discards 949a7de5e3c9 178: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] discards 696b516fe725 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards 31a970f7021e 176: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] discards ce01188d880d 175: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] discards 752cd56036cc 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: [...] discards 5d9323ab7585 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 607094718fcc 172: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] discards c663576d1a86 171: onsuccess: #2206: 1: Success after binutils/gcc/linux [...] discards 4296b82838fb 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc [...] discards ec9b5311a207 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc [...] discards fade38242c97 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc [...] discards caa3fb6eea5f 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qe [...] discards e8b72ce02f30 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 [...] discards 5df8305c275b 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 9dc66131afb0 164: onsuccess: #2199: 1: Success after binutils/gcc/linux [...] discards b813011f8503 163: onsuccess: #2198: 1: Success after binutils/gcc/linux [...] discards 4f5f74b0759b 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc [...] discards c28a2637c4af 161: onsuccess: #2196: 1: Success after binutils/gcc/linux [...] discards 7cad5c155e79 160: onsuccess: #2195: 1: Success after binutils/gcc/linux [...] discards 2913672251e8 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 1 [...] discards dedbecaf689c 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc [...] discards 5ba0e6b72bf5 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: [...] discards 6cb928b461bb 156: onsuccess: #2191: 1: Success after binutils/gcc/linux [...] discards 3c392eb74c49 155: onsuccess: #2190: 1: Success after binutils/gcc/linux [...] discards b971614861b7 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: [...] discards 56808cb84ce7 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: [...] discards 1194076a6d3a 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 2 [...] discards 99c2581cabda 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 45d2f0722112 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 14e959d416d3 149: onsuccess: #2184: 1: Success after binutils/gcc/linux [...] discards 9846a92d6e7f 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 6 [...] discards 259ff32a2ab9 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: [...] discards d5b77105b37f 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb [...] discards 50a8d29db5c3 145: onsuccess: #2180: 1: Success after binutils/gcc/linux [...] discards 0230b7d5bf84 144: onsuccess: #2179: 1: Success after binutils/gcc/linux [...] discards 8c5d6efdfd6e 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/q [...] discards 7a4a6160c992 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 4a00c3d79373 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: [...] discards 3020d7b85504 140: onsuccess: #2175: 1: Success after binutils/gcc/linux [...] discards 2a52af7c6f4e 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: [...] discards 15167ffdeabe 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: [...] discards b18f91b88867 137: onsuccess: #2172: 1: Success after binutils/gcc/linux [...] discards 018483b13845 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/q [...] discards d82fca74bf88 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 [...] discards 891708a7167a 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: [...] discards 8469396760d9 133: onsuccess: #2168: 1: Success after binutils/gcc/linux [...] new bb5c785a25f4 133: onsuccess: #2168: 1: Success after binutils/gcc/linux [...] new c738c8f40945 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: [...] new 898747d9a0b5 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 [...] new 0ce48efebe6c 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/q [...] new c89ccef1c16a 137: onsuccess: #2172: 1: Success after binutils/gcc/linux [...] new 8248c921eac6 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: [...] new 926b7f33801a 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: [...] new 92583adf52a5 140: onsuccess: #2175: 1: Success after binutils/gcc/linux [...] new 0fe8a1ee2767 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: [...] new 77d2c3bce187 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 4fe6b7bcc18f 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/q [...] new db4f7698d6a4 144: onsuccess: #2179: 1: Success after binutils/gcc/linux [...] new 677cb66040c2 145: onsuccess: #2180: 1: Success after binutils/gcc/linux [...] new 4a070f4f3a27 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb [...] new d633bb54de86 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: [...] new f5b3ad9921ea 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 6 [...] new dfb7bd29e10b 149: onsuccess: #2184: 1: Success after binutils/gcc/linux [...] new 1e279c6d3563 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 0f2caf2555fa 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 1f35ef60a200 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 2 [...] new 882965d303a5 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: [...] new 1ed1429afc19 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: [...] new 0209a1e2fb26 155: onsuccess: #2190: 1: Success after binutils/gcc/linux [...] new fb03d2d0023d 156: onsuccess: #2191: 1: Success after binutils/gcc/linux [...] new eeddc3c034dd 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: [...] new 2d363c30767d 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc [...] new 72a286da56f1 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 1 [...] new 62c6ea3f2d5d 160: onsuccess: #2195: 1: Success after binutils/gcc/linux [...] new df4c7b3d089a 161: onsuccess: #2196: 1: Success after binutils/gcc/linux [...] new a2fab2bfec9e 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc [...] new 2cb868594fbd 163: onsuccess: #2198: 1: Success after binutils/gcc/linux [...] new 431d89b0f4dd 164: onsuccess: #2199: 1: Success after binutils/gcc/linux [...] new c4153ea97469 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 234468194013 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 [...] new 9f0aa7ec89f0 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qe [...] new 3daa7ffead2e 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc [...] new 3104956bfdfe 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc [...] new 2fb6174fbb60 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc [...] new 8d4890da199a 171: onsuccess: #2206: 1: Success after binutils/gcc/linux [...] new b655daf71db5 172: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] new 197593ec44be 173: onsuccess: #2208: 1: Success after gcc: 10 commits new 9a114d9ef684 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: [...] new 7e13ba5ae199 175: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] new a71cb8c54857 176: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] new 1451c1d1b445 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new 93f3e3ad9c9b 178: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] new e38db73e939a 179: onsuccess: #2230: 1: Success after binutils/gcc/linux [...] new 4680c7ce8bec 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc [...] new 552ce1429939 181: onsuccess: #2239: 1: Success after binutils/gcc/linux [...] new 5b235b1e73fc 182: onsuccess: #2247: 1: Success after binutils/gcc/linux [...] new 2628d7a18947 183: onsuccess: #2270: 1: Success after binutils/gcc/linux [...] new 3cc5dbf3f68c 184: onsuccess: #2288: 1: Success after binutils/gcc/linux [...] new d7045841e9e5 185: onsuccess: #2290: 1: Success after binutils/gcc/linux [...] new b363c8b4e45f 186: onsuccess: #2291: 1: Success after binutils/gcc/linux [...] new 3be796bcf963 187: onsuccess: #2294: 1: Success after binutils/gcc/linux [...] new f9241927099c 188: onsuccess: #2295: 1: Success after binutils/gcc/linux [...] new 42de3670c615 189: onsuccess: #2299: 1: Success after binutils/gcc/linux [...] new 714e78af139a 190: onsuccess: #2330: 1: Success after binutils/gcc/linux [...] new db20c4f374fd 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new e6b0c1f889a9 192: onsuccess: #2338: 1: Success after binutils/gcc/linux [...] new 9aba0821cf19 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc [...] new 7be37e225cad 194: onsuccess: #2340: 1: Success after binutils/gcc/linux [...] new 221f27d599c8 195: onsuccess: #2341: 1: Success after binutils/gcc/linux [...] new e3633db1d663 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: [...] new 1ce4b74a1a20 197: onsuccess: #2348: 1: Success after linux: 190 commits new a707b5b2ae3c 198: onsuccess: #2360: 1: Success after binutils/gcc/linux [...] new d6ba0909861c 199: onsuccess: #2363: 1: Success after binutils/gcc/linux [...] new d2b5e7e4501a 200: onsuccess: #2427: 1: Success after binutils: 274 commits new fde600b0eb8c 201: onsuccess: #2430: 1: Success after glibc: 26 commits new c2dcbd65da99 202: onsuccess: #2431: 1: Success after linux: 944 commits new 8d0f1da0397a 203: onsuccess: #2433: 1: Success after binutils: 27 commits new 1a523d1fae6a 204: onsuccess: #2435: 1: Success after linux: 3 commits new 467ee76be507 205: onsuccess: #2444: 1: Success after binutils/gcc/linux [...] new 5c8961ee4015 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc [...] new 7e8c5a4a8678 207: onsuccess: #2446: 1: Success after binutils/gcc/linux [...] new 7c4dc103c2c9 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: [...] new 32dc6edf67a5 209: onsuccess: #2448: 1: Success after binutils/gcc/linux [...] new b5fc36c5951a 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: [...] new f959826c2923 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new 5b6f2c84dcde 212: onsuccess: #2451: 1: Success after binutils/gcc/linux [...] new cf1501437b89 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: [...] new 9bebbc9ada98 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc [...] new adc792cbae3a 215: onsuccess: #2455: 1: Success after binutils: 3 commits new b82efa7cec77 216: onsuccess: #2457: 1: Success after linux: 1736 commits new bf46f5935291 217: onsuccess: #2459: 1: Success after binutils: 3 commits new 5ec2b3383648 218: onsuccess: #2461: 1: Success after linux: 916 commits new 0fbe37ce36ec 219: onsuccess: #2463: 1: Success after binutils: 3 commits new 4f8b690df6b6 220: onsuccess: #2465: 1: Success after linux: 572 commits new a9da820af5ae 221: onsuccess: #2467: 1: Success after binutils: 3 commits new b454c414630d 222: onsuccess: #2469: 1: Success after binutils/gcc/linux [...] new 789686712d0e 223: onsuccess: #2470: 1: Success after binutils/gcc/linux [...] new ef6715bf9063 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: [...] new 7e665a1bd813 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new 9126899afc71 226: onsuccess: #2473: 1: Success after binutils/gcc/linux [...] new 6ea41f5872ba 227: onsuccess: #2474: 1: Success after gcc: 2 commits new 0f620649397c 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/q [...] new 1edde54cf84e 229: onsuccess: #2476: 1: Success after binutils/gcc/linux [...] new 26c7c7ffb401 230: onsuccess: #2477: 1: Success after binutils/gcc/linux [...] new 8cb36cbf3524 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/q [...] new 75e5b40fa045 232: onsuccess: #2480: 1: Success after binutils/gcc/linux [...] new ad87fb95b4b6 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/q [...] new 207e17e93701 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 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 (3920d93326bc) \ 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 1760 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31960 -> 32948 bytes 04-build_abe-stage1/console.log.xz | Bin 73492 -> 73124 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8696 -> 8696 bytes 07-build_abe-glibc/console.log.xz | Bin 244712 -> 243424 bytes 08-build_abe-stage2/console.log.xz | Bin 205812 -> 204344 bytes 09-build_abe-gdb/console.log.xz | Bin 39120 -> 39640 bytes 10-build_abe-qemu/console.log.xz | Bin 32136 -> 31444 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3908 -> 3912 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2948 -> 2868 bytes 13-check_regression/console.log.xz | Bin 13184 -> 10684 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 104 +- 13-check_regression/mail-body.txt | 244 +- 13-check_regression/results.compare | 209 +- 13-check_regression/results.compare2 | 1837 ++++------ 13-check_regression/results.regressions | 142 +- 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 246 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 142 +- sumfiles/g++.log.xz | Bin 3429720 -> 3411632 bytes sumfiles/g++.sum | 174 +- sumfiles/gcc.log.xz | Bin 3043248 -> 3034356 bytes sumfiles/gcc.sum | 5686 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1046088 -> 1037988 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 214620 -> 214596 bytes sumfiles/libgomp.sum | 21 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 437308 -> 426080 bytes sumfiles/libstdc++.sum | 25 +- 42 files changed, 4206 insertions(+), 4784 deletions(-)