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 5356c3a8c3a6 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: [...] discards 72ab9109aa7d 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/q [...] discards 30c838dae048 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 4faed16cc565 235: onsuccess: #2483: 1: Success after linux: 108 commits discards 1717e6956c53 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards 68ea1fb5be73 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/q [...] discards 186ef8a93c50 232: onsuccess: #2480: 1: Success after binutils/gcc/linux [...] discards e7e577436276 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/q [...] discards 3f2af0e42863 230: onsuccess: #2477: 1: Success after binutils/gcc/linux [...] discards 2a94c05d08bb 229: onsuccess: #2476: 1: Success after binutils/gcc/linux [...] discards ac3911ac97b1 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/q [...] discards ad360a2adf87 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards 23d814ff141e 226: onsuccess: #2473: 1: Success after binutils/gcc/linux [...] discards b5c057d05103 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards 300a400363a6 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: [...] discards 32cf734093a7 223: onsuccess: #2470: 1: Success after binutils/gcc/linux [...] discards eae53f9a1981 222: onsuccess: #2469: 1: Success after binutils/gcc/linux [...] discards ecabd6c6c4b1 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards 88ab050f0545 220: onsuccess: #2465: 1: Success after linux: 572 commits discards b1da1262c317 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards 7fab2e19db3d 218: onsuccess: #2461: 1: Success after linux: 916 commits discards daf3fa24fd31 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards 67570d30538e 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards 57b435c69e1f 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards 1c84bf54b037 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc [...] discards 9100db08ba08 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: [...] discards 58bf33bd1b26 212: onsuccess: #2451: 1: Success after binutils/gcc/linux [...] discards 4f9fe5e4df00 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards 39288141a5f4 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: [...] discards 0fc0645c4a28 209: onsuccess: #2448: 1: Success after binutils/gcc/linux [...] discards 174f19017c1e 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: [...] discards 7fbf26a0b7a4 207: onsuccess: #2446: 1: Success after binutils/gcc/linux [...] discards 5c66cb1a1281 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc [...] discards e8ec3209f214 205: onsuccess: #2444: 1: Success after binutils/gcc/linux [...] discards 7c48b05aff32 204: onsuccess: #2435: 1: Success after linux: 3 commits discards d2c6ba1a107e 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards 8775ad3fac37 202: onsuccess: #2431: 1: Success after linux: 944 commits discards df3b6db996e5 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards 7cf0d7ad2804 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards f945c48a2be0 199: onsuccess: #2363: 1: Success after binutils/gcc/linux [...] discards dfde384d2206 198: onsuccess: #2360: 1: Success after binutils/gcc/linux [...] discards fe7978a6003f 197: onsuccess: #2348: 1: Success after linux: 190 commits discards 06c1bb0980de 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: [...] discards 5db1472797ed 195: onsuccess: #2341: 1: Success after binutils/gcc/linux [...] discards 8c81a0b252d7 194: onsuccess: #2340: 1: Success after binutils/gcc/linux [...] discards 9151ecab1abd 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc [...] discards d9ff90a37a01 192: onsuccess: #2338: 1: Success after binutils/gcc/linux [...] discards 45247ed21b68 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards 9a775bf369dc 190: onsuccess: #2330: 1: Success after binutils/gcc/linux [...] discards b4159eb909c6 189: onsuccess: #2299: 1: Success after binutils/gcc/linux [...] discards 1a4c29f03986 188: onsuccess: #2295: 1: Success after binutils/gcc/linux [...] discards 36c533737f7b 187: onsuccess: #2294: 1: Success after binutils/gcc/linux [...] discards 8e53680e2d67 186: onsuccess: #2291: 1: Success after binutils/gcc/linux [...] discards 881f65c06172 185: onsuccess: #2290: 1: Success after binutils/gcc/linux [...] discards 3472a436c02f 184: onsuccess: #2288: 1: Success after binutils/gcc/linux [...] discards 954278d92ae5 183: onsuccess: #2270: 1: Success after binutils/gcc/linux [...] discards 3cd1d1ac175c 182: onsuccess: #2247: 1: Success after binutils/gcc/linux [...] discards d73cf753ecbd 181: onsuccess: #2239: 1: Success after binutils/gcc/linux [...] discards 3335ef673b7c 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc [...] discards 0f5936ddd999 179: onsuccess: #2230: 1: Success after binutils/gcc/linux [...] discards 2494b70c282e 178: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] discards 06dcd7371d3e 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards b5cd978e85cc 176: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] discards 4581a6dba86c 175: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] discards 3b82fa145a66 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: [...] discards 8dc9593ea70e 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards fb3e80103875 172: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] discards aa11a76702db 171: onsuccess: #2206: 1: Success after binutils/gcc/linux [...] discards 3b49ea534805 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc [...] discards 14081631e298 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc [...] discards 5afd497204f1 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc [...] discards 8ff684200873 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qe [...] discards 15cad30f1c51 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 [...] discards 1a7f366cee2f 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards e7f213cade52 164: onsuccess: #2199: 1: Success after binutils/gcc/linux [...] discards 93c853e1c744 163: onsuccess: #2198: 1: Success after binutils/gcc/linux [...] discards f81c6fc81071 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc [...] discards 292936ada317 161: onsuccess: #2196: 1: Success after binutils/gcc/linux [...] discards 4daa8b4d9d5f 160: onsuccess: #2195: 1: Success after binutils/gcc/linux [...] discards bb2dfe9b7bc8 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 1 [...] discards af595be5ab65 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc [...] discards 8196ef6d15a1 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: [...] discards 5a262dc551d7 156: onsuccess: #2191: 1: Success after binutils/gcc/linux [...] discards 0a2c31473d47 155: onsuccess: #2190: 1: Success after binutils/gcc/linux [...] discards 770bcc96185c 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: [...] discards 4bf3fe404d0c 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: [...] discards dbdb62b11fa3 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 2 [...] discards f00a0f54994c 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 44ebe0e3c8f5 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards eea9d627a4fd 149: onsuccess: #2184: 1: Success after binutils/gcc/linux [...] discards 6457abb54eb8 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 6 [...] discards 82773c1a893c 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: [...] discards 840398c65b60 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb [...] discards 0de9c7a2da32 145: onsuccess: #2180: 1: Success after binutils/gcc/linux [...] discards b515fbe32243 144: onsuccess: #2179: 1: Success after binutils/gcc/linux [...] discards 01938b3eb7ff 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/q [...] discards 7e17d7aee3ae 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 064b9219635b 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: [...] discards 4e146b3f04e1 140: onsuccess: #2175: 1: Success after binutils/gcc/linux [...] discards 0a7d9d12e976 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: [...] discards ba313dc03665 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: [...] new de7ccc5f8527 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: [...] new 9800ff3692fd 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: [...] new 95698cdc21be 140: onsuccess: #2175: 1: Success after binutils/gcc/linux [...] new 0c7e3309f760 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: [...] new 4a1e49ea7210 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new d975f0c1c2c6 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/q [...] new c0ab40ae359f 144: onsuccess: #2179: 1: Success after binutils/gcc/linux [...] new ed8410037d9c 145: onsuccess: #2180: 1: Success after binutils/gcc/linux [...] new c48837cda3e8 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb [...] new 548d67e40d25 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: [...] new 93bca3682c92 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 6 [...] new dfb112fc77cc 149: onsuccess: #2184: 1: Success after binutils/gcc/linux [...] new c20db0b30cee 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 4134821176e4 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 39cdc6209c35 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 2 [...] new 819e4361e3af 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: [...] new 9ff203b18c3e 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: [...] new 16a1009b306d 155: onsuccess: #2190: 1: Success after binutils/gcc/linux [...] new 653c9d6714b1 156: onsuccess: #2191: 1: Success after binutils/gcc/linux [...] new 46197233e58b 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: [...] new c04f21ad8bf1 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc [...] new 5cc1b92c10bf 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 1 [...] new 8a1a8e65b13b 160: onsuccess: #2195: 1: Success after binutils/gcc/linux [...] new 20be04e75693 161: onsuccess: #2196: 1: Success after binutils/gcc/linux [...] new 1b08cfe3211d 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc [...] new d17275f91fcf 163: onsuccess: #2198: 1: Success after binutils/gcc/linux [...] new 8dc8b98cf8bb 164: onsuccess: #2199: 1: Success after binutils/gcc/linux [...] new 8570f79398e1 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 574e574ce881 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 [...] new 68c0a0ad00b0 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qe [...] new 5eb582bf6358 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc [...] new 219a4ee91384 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc [...] new 7e036ecd76ea 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc [...] new 4ef243fdb9a1 171: onsuccess: #2206: 1: Success after binutils/gcc/linux [...] new 445c367647da 172: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] new 6bcf63033346 173: onsuccess: #2208: 1: Success after gcc: 10 commits new 85a5c662b8b3 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: [...] new cf956907e833 175: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] new ab8a44140c2d 176: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] new 109c6f8eaa58 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new 6790a4faae29 178: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] new 28186bde0b39 179: onsuccess: #2230: 1: Success after binutils/gcc/linux [...] new ced2a721549f 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc [...] new ee4b14a95903 181: onsuccess: #2239: 1: Success after binutils/gcc/linux [...] new 449fe536e9f6 182: onsuccess: #2247: 1: Success after binutils/gcc/linux [...] new 1efb4337ff8c 183: onsuccess: #2270: 1: Success after binutils/gcc/linux [...] new d136c6d50d1e 184: onsuccess: #2288: 1: Success after binutils/gcc/linux [...] new a5cbd6485f93 185: onsuccess: #2290: 1: Success after binutils/gcc/linux [...] new 031dabb82831 186: onsuccess: #2291: 1: Success after binutils/gcc/linux [...] new 23a0e32f376a 187: onsuccess: #2294: 1: Success after binutils/gcc/linux [...] new 7fbcafca3f55 188: onsuccess: #2295: 1: Success after binutils/gcc/linux [...] new 685c489958e4 189: onsuccess: #2299: 1: Success after binutils/gcc/linux [...] new 1a497c50cadd 190: onsuccess: #2330: 1: Success after binutils/gcc/linux [...] new 2866221e43fd 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new 01c33f5a92da 192: onsuccess: #2338: 1: Success after binutils/gcc/linux [...] new fb9793736582 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc [...] new 95b6c4c803ca 194: onsuccess: #2340: 1: Success after binutils/gcc/linux [...] new 1bec153ea1b4 195: onsuccess: #2341: 1: Success after binutils/gcc/linux [...] new 34a83ad0ffbf 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: [...] new 05dd44144ca1 197: onsuccess: #2348: 1: Success after linux: 190 commits new c7dfe3b4ec3c 198: onsuccess: #2360: 1: Success after binutils/gcc/linux [...] new 749c33000664 199: onsuccess: #2363: 1: Success after binutils/gcc/linux [...] new 7f905c093dc2 200: onsuccess: #2427: 1: Success after binutils: 274 commits new c8603e9b7758 201: onsuccess: #2430: 1: Success after glibc: 26 commits new 04afdbad2452 202: onsuccess: #2431: 1: Success after linux: 944 commits new e27f0810bc39 203: onsuccess: #2433: 1: Success after binutils: 27 commits new e0efbbd5ca40 204: onsuccess: #2435: 1: Success after linux: 3 commits new 8220ecb0e1ea 205: onsuccess: #2444: 1: Success after binutils/gcc/linux [...] new 83e8ca175acc 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc [...] new 93069308017c 207: onsuccess: #2446: 1: Success after binutils/gcc/linux [...] new 834a8ebf623d 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: [...] new fc770df0ae52 209: onsuccess: #2448: 1: Success after binutils/gcc/linux [...] new 93ff398d726c 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: [...] new 8b1e2dc638de 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new 0d6fec5b039c 212: onsuccess: #2451: 1: Success after binutils/gcc/linux [...] new 6b7f967f5e0a 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: [...] new b7680f000be0 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc [...] new e8d553e8a62d 215: onsuccess: #2455: 1: Success after binutils: 3 commits new 6a3edc94f5a0 216: onsuccess: #2457: 1: Success after linux: 1736 commits new 79ab7bb288f7 217: onsuccess: #2459: 1: Success after binutils: 3 commits new 5b6e62849437 218: onsuccess: #2461: 1: Success after linux: 916 commits new bd72cb66d867 219: onsuccess: #2463: 1: Success after binutils: 3 commits new 510b884b1f4e 220: onsuccess: #2465: 1: Success after linux: 572 commits new e81faa6d530d 221: onsuccess: #2467: 1: Success after binutils: 3 commits new 292116b2bf35 222: onsuccess: #2469: 1: Success after binutils/gcc/linux [...] new 2a94ecaca635 223: onsuccess: #2470: 1: Success after binutils/gcc/linux [...] new 22fa6bc5ee22 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: [...] new c12501844371 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new a8b9f2edc65a 226: onsuccess: #2473: 1: Success after binutils/gcc/linux [...] new 3068f5380449 227: onsuccess: #2474: 1: Success after gcc: 2 commits new 23cfaf9306d1 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/q [...] new 39bfbf61f972 229: onsuccess: #2476: 1: Success after binutils/gcc/linux [...] new 9ef38f448b1f 230: onsuccess: #2477: 1: Success after binutils/gcc/linux [...] new 786fbb327f8f 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/q [...] new 0883e3c34a8a 232: onsuccess: #2480: 1: Success after binutils/gcc/linux [...] new e30e70d6088d 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/q [...] new 0226ba90f190 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 814a537c6e39 235: onsuccess: #2483: 1: Success after linux: 108 commits new 9bd190fe00ef 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 046f076b7190 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/q [...] new 8734b0678ed1 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: [...] new 6950fdc42a6b 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: [...]

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 (5356c3a8c3a6) \ 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 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 32312 -> 32160 bytes 04-build_abe-stage1/console.log.xz | Bin 73336 -> 73256 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8652 -> 8628 bytes 07-build_abe-glibc/console.log.xz | Bin 243988 -> 243284 bytes 08-build_abe-stage2/console.log.xz | Bin 204444 -> 204160 bytes 09-build_abe-gdb/console.log.xz | Bin 39348 -> 39380 bytes 10-build_abe-qemu/console.log.xz | Bin 31428 -> 31408 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3900 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2816 -> 2804 bytes 13-check_regression/console.log.xz | Bin 5980 -> 5988 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 33 +- 13-check_regression/mail-body.txt | 92 +- 13-check_regression/results.compare | 70 +- 13-check_regression/results.compare2 | 69 +- 13-check_regression/results.regressions | 70 +- 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/mail-body.txt | 92 +- manifest.sh | 32 +- results | 70 +- sumfiles/g++.log.xz | Bin 3420692 -> 3412980 bytes sumfiles/g++.sum | 183 +- sumfiles/gcc.log.xz | Bin 3041176 -> 3037112 bytes sumfiles/gcc.sum | 4868 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1038996 -> 1038344 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2296 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 214764 -> 214688 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2696 -> 2696 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 431272 -> 425736 bytes sumfiles/libstdc++.sum | 16 +- 41 files changed, 2907 insertions(+), 2834 deletions(-)