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 2058e0bc3e09 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/q [...] discards 94ef7a5d8e2b 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 4e7fc41f90c3 235: onsuccess: #2483: 1: Success after linux: 108 commits discards 861d9f2ee09b 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards 3eecf30a7419 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/q [...] discards 546b5d089fc8 232: onsuccess: #2480: 1: Success after binutils/gcc/linux [...] discards e94904e160c5 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/q [...] discards 3cbb376744c8 230: onsuccess: #2477: 1: Success after binutils/gcc/linux [...] discards 504c085eaebf 229: onsuccess: #2476: 1: Success after binutils/gcc/linux [...] discards 0afb3e136162 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/q [...] discards d01c9be58324 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards f032851e9abc 226: onsuccess: #2473: 1: Success after binutils/gcc/linux [...] discards 9571d1b5fa0b 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards e30b30a8f28f 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: [...] discards c972d72c68d7 223: onsuccess: #2470: 1: Success after binutils/gcc/linux [...] discards 45365f50d3e3 222: onsuccess: #2469: 1: Success after binutils/gcc/linux [...] discards 7882f0aee013 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards e30c9c8eb804 220: onsuccess: #2465: 1: Success after linux: 572 commits discards 0c797987751a 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards 88b25bc91330 218: onsuccess: #2461: 1: Success after linux: 916 commits discards fe3dcc4d8b19 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards b1429be88bf4 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards 82798f543118 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards 30f19be48e46 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc [...] discards c65dfd208995 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: [...] discards ccc91c83c14f 212: onsuccess: #2451: 1: Success after binutils/gcc/linux [...] discards 1e0686ca5586 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards a58fa23376d3 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: [...] discards ded32db7ab8e 209: onsuccess: #2448: 1: Success after binutils/gcc/linux [...] discards 37e3b86c5fe4 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: [...] discards 348d08a1602b 207: onsuccess: #2446: 1: Success after binutils/gcc/linux [...] discards ba8b061c5aa8 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc [...] discards 40f9a73cafc2 205: onsuccess: #2444: 1: Success after binutils/gcc/linux [...] discards 2801575f0335 204: onsuccess: #2435: 1: Success after linux: 3 commits discards 34781fbeb9ee 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards 55f47d1f4226 202: onsuccess: #2431: 1: Success after linux: 944 commits discards d0a1cbb2c405 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards c386ab0c7e55 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards dd05686f019c 199: onsuccess: #2363: 1: Success after binutils/gcc/linux [...] discards 684752c1dc8d 198: onsuccess: #2360: 1: Success after binutils/gcc/linux [...] discards 4b3a007d8aaa 197: onsuccess: #2348: 1: Success after linux: 190 commits discards 0bec24de1532 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: [...] discards 7011f93f9b01 195: onsuccess: #2341: 1: Success after binutils/gcc/linux [...] discards 3e599db88aac 194: onsuccess: #2340: 1: Success after binutils/gcc/linux [...] discards 01b339f597a5 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc [...] discards f9b501d06679 192: onsuccess: #2338: 1: Success after binutils/gcc/linux [...] discards 6c87eb1bc56e 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards 385d1fa8b18c 190: onsuccess: #2330: 1: Success after binutils/gcc/linux [...] discards f2385dc7afe4 189: onsuccess: #2299: 1: Success after binutils/gcc/linux [...] discards 760b9a51c6bb 188: onsuccess: #2295: 1: Success after binutils/gcc/linux [...] discards fdc61cf934cf 187: onsuccess: #2294: 1: Success after binutils/gcc/linux [...] discards e63cd4d93652 186: onsuccess: #2291: 1: Success after binutils/gcc/linux [...] discards c8b971db492f 185: onsuccess: #2290: 1: Success after binutils/gcc/linux [...] discards 449d4c4f53b2 184: onsuccess: #2288: 1: Success after binutils/gcc/linux [...] discards 29fbebf3b181 183: onsuccess: #2270: 1: Success after binutils/gcc/linux [...] discards ebdf15569826 182: onsuccess: #2247: 1: Success after binutils/gcc/linux [...] discards 2fa740e5a8d5 181: onsuccess: #2239: 1: Success after binutils/gcc/linux [...] discards 6587a3e54fdd 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc [...] discards 3bbdd8a2f882 179: onsuccess: #2230: 1: Success after binutils/gcc/linux [...] discards 394182e3d5cf 178: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] discards 3330eceae02f 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards 619185af0f06 176: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] discards 6a90e2a924bf 175: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] discards 37087bb2de74 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: [...] discards 5f988884736a 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards ec5c8cee76bc 172: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] discards 1f5261eacdd8 171: onsuccess: #2206: 1: Success after binutils/gcc/linux [...] discards 8d8056243cb1 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc [...] discards e25a1e2350af 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc [...] discards 08f78acbd729 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc [...] discards 001941ebca7c 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qe [...] discards a945bb1290d9 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 [...] discards a89901ff46d6 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards f5d7bbdd57bf 164: onsuccess: #2199: 1: Success after binutils/gcc/linux [...] discards 0dbb2466e3f1 163: onsuccess: #2198: 1: Success after binutils/gcc/linux [...] discards a30802dc0cdc 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc [...] discards d852c7da9201 161: onsuccess: #2196: 1: Success after binutils/gcc/linux [...] discards 87af57f83ef9 160: onsuccess: #2195: 1: Success after binutils/gcc/linux [...] discards 1987c1defc0e 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 1 [...] discards af37ff6727e6 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc [...] discards 5e360af4dcde 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: [...] discards 7787e9a35575 156: onsuccess: #2191: 1: Success after binutils/gcc/linux [...] discards 14dd0c22d488 155: onsuccess: #2190: 1: Success after binutils/gcc/linux [...] discards 4ad9bfab9150 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: [...] discards 0552c95e7034 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: [...] discards 7f169fb221da 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 2 [...] discards 4c8d5c547e8b 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards cdbff712b211 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 531019909f31 149: onsuccess: #2184: 1: Success after binutils/gcc/linux [...] discards 230c225038ce 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 6 [...] discards fc917e0748c1 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: [...] discards df87879a2441 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb [...] discards 7a833d365cc2 145: onsuccess: #2180: 1: Success after binutils/gcc/linux [...] discards b8b5a0d82d29 144: onsuccess: #2179: 1: Success after binutils/gcc/linux [...] discards 25147f4e4201 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/q [...] discards dfa6a07113df 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 4416dd5a39d4 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: [...] discards 02774520ec88 140: onsuccess: #2175: 1: Success after binutils/gcc/linux [...] discards d544e10a71b1 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: [...] discards 09f022d92eee 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: [...] discards 3e77adabb6ba 137: onsuccess: #2172: 1: Success after binutils/gcc/linux [...] new 29240cb5a4cc 137: onsuccess: #2172: 1: Success after binutils/gcc/linux [...] new ba313dc03665 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: [...] new 0a7d9d12e976 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: [...] new 4e146b3f04e1 140: onsuccess: #2175: 1: Success after binutils/gcc/linux [...] new 064b9219635b 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: [...] new 7e17d7aee3ae 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 01938b3eb7ff 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/q [...] new b515fbe32243 144: onsuccess: #2179: 1: Success after binutils/gcc/linux [...] new 0de9c7a2da32 145: onsuccess: #2180: 1: Success after binutils/gcc/linux [...] new 840398c65b60 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb [...] new 82773c1a893c 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: [...] new 6457abb54eb8 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 6 [...] new eea9d627a4fd 149: onsuccess: #2184: 1: Success after binutils/gcc/linux [...] new 44ebe0e3c8f5 150: onsuccess: #2185: 1: Success after gcc: 3 commits new f00a0f54994c 151: onsuccess: #2186: 1: Success after gcc: 2 commits new dbdb62b11fa3 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 2 [...] new 4bf3fe404d0c 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: [...] new 770bcc96185c 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: [...] new 0a2c31473d47 155: onsuccess: #2190: 1: Success after binutils/gcc/linux [...] new 5a262dc551d7 156: onsuccess: #2191: 1: Success after binutils/gcc/linux [...] new 8196ef6d15a1 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: [...] new af595be5ab65 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc [...] new bb2dfe9b7bc8 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 1 [...] new 4daa8b4d9d5f 160: onsuccess: #2195: 1: Success after binutils/gcc/linux [...] new 292936ada317 161: onsuccess: #2196: 1: Success after binutils/gcc/linux [...] new f81c6fc81071 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc [...] new 93c853e1c744 163: onsuccess: #2198: 1: Success after binutils/gcc/linux [...] new e7f213cade52 164: onsuccess: #2199: 1: Success after binutils/gcc/linux [...] new 1a7f366cee2f 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 15cad30f1c51 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 [...] new 8ff684200873 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qe [...] new 5afd497204f1 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc [...] new 14081631e298 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc [...] new 3b49ea534805 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc [...] new aa11a76702db 171: onsuccess: #2206: 1: Success after binutils/gcc/linux [...] new fb3e80103875 172: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] new 8dc9593ea70e 173: onsuccess: #2208: 1: Success after gcc: 10 commits new 3b82fa145a66 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: [...] new 4581a6dba86c 175: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] new b5cd978e85cc 176: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] new 06dcd7371d3e 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new 2494b70c282e 178: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] new 0f5936ddd999 179: onsuccess: #2230: 1: Success after binutils/gcc/linux [...] new 3335ef673b7c 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc [...] new d73cf753ecbd 181: onsuccess: #2239: 1: Success after binutils/gcc/linux [...] new 3cd1d1ac175c 182: onsuccess: #2247: 1: Success after binutils/gcc/linux [...] new 954278d92ae5 183: onsuccess: #2270: 1: Success after binutils/gcc/linux [...] new 3472a436c02f 184: onsuccess: #2288: 1: Success after binutils/gcc/linux [...] new 881f65c06172 185: onsuccess: #2290: 1: Success after binutils/gcc/linux [...] new 8e53680e2d67 186: onsuccess: #2291: 1: Success after binutils/gcc/linux [...] new 36c533737f7b 187: onsuccess: #2294: 1: Success after binutils/gcc/linux [...] new 1a4c29f03986 188: onsuccess: #2295: 1: Success after binutils/gcc/linux [...] new b4159eb909c6 189: onsuccess: #2299: 1: Success after binutils/gcc/linux [...] new 9a775bf369dc 190: onsuccess: #2330: 1: Success after binutils/gcc/linux [...] new 45247ed21b68 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new d9ff90a37a01 192: onsuccess: #2338: 1: Success after binutils/gcc/linux [...] new 9151ecab1abd 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc [...] new 8c81a0b252d7 194: onsuccess: #2340: 1: Success after binutils/gcc/linux [...] new 5db1472797ed 195: onsuccess: #2341: 1: Success after binutils/gcc/linux [...] new 06c1bb0980de 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: [...] new fe7978a6003f 197: onsuccess: #2348: 1: Success after linux: 190 commits new dfde384d2206 198: onsuccess: #2360: 1: Success after binutils/gcc/linux [...] new f945c48a2be0 199: onsuccess: #2363: 1: Success after binutils/gcc/linux [...] new 7cf0d7ad2804 200: onsuccess: #2427: 1: Success after binutils: 274 commits new df3b6db996e5 201: onsuccess: #2430: 1: Success after glibc: 26 commits new 8775ad3fac37 202: onsuccess: #2431: 1: Success after linux: 944 commits new d2c6ba1a107e 203: onsuccess: #2433: 1: Success after binutils: 27 commits new 7c48b05aff32 204: onsuccess: #2435: 1: Success after linux: 3 commits new e8ec3209f214 205: onsuccess: #2444: 1: Success after binutils/gcc/linux [...] new 5c66cb1a1281 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc [...] new 7fbf26a0b7a4 207: onsuccess: #2446: 1: Success after binutils/gcc/linux [...] new 174f19017c1e 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: [...] new 0fc0645c4a28 209: onsuccess: #2448: 1: Success after binutils/gcc/linux [...] new 39288141a5f4 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: [...] new 4f9fe5e4df00 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new 58bf33bd1b26 212: onsuccess: #2451: 1: Success after binutils/gcc/linux [...] new 9100db08ba08 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: [...] new 1c84bf54b037 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc [...] new 57b435c69e1f 215: onsuccess: #2455: 1: Success after binutils: 3 commits new 67570d30538e 216: onsuccess: #2457: 1: Success after linux: 1736 commits new daf3fa24fd31 217: onsuccess: #2459: 1: Success after binutils: 3 commits new 7fab2e19db3d 218: onsuccess: #2461: 1: Success after linux: 916 commits new b1da1262c317 219: onsuccess: #2463: 1: Success after binutils: 3 commits new 88ab050f0545 220: onsuccess: #2465: 1: Success after linux: 572 commits new ecabd6c6c4b1 221: onsuccess: #2467: 1: Success after binutils: 3 commits new eae53f9a1981 222: onsuccess: #2469: 1: Success after binutils/gcc/linux [...] new 32cf734093a7 223: onsuccess: #2470: 1: Success after binutils/gcc/linux [...] new 300a400363a6 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: [...] new b5c057d05103 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new 23d814ff141e 226: onsuccess: #2473: 1: Success after binutils/gcc/linux [...] new ad360a2adf87 227: onsuccess: #2474: 1: Success after gcc: 2 commits new ac3911ac97b1 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/q [...] new 2a94c05d08bb 229: onsuccess: #2476: 1: Success after binutils/gcc/linux [...] new 3f2af0e42863 230: onsuccess: #2477: 1: Success after binutils/gcc/linux [...] new e7e577436276 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/q [...] new 186ef8a93c50 232: onsuccess: #2480: 1: Success after binutils/gcc/linux [...] new 68ea1fb5be73 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/q [...] new 1717e6956c53 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 4faed16cc565 235: onsuccess: #2483: 1: Success after linux: 108 commits new 30c838dae048 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 72ab9109aa7d 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/q [...] new 5356c3a8c3a6 238: onsuccess: #2486: 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 (2058e0bc3e09) \ 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 1776 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 32280 -> 32312 bytes 04-build_abe-stage1/console.log.xz | Bin 73400 -> 73336 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8664 -> 8652 bytes 07-build_abe-glibc/console.log.xz | Bin 244224 -> 243988 bytes 08-build_abe-stage2/console.log.xz | Bin 204860 -> 204444 bytes 09-build_abe-gdb/console.log.xz | Bin 39516 -> 39348 bytes 10-build_abe-qemu/console.log.xz | Bin 31836 -> 31428 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3952 -> 3900 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2652 -> 2816 bytes 13-check_regression/console.log.xz | Bin 6336 -> 5980 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 28 + 13-check_regression/mail-body.txt | 95 +- 13-check_regression/results.compare | 54 +- 13-check_regression/results.compare2 | 69 +- .../results.regressions | 106 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 97 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 48 + sumfiles/g++.log.xz | Bin 3429016 -> 3420692 bytes sumfiles/g++.sum | 203 +- sumfiles/gcc.log.xz | Bin 3015484 -> 3041176 bytes sumfiles/gcc.sum | 5307 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 1034528 -> 1038996 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 214768 -> 214764 bytes sumfiles/libgomp.sum | 21 +- sumfiles/libitm.log.xz | Bin 2696 -> 2696 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 433192 -> 431272 bytes sumfiles/libstdc++.sum | 14 +- 43 files changed, 3124 insertions(+), 3085 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum copy mail/mail-body.txt => 13-check_regression/results.regressions (51%)