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 74bd4f2acc8e 232: onsuccess: #2480: 1: Success after binutils/gcc/linux [...] discards 8dc888efb189 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/q [...] discards 580ca7d97d1b 230: onsuccess: #2477: 1: Success after binutils/gcc/linux [...] discards ceea8013aca8 229: onsuccess: #2476: 1: Success after binutils/gcc/linux [...] discards 8faedf84fa3f 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/q [...] discards 35b07478cfc6 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards 71540756e443 226: onsuccess: #2473: 1: Success after binutils/gcc/linux [...] discards c192d8fdfd67 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards d03a20859f5b 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: [...] discards 741d9dccbf27 223: onsuccess: #2470: 1: Success after binutils/gcc/linux [...] discards d5d774f2c1e5 222: onsuccess: #2469: 1: Success after binutils/gcc/linux [...] discards 7850eb946d70 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards f98a955ba228 220: onsuccess: #2465: 1: Success after linux: 572 commits discards 1b9a5871a54a 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards 04abb5fe987d 218: onsuccess: #2461: 1: Success after linux: 916 commits discards 9c43834f7168 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards 82ed7f2aedd9 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards 74f233b0d6fd 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards 69b71bb6a3a6 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc [...] discards 28428008a97c 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: [...] discards 65d731de9652 212: onsuccess: #2451: 1: Success after binutils/gcc/linux [...] discards 9332d7099ebf 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards b58cc72070fa 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: [...] discards 363bfdf92b11 209: onsuccess: #2448: 1: Success after binutils/gcc/linux [...] discards ba0599025c54 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: [...] discards 37acfb3158f1 207: onsuccess: #2446: 1: Success after binutils/gcc/linux [...] discards 33dbcd2961d0 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc [...] discards 85827b369248 205: onsuccess: #2444: 1: Success after binutils/gcc/linux [...] discards 4c85815f30cd 204: onsuccess: #2435: 1: Success after linux: 3 commits discards efe2994d33ea 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards a5e478bc672c 202: onsuccess: #2431: 1: Success after linux: 944 commits discards d1095862de14 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards dfb2edd74ab0 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards 8c66667cc8a7 199: onsuccess: #2363: 1: Success after binutils/gcc/linux [...] discards fbfd4f02e1aa 198: onsuccess: #2360: 1: Success after binutils/gcc/linux [...] discards 1e99b5e506c9 197: onsuccess: #2348: 1: Success after linux: 190 commits discards 9c5346abfdb0 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: [...] discards 4cdf0685e768 195: onsuccess: #2341: 1: Success after binutils/gcc/linux [...] discards ce5dafb8fcd4 194: onsuccess: #2340: 1: Success after binutils/gcc/linux [...] discards 755163e6dd37 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc [...] discards 37e5ebc8f3ed 192: onsuccess: #2338: 1: Success after binutils/gcc/linux [...] discards 4e25fb5392ea 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards dd89b6cea107 190: onsuccess: #2330: 1: Success after binutils/gcc/linux [...] discards bdd1f51f1e3a 189: onsuccess: #2299: 1: Success after binutils/gcc/linux [...] discards 065fc02c85cb 188: onsuccess: #2295: 1: Success after binutils/gcc/linux [...] discards 68288ac36924 187: onsuccess: #2294: 1: Success after binutils/gcc/linux [...] discards 44922c1e927c 186: onsuccess: #2291: 1: Success after binutils/gcc/linux [...] discards f719b4115454 185: onsuccess: #2290: 1: Success after binutils/gcc/linux [...] discards 27ed5793c0ce 184: onsuccess: #2288: 1: Success after binutils/gcc/linux [...] discards 19a5fcda85f5 183: onsuccess: #2270: 1: Success after binutils/gcc/linux [...] discards 9d1b38662bd6 182: onsuccess: #2247: 1: Success after binutils/gcc/linux [...] discards 4c859afb083d 181: onsuccess: #2239: 1: Success after binutils/gcc/linux [...] discards 1344e10d93b7 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc [...] discards ebd7129c0b72 179: onsuccess: #2230: 1: Success after binutils/gcc/linux [...] discards 9ea25d765f01 178: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] discards 824206405ab9 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards f65f98b267c8 176: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] discards 90711e785a10 175: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] discards 21c9c1fef029 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: [...] discards 6122a39d7482 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards fe989e430013 172: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] discards ac2e324912ed 171: onsuccess: #2206: 1: Success after binutils/gcc/linux [...] discards a0dced26dd3b 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc [...] discards fc95c0ee81d8 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc [...] discards 4fdd49dce455 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc [...] discards 6dcdf27e04f3 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qe [...] discards 3aceae439d4e 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 [...] discards ba50260784db 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 1a97999796ec 164: onsuccess: #2199: 1: Success after binutils/gcc/linux [...] discards bf96bdfcf713 163: onsuccess: #2198: 1: Success after binutils/gcc/linux [...] discards d99cd6c97d14 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc [...] discards 1793ec454a83 161: onsuccess: #2196: 1: Success after binutils/gcc/linux [...] discards 7b887e6323fe 160: onsuccess: #2195: 1: Success after binutils/gcc/linux [...] discards e6f76571b707 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 1 [...] discards 221250c7b7f6 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc [...] discards 536b4e2edfd4 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: [...] discards 472cce957abc 156: onsuccess: #2191: 1: Success after binutils/gcc/linux [...] discards 1412959fcc68 155: onsuccess: #2190: 1: Success after binutils/gcc/linux [...] discards 408d4b8f9054 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: [...] discards dc24c513bd98 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: [...] discards 85e87be74157 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 2 [...] discards 88f302c3650e 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards f55543dbcd6b 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 1871f804b965 149: onsuccess: #2184: 1: Success after binutils/gcc/linux [...] discards 78c077365282 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 6 [...] discards f959b13ba129 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: [...] discards 5ac13b571808 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb [...] discards c47f74471bfa 145: onsuccess: #2180: 1: Success after binutils/gcc/linux [...] discards e1e78a508506 144: onsuccess: #2179: 1: Success after binutils/gcc/linux [...] discards 3bc3f0ce9997 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/q [...] discards 44b86c8b8ec7 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 771551919456 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: [...] discards b22b5cefb7e2 140: onsuccess: #2175: 1: Success after binutils/gcc/linux [...] discards ab288b5084d1 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: [...] discards 0a0c2cb22024 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: [...] discards 1dd8aecf73b2 137: onsuccess: #2172: 1: Success after binutils/gcc/linux [...] discards 9328b1a9cff9 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/q [...] discards 2e1e995e3fc1 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 [...] discards 72d1c610c1bf 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: [...] discards 30ed589a1d20 133: onsuccess: #2168: 1: Success after binutils/gcc/linux [...] discards 24517d546498 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc [...] new 62b4a84a124d 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc [...] new 8469396760d9 133: onsuccess: #2168: 1: Success after binutils/gcc/linux [...] new 891708a7167a 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: [...] new d82fca74bf88 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 [...] new 018483b13845 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/q [...] new b18f91b88867 137: onsuccess: #2172: 1: Success after binutils/gcc/linux [...] new 15167ffdeabe 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: [...] new 2a52af7c6f4e 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: [...] new 3020d7b85504 140: onsuccess: #2175: 1: Success after binutils/gcc/linux [...] new 4a00c3d79373 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: [...] new 7a4a6160c992 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 8c5d6efdfd6e 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/q [...] new 0230b7d5bf84 144: onsuccess: #2179: 1: Success after binutils/gcc/linux [...] new 50a8d29db5c3 145: onsuccess: #2180: 1: Success after binutils/gcc/linux [...] new d5b77105b37f 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb [...] new 259ff32a2ab9 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: [...] new 9846a92d6e7f 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 6 [...] new 14e959d416d3 149: onsuccess: #2184: 1: Success after binutils/gcc/linux [...] new 45d2f0722112 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 99c2581cabda 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 1194076a6d3a 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 2 [...] new 56808cb84ce7 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: [...] new b971614861b7 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: [...] new 3c392eb74c49 155: onsuccess: #2190: 1: Success after binutils/gcc/linux [...] new 6cb928b461bb 156: onsuccess: #2191: 1: Success after binutils/gcc/linux [...] new 5ba0e6b72bf5 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: [...] new dedbecaf689c 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc [...] new 2913672251e8 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 1 [...] new 7cad5c155e79 160: onsuccess: #2195: 1: Success after binutils/gcc/linux [...] new c28a2637c4af 161: onsuccess: #2196: 1: Success after binutils/gcc/linux [...] new 4f5f74b0759b 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc [...] new b813011f8503 163: onsuccess: #2198: 1: Success after binutils/gcc/linux [...] new 9dc66131afb0 164: onsuccess: #2199: 1: Success after binutils/gcc/linux [...] new 5df8305c275b 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new e8b72ce02f30 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 [...] new caa3fb6eea5f 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qe [...] new fade38242c97 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc [...] new ec9b5311a207 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc [...] new 4296b82838fb 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc [...] new c663576d1a86 171: onsuccess: #2206: 1: Success after binutils/gcc/linux [...] new 607094718fcc 172: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] new 5d9323ab7585 173: onsuccess: #2208: 1: Success after gcc: 10 commits new 752cd56036cc 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: [...] new ce01188d880d 175: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] new 31a970f7021e 176: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] new 696b516fe725 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new 949a7de5e3c9 178: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] new bfe690db4bd1 179: onsuccess: #2230: 1: Success after binutils/gcc/linux [...] new d2943be5a315 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc [...] new 9510ea580f3c 181: onsuccess: #2239: 1: Success after binutils/gcc/linux [...] new fa60c2c23125 182: onsuccess: #2247: 1: Success after binutils/gcc/linux [...] new 8304d271f33b 183: onsuccess: #2270: 1: Success after binutils/gcc/linux [...] new 9b2f421da0d9 184: onsuccess: #2288: 1: Success after binutils/gcc/linux [...] new 2169f8321ca9 185: onsuccess: #2290: 1: Success after binutils/gcc/linux [...] new 39f8d697c5cd 186: onsuccess: #2291: 1: Success after binutils/gcc/linux [...] new 6deb4aa4a9f0 187: onsuccess: #2294: 1: Success after binutils/gcc/linux [...] new e86e9b3ffcf3 188: onsuccess: #2295: 1: Success after binutils/gcc/linux [...] new c08aa138e38b 189: onsuccess: #2299: 1: Success after binutils/gcc/linux [...] new 0b9688854c53 190: onsuccess: #2330: 1: Success after binutils/gcc/linux [...] new 6f169e1029df 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new 4cd6828bcde8 192: onsuccess: #2338: 1: Success after binutils/gcc/linux [...] new 62c3a5f70495 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc [...] new 8d1fa7deaf20 194: onsuccess: #2340: 1: Success after binutils/gcc/linux [...] new 1bbee6225568 195: onsuccess: #2341: 1: Success after binutils/gcc/linux [...] new da9d76830a7d 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: [...] new ef70baed61f1 197: onsuccess: #2348: 1: Success after linux: 190 commits new a40edc298082 198: onsuccess: #2360: 1: Success after binutils/gcc/linux [...] new 0fa2e500a2db 199: onsuccess: #2363: 1: Success after binutils/gcc/linux [...] new e106017ae43a 200: onsuccess: #2427: 1: Success after binutils: 274 commits new d3e67fdf3afd 201: onsuccess: #2430: 1: Success after glibc: 26 commits new 1ac1d7887636 202: onsuccess: #2431: 1: Success after linux: 944 commits new de57565ba26c 203: onsuccess: #2433: 1: Success after binutils: 27 commits new dc727fb608d8 204: onsuccess: #2435: 1: Success after linux: 3 commits new 39f22d8afa23 205: onsuccess: #2444: 1: Success after binutils/gcc/linux [...] new f54f9db3948d 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc [...] new 686bb691496d 207: onsuccess: #2446: 1: Success after binutils/gcc/linux [...] new 2b321bfe0fb1 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: [...] new ce93923de972 209: onsuccess: #2448: 1: Success after binutils/gcc/linux [...] new 145cf55cfe59 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: [...] new 60657d20013c 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new 828f6ccd7c31 212: onsuccess: #2451: 1: Success after binutils/gcc/linux [...] new 1f9e29294936 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: [...] new 0faf97a2de06 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc [...] new e3cd8b02d8ae 215: onsuccess: #2455: 1: Success after binutils: 3 commits new 2b51e21bc0c5 216: onsuccess: #2457: 1: Success after linux: 1736 commits new e28ccc238a05 217: onsuccess: #2459: 1: Success after binutils: 3 commits new 085db6b0e7c3 218: onsuccess: #2461: 1: Success after linux: 916 commits new 8654ca1e6d27 219: onsuccess: #2463: 1: Success after binutils: 3 commits new 507d5b536199 220: onsuccess: #2465: 1: Success after linux: 572 commits new 6da52110e7dd 221: onsuccess: #2467: 1: Success after binutils: 3 commits new 5a8c3974c1d1 222: onsuccess: #2469: 1: Success after binutils/gcc/linux [...] new 304c145903f7 223: onsuccess: #2470: 1: Success after binutils/gcc/linux [...] new ce5b27a1413a 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: [...] new 0305867565f7 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new bed3f20976a2 226: onsuccess: #2473: 1: Success after binutils/gcc/linux [...] new 20ffee17a251 227: onsuccess: #2474: 1: Success after gcc: 2 commits new 2c304c6a5a39 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/q [...] new 6fea4d022fab 229: onsuccess: #2476: 1: Success after binutils/gcc/linux [...] new 5281c09e6ba5 230: onsuccess: #2477: 1: Success after binutils/gcc/linux [...] new 1684c468e945 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/q [...] new e0a361875528 232: onsuccess: #2480: 1: Success after binutils/gcc/linux [...] new 3920d93326bc 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/q [...]

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 (74bd4f2acc8e) \ 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 1768 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 32156 -> 31960 bytes 04-build_abe-stage1/console.log.xz | Bin 73120 -> 73492 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8692 -> 8696 bytes 07-build_abe-glibc/console.log.xz | Bin 243196 -> 244712 bytes 08-build_abe-stage2/console.log.xz | Bin 204120 -> 205812 bytes 09-build_abe-gdb/console.log.xz | Bin 39396 -> 39120 bytes 10-build_abe-qemu/console.log.xz | Bin 31792 -> 32136 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3900 -> 3908 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2936 -> 2948 bytes 13-check_regression/console.log.xz | Bin 12564 -> 13184 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 92 +- 13-check_regression/mail-body.txt | 218 +- 13-check_regression/results.compare | 135 +- 13-check_regression/results.compare2 | 1409 +++---- 13-check_regression/results.regressions | 148 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 220 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 148 +- sumfiles/g++.log.xz | Bin 3417656 -> 3429720 bytes sumfiles/g++.sum | 190 +- sumfiles/gcc.log.xz | Bin 3040176 -> 3043248 bytes sumfiles/gcc.sum | 6340 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1037348 -> 1046088 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 214828 -> 214620 bytes sumfiles/libgomp.sum | 21 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 425996 -> 437308 bytes sumfiles/libstdc++.sum | 25 +- 44 files changed, 4587 insertions(+), 4529 deletions(-)