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 b61ce124277e 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 645c11cc170d 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: [...] discards 677b6b2681ad 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: [...] discards 2dab1b890696 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/q [...] discards 01ad5e0a9032 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 9d96c53ad4f0 235: onsuccess: #2483: 1: Success after linux: 108 commits discards 2042f381ea97 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards 29af24afd4ab 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/q [...] discards c12cc75c60b7 232: onsuccess: #2480: 1: Success after binutils/gcc/linux [...] discards f20baee0a564 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/q [...] discards 511fd9b37564 230: onsuccess: #2477: 1: Success after binutils/gcc/linux [...] discards 8c625b832ef2 229: onsuccess: #2476: 1: Success after binutils/gcc/linux [...] discards e40ecb320648 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/q [...] discards d4f6cdd90633 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards 3f2ab46d5a4f 226: onsuccess: #2473: 1: Success after binutils/gcc/linux [...] discards fa9ed8785d98 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards 908838598702 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: [...] discards 2eeca990561a 223: onsuccess: #2470: 1: Success after binutils/gcc/linux [...] discards 49926335880f 222: onsuccess: #2469: 1: Success after binutils/gcc/linux [...] discards 1e63974accb6 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards d6747feaabd8 220: onsuccess: #2465: 1: Success after linux: 572 commits discards 29e74ffce393 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards 2765e9829b5f 218: onsuccess: #2461: 1: Success after linux: 916 commits discards 5c5aac28c072 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards 2b67534644ad 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards 157cc2e9a211 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards 987a1db73e8b 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc [...] discards c658ed1408d8 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: [...] discards f16305d5d57d 212: onsuccess: #2451: 1: Success after binutils/gcc/linux [...] discards d65770796a4b 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards 9025c4741e0b 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: [...] discards 34c5d36e149f 209: onsuccess: #2448: 1: Success after binutils/gcc/linux [...] discards 41156105407c 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: [...] discards 5b5df1992c7e 207: onsuccess: #2446: 1: Success after binutils/gcc/linux [...] discards a6dc8e19c198 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc [...] discards 8554aaf0f838 205: onsuccess: #2444: 1: Success after binutils/gcc/linux [...] discards 6035b1c3aae7 204: onsuccess: #2435: 1: Success after linux: 3 commits discards 5b267dd6ba1d 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards 65fab6855e2d 202: onsuccess: #2431: 1: Success after linux: 944 commits discards 22ac5ed94353 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards f0247b0608f3 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards 7f2e1e4d00a1 199: onsuccess: #2363: 1: Success after binutils/gcc/linux [...] discards 5e518f0a1ea4 198: onsuccess: #2360: 1: Success after binutils/gcc/linux [...] discards a6814c01d55f 197: onsuccess: #2348: 1: Success after linux: 190 commits discards 287343f9aa6c 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: [...] discards 2bd7056beecf 195: onsuccess: #2341: 1: Success after binutils/gcc/linux [...] discards 4331f974ccaa 194: onsuccess: #2340: 1: Success after binutils/gcc/linux [...] discards bee3e0f276a2 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc [...] discards 9eead97e62e0 192: onsuccess: #2338: 1: Success after binutils/gcc/linux [...] discards 1974d4a77632 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards 9f850ee279f8 190: onsuccess: #2330: 1: Success after binutils/gcc/linux [...] discards 4968dbed1034 189: onsuccess: #2299: 1: Success after binutils/gcc/linux [...] discards ffc47a46422b 188: onsuccess: #2295: 1: Success after binutils/gcc/linux [...] discards 7cb9bd9ab963 187: onsuccess: #2294: 1: Success after binutils/gcc/linux [...] discards afb2fefdf696 186: onsuccess: #2291: 1: Success after binutils/gcc/linux [...] discards 87ed578bac68 185: onsuccess: #2290: 1: Success after binutils/gcc/linux [...] discards 31f45b8f89cf 184: onsuccess: #2288: 1: Success after binutils/gcc/linux [...] discards 94598aefd45c 183: onsuccess: #2270: 1: Success after binutils/gcc/linux [...] discards 6a3d9717e1a3 182: onsuccess: #2247: 1: Success after binutils/gcc/linux [...] discards 7796d310ff2b 181: onsuccess: #2239: 1: Success after binutils/gcc/linux [...] discards b877182b246e 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc [...] discards a3314c00a049 179: onsuccess: #2230: 1: Success after binutils/gcc/linux [...] discards 2b7e1083a376 178: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] discards fe50326c92fa 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards e566f60e22ca 176: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] discards 2fc31336a015 175: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] discards 270f1bbfdcea 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: [...] discards 8079ba0eed60 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 0b0a1a5f1d43 172: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] discards 5804f3a37e8b 171: onsuccess: #2206: 1: Success after binutils/gcc/linux [...] discards f91cb7e2756e 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc [...] discards 775d619ff01e 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc [...] discards 38308eafffa1 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc [...] discards 0b18af17a5c3 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qe [...] discards 0a4320f41f86 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 [...] discards 9011567086fc 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 51fe414d197e 164: onsuccess: #2199: 1: Success after binutils/gcc/linux [...] discards ce93a869d575 163: onsuccess: #2198: 1: Success after binutils/gcc/linux [...] discards 69eb6ba36462 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc [...] discards aea2191aca19 161: onsuccess: #2196: 1: Success after binutils/gcc/linux [...] discards 583dbf83e809 160: onsuccess: #2195: 1: Success after binutils/gcc/linux [...] discards d91ec87ef555 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 1 [...] discards 57df48a8120f 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc [...] discards 8e5269c714c7 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: [...] discards cc17c43fbe24 156: onsuccess: #2191: 1: Success after binutils/gcc/linux [...] discards 2ec7b3d65f66 155: onsuccess: #2190: 1: Success after binutils/gcc/linux [...] discards 9786d4d787e3 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: [...] discards 2376c0c84d19 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: [...] discards 982a3761adb0 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 2 [...] discards 2fd0bf4d9c6c 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards af95445be5d4 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards eab1628f8fa0 149: onsuccess: #2184: 1: Success after binutils/gcc/linux [...] discards 415f2414f346 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 6 [...] discards 317525ae7b25 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: [...] discards d25717cc0cae 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb [...] discards 46bb581d4396 145: onsuccess: #2180: 1: Success after binutils/gcc/linux [...] discards e47a501b0ab9 144: onsuccess: #2179: 1: Success after binutils/gcc/linux [...] discards 65ec56708576 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/q [...] discards 9da606d24aa5 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 082ca95adfd4 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: [...] discards 2b7ba62d05af 140: onsuccess: #2175: 1: Success after binutils/gcc/linux [...] new d5af8b7a7b2e 140: onsuccess: #2175: 1: Success after binutils/gcc/linux [...] new 68703851b32d 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: [...] new fb88d792fbd6 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 0c7cd888b488 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/q [...] new b39fb9a6fe0e 144: onsuccess: #2179: 1: Success after binutils/gcc/linux [...] new c037204ecbb3 145: onsuccess: #2180: 1: Success after binutils/gcc/linux [...] new 153261734934 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb [...] new 6f911af2cb85 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: [...] new 88baab848171 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 6 [...] new 5bf93b8ebe9e 149: onsuccess: #2184: 1: Success after binutils/gcc/linux [...] new 45de5728037e 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 3f670336a56d 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 97b40af1dd15 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 2 [...] new 5906e9dce442 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: [...] new 0bcd9b02e696 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: [...] new f854c7de7eb1 155: onsuccess: #2190: 1: Success after binutils/gcc/linux [...] new 257ff795ce59 156: onsuccess: #2191: 1: Success after binutils/gcc/linux [...] new 5cccc88703ee 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: [...] new 094a190b6390 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc [...] new bbb391c955f1 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 1 [...] new 6b0b91d97b73 160: onsuccess: #2195: 1: Success after binutils/gcc/linux [...] new 80f5983a5b6c 161: onsuccess: #2196: 1: Success after binutils/gcc/linux [...] new c0c863d5353c 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc [...] new fb306428b8e8 163: onsuccess: #2198: 1: Success after binutils/gcc/linux [...] new 38936038dcfc 164: onsuccess: #2199: 1: Success after binutils/gcc/linux [...] new 32b12c093f26 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 9b245733cd96 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 [...] new 371e0ce56093 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qe [...] new 4a634e93f698 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc [...] new 41c2588bcdca 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc [...] new bd43b708b954 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc [...] new 1e61f7e8945b 171: onsuccess: #2206: 1: Success after binutils/gcc/linux [...] new 31c94227a5f6 172: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] new 2684ec466b54 173: onsuccess: #2208: 1: Success after gcc: 10 commits new 9a47afaad89e 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: [...] new 1b8c2ac991a7 175: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] new 1e90178be79f 176: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] new 51691242d4c9 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new e1ef428f7057 178: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] new 56fa10c22e7b 179: onsuccess: #2230: 1: Success after binutils/gcc/linux [...] new a0a1700d65ab 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc [...] new c5df64be52c6 181: onsuccess: #2239: 1: Success after binutils/gcc/linux [...] new 40543fdfacc7 182: onsuccess: #2247: 1: Success after binutils/gcc/linux [...] new fc7680cd717a 183: onsuccess: #2270: 1: Success after binutils/gcc/linux [...] new 143d8902f537 184: onsuccess: #2288: 1: Success after binutils/gcc/linux [...] new b7e4527671de 185: onsuccess: #2290: 1: Success after binutils/gcc/linux [...] new e5b4c7ea1d55 186: onsuccess: #2291: 1: Success after binutils/gcc/linux [...] new 912b25ee0cea 187: onsuccess: #2294: 1: Success after binutils/gcc/linux [...] new 325d374fa4c9 188: onsuccess: #2295: 1: Success after binutils/gcc/linux [...] new e3dbf2fafade 189: onsuccess: #2299: 1: Success after binutils/gcc/linux [...] new 827534166757 190: onsuccess: #2330: 1: Success after binutils/gcc/linux [...] new 9d9aa1c86cde 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new b1734ba4a4e8 192: onsuccess: #2338: 1: Success after binutils/gcc/linux [...] new 97345eaa2d9a 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc [...] new 9df923af4276 194: onsuccess: #2340: 1: Success after binutils/gcc/linux [...] new 451dcfa05c49 195: onsuccess: #2341: 1: Success after binutils/gcc/linux [...] new 7ea867573de2 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: [...] new 5c502ff05cba 197: onsuccess: #2348: 1: Success after linux: 190 commits new df7513ce4169 198: onsuccess: #2360: 1: Success after binutils/gcc/linux [...] new 78f7f4b3844d 199: onsuccess: #2363: 1: Success after binutils/gcc/linux [...] new 15ee515de9a3 200: onsuccess: #2427: 1: Success after binutils: 274 commits new 6680438104a3 201: onsuccess: #2430: 1: Success after glibc: 26 commits new e4bb1e0ef0ce 202: onsuccess: #2431: 1: Success after linux: 944 commits new 8ed46b3eafd2 203: onsuccess: #2433: 1: Success after binutils: 27 commits new 1161f502d9c6 204: onsuccess: #2435: 1: Success after linux: 3 commits new f2e5eeb37f0a 205: onsuccess: #2444: 1: Success after binutils/gcc/linux [...] new 6cf58d03ddf7 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc [...] new 9f372ca115b5 207: onsuccess: #2446: 1: Success after binutils/gcc/linux [...] new 299d3297cc8b 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: [...] new 67480bc12ed8 209: onsuccess: #2448: 1: Success after binutils/gcc/linux [...] new 6cb229d721a1 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: [...] new 8d8af6641c72 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new 76b393d4013e 212: onsuccess: #2451: 1: Success after binutils/gcc/linux [...] new 5d2e1f95eef8 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: [...] new aa7f4e7349ce 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc [...] new f0a880539336 215: onsuccess: #2455: 1: Success after binutils: 3 commits new 1b3838d63ba0 216: onsuccess: #2457: 1: Success after linux: 1736 commits new 4197ac15e363 217: onsuccess: #2459: 1: Success after binutils: 3 commits new bf94ffeccb80 218: onsuccess: #2461: 1: Success after linux: 916 commits new 0df8d3c9eeba 219: onsuccess: #2463: 1: Success after binutils: 3 commits new 5a66d3a2ad5d 220: onsuccess: #2465: 1: Success after linux: 572 commits new 888e9cde4756 221: onsuccess: #2467: 1: Success after binutils: 3 commits new aae8f434663f 222: onsuccess: #2469: 1: Success after binutils/gcc/linux [...] new 189fbbf3df4e 223: onsuccess: #2470: 1: Success after binutils/gcc/linux [...] new 8260c076fdbc 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: [...] new f9745a9f103d 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new 135f609d6036 226: onsuccess: #2473: 1: Success after binutils/gcc/linux [...] new f4c4b5861ce7 227: onsuccess: #2474: 1: Success after gcc: 2 commits new 45146e65a755 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/q [...] new 9dd99240bd3b 229: onsuccess: #2476: 1: Success after binutils/gcc/linux [...] new d029ce37e768 230: onsuccess: #2477: 1: Success after binutils/gcc/linux [...] new 6ad220115d61 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/q [...] new a3fdb14a10bd 232: onsuccess: #2480: 1: Success after binutils/gcc/linux [...] new 6ed7ffa00ed3 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/q [...] new f56a9bc2c2d8 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 12d049290ca0 235: onsuccess: #2483: 1: Success after linux: 108 commits new cc8bf6261159 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 5bf8300b2111 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/q [...] new 6d3270e42121 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: [...] new 47c4cf879c62 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: [...] new 349063ab5a8c 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new d6b0de83ca02 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc [...]

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 (b61ce124277e) \ 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 -> 1812 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 32032 -> 31980 bytes 04-build_abe-stage1/console.log.xz | Bin 73076 -> 73040 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8604 -> 8632 bytes 07-build_abe-glibc/console.log.xz | Bin 243632 -> 243076 bytes 08-build_abe-stage2/console.log.xz | Bin 204088 -> 203872 bytes 09-build_abe-gdb/console.log.xz | Bin 39148 -> 39068 bytes 10-build_abe-qemu/console.log.xz | Bin 31096 -> 31044 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3912 -> 3876 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2940 -> 2668 bytes 13-check_regression/console.log.xz | Bin 5924 -> 6092 bytes 13-check_regression/fails.sum | 10 +- 13-check_regression/mail-body.txt | 84 +- 13-check_regression/results.compare | 40 +- 13-check_regression/results.compare2 | 47 +- 13-check_regression/results.regressions | 40 +- 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 86 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 40 +- sumfiles/g++.log.xz | Bin 3438904 -> 3423320 bytes sumfiles/g++.sum | 151 +- sumfiles/gcc.log.xz | Bin 3019076 -> 3021436 bytes sumfiles/gcc.sum | 4438 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1032408 -> 1034368 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 214776 -> 214620 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2692 -> 2696 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 421208 -> 432432 bytes sumfiles/libstdc++.sum | 10 +- 43 files changed, 2562 insertions(+), 2572 deletions(-)