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 6950fdc42a6b 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: [...] discards 8734b0678ed1 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: [...] discards 046f076b7190 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/q [...] discards 9bd190fe00ef 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 814a537c6e39 235: onsuccess: #2483: 1: Success after linux: 108 commits discards 0226ba90f190 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards e30e70d6088d 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/q [...] discards 0883e3c34a8a 232: onsuccess: #2480: 1: Success after binutils/gcc/linux [...] discards 786fbb327f8f 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/q [...] discards 9ef38f448b1f 230: onsuccess: #2477: 1: Success after binutils/gcc/linux [...] discards 39bfbf61f972 229: onsuccess: #2476: 1: Success after binutils/gcc/linux [...] discards 23cfaf9306d1 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/q [...] discards 3068f5380449 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards a8b9f2edc65a 226: onsuccess: #2473: 1: Success after binutils/gcc/linux [...] discards c12501844371 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards 22fa6bc5ee22 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: [...] discards 2a94ecaca635 223: onsuccess: #2470: 1: Success after binutils/gcc/linux [...] discards 292116b2bf35 222: onsuccess: #2469: 1: Success after binutils/gcc/linux [...] discards e81faa6d530d 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards 510b884b1f4e 220: onsuccess: #2465: 1: Success after linux: 572 commits discards bd72cb66d867 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards 5b6e62849437 218: onsuccess: #2461: 1: Success after linux: 916 commits discards 79ab7bb288f7 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards 6a3edc94f5a0 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards e8d553e8a62d 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards b7680f000be0 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc [...] discards 6b7f967f5e0a 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: [...] discards 0d6fec5b039c 212: onsuccess: #2451: 1: Success after binutils/gcc/linux [...] discards 8b1e2dc638de 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards 93ff398d726c 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: [...] discards fc770df0ae52 209: onsuccess: #2448: 1: Success after binutils/gcc/linux [...] discards 834a8ebf623d 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: [...] discards 93069308017c 207: onsuccess: #2446: 1: Success after binutils/gcc/linux [...] discards 83e8ca175acc 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc [...] discards 8220ecb0e1ea 205: onsuccess: #2444: 1: Success after binutils/gcc/linux [...] discards e0efbbd5ca40 204: onsuccess: #2435: 1: Success after linux: 3 commits discards e27f0810bc39 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards 04afdbad2452 202: onsuccess: #2431: 1: Success after linux: 944 commits discards c8603e9b7758 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards 7f905c093dc2 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards 749c33000664 199: onsuccess: #2363: 1: Success after binutils/gcc/linux [...] discards c7dfe3b4ec3c 198: onsuccess: #2360: 1: Success after binutils/gcc/linux [...] discards 05dd44144ca1 197: onsuccess: #2348: 1: Success after linux: 190 commits discards 34a83ad0ffbf 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: [...] discards 1bec153ea1b4 195: onsuccess: #2341: 1: Success after binutils/gcc/linux [...] discards 95b6c4c803ca 194: onsuccess: #2340: 1: Success after binutils/gcc/linux [...] discards fb9793736582 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc [...] discards 01c33f5a92da 192: onsuccess: #2338: 1: Success after binutils/gcc/linux [...] discards 2866221e43fd 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards 1a497c50cadd 190: onsuccess: #2330: 1: Success after binutils/gcc/linux [...] discards 685c489958e4 189: onsuccess: #2299: 1: Success after binutils/gcc/linux [...] discards 7fbcafca3f55 188: onsuccess: #2295: 1: Success after binutils/gcc/linux [...] discards 23a0e32f376a 187: onsuccess: #2294: 1: Success after binutils/gcc/linux [...] discards 031dabb82831 186: onsuccess: #2291: 1: Success after binutils/gcc/linux [...] discards a5cbd6485f93 185: onsuccess: #2290: 1: Success after binutils/gcc/linux [...] discards d136c6d50d1e 184: onsuccess: #2288: 1: Success after binutils/gcc/linux [...] discards 1efb4337ff8c 183: onsuccess: #2270: 1: Success after binutils/gcc/linux [...] discards 449fe536e9f6 182: onsuccess: #2247: 1: Success after binutils/gcc/linux [...] discards ee4b14a95903 181: onsuccess: #2239: 1: Success after binutils/gcc/linux [...] discards ced2a721549f 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc [...] discards 28186bde0b39 179: onsuccess: #2230: 1: Success after binutils/gcc/linux [...] discards 6790a4faae29 178: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] discards 109c6f8eaa58 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards ab8a44140c2d 176: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] discards cf956907e833 175: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] discards 85a5c662b8b3 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: [...] discards 6bcf63033346 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 445c367647da 172: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] discards 4ef243fdb9a1 171: onsuccess: #2206: 1: Success after binutils/gcc/linux [...] discards 7e036ecd76ea 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc [...] discards 219a4ee91384 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc [...] discards 5eb582bf6358 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc [...] discards 68c0a0ad00b0 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qe [...] discards 574e574ce881 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 [...] discards 8570f79398e1 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 8dc8b98cf8bb 164: onsuccess: #2199: 1: Success after binutils/gcc/linux [...] discards d17275f91fcf 163: onsuccess: #2198: 1: Success after binutils/gcc/linux [...] discards 1b08cfe3211d 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc [...] discards 20be04e75693 161: onsuccess: #2196: 1: Success after binutils/gcc/linux [...] discards 8a1a8e65b13b 160: onsuccess: #2195: 1: Success after binutils/gcc/linux [...] discards 5cc1b92c10bf 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 1 [...] discards c04f21ad8bf1 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc [...] discards 46197233e58b 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: [...] discards 653c9d6714b1 156: onsuccess: #2191: 1: Success after binutils/gcc/linux [...] discards 16a1009b306d 155: onsuccess: #2190: 1: Success after binutils/gcc/linux [...] discards 9ff203b18c3e 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: [...] discards 819e4361e3af 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: [...] discards 39cdc6209c35 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 2 [...] discards 4134821176e4 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards c20db0b30cee 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards dfb112fc77cc 149: onsuccess: #2184: 1: Success after binutils/gcc/linux [...] discards 93bca3682c92 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 6 [...] discards 548d67e40d25 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: [...] discards c48837cda3e8 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb [...] discards ed8410037d9c 145: onsuccess: #2180: 1: Success after binutils/gcc/linux [...] discards c0ab40ae359f 144: onsuccess: #2179: 1: Success after binutils/gcc/linux [...] discards d975f0c1c2c6 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/q [...] discards 4a1e49ea7210 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 0c7e3309f760 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: [...] discards 95698cdc21be 140: onsuccess: #2175: 1: Success after binutils/gcc/linux [...] discards 9800ff3692fd 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: [...] new 1c170aee4228 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: [...] new 2b7ba62d05af 140: onsuccess: #2175: 1: Success after binutils/gcc/linux [...] new 082ca95adfd4 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: [...] new 9da606d24aa5 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 65ec56708576 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/q [...] new e47a501b0ab9 144: onsuccess: #2179: 1: Success after binutils/gcc/linux [...] new 46bb581d4396 145: onsuccess: #2180: 1: Success after binutils/gcc/linux [...] new d25717cc0cae 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb [...] new 317525ae7b25 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: [...] new 415f2414f346 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 6 [...] new eab1628f8fa0 149: onsuccess: #2184: 1: Success after binutils/gcc/linux [...] new af95445be5d4 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 2fd0bf4d9c6c 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 982a3761adb0 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 2 [...] new 2376c0c84d19 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: [...] new 9786d4d787e3 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: [...] new 2ec7b3d65f66 155: onsuccess: #2190: 1: Success after binutils/gcc/linux [...] new cc17c43fbe24 156: onsuccess: #2191: 1: Success after binutils/gcc/linux [...] new 8e5269c714c7 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: [...] new 57df48a8120f 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc [...] new d91ec87ef555 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 1 [...] new 583dbf83e809 160: onsuccess: #2195: 1: Success after binutils/gcc/linux [...] new aea2191aca19 161: onsuccess: #2196: 1: Success after binutils/gcc/linux [...] new 69eb6ba36462 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc [...] new ce93a869d575 163: onsuccess: #2198: 1: Success after binutils/gcc/linux [...] new 51fe414d197e 164: onsuccess: #2199: 1: Success after binutils/gcc/linux [...] new 9011567086fc 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 0a4320f41f86 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 [...] new 0b18af17a5c3 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qe [...] new 38308eafffa1 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc [...] new 775d619ff01e 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc [...] new f91cb7e2756e 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc [...] new 5804f3a37e8b 171: onsuccess: #2206: 1: Success after binutils/gcc/linux [...] new 0b0a1a5f1d43 172: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] new 8079ba0eed60 173: onsuccess: #2208: 1: Success after gcc: 10 commits new 270f1bbfdcea 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: [...] new 2fc31336a015 175: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] new e566f60e22ca 176: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] new fe50326c92fa 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new 2b7e1083a376 178: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] new a3314c00a049 179: onsuccess: #2230: 1: Success after binutils/gcc/linux [...] new b877182b246e 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc [...] new 7796d310ff2b 181: onsuccess: #2239: 1: Success after binutils/gcc/linux [...] new 6a3d9717e1a3 182: onsuccess: #2247: 1: Success after binutils/gcc/linux [...] new 94598aefd45c 183: onsuccess: #2270: 1: Success after binutils/gcc/linux [...] new 31f45b8f89cf 184: onsuccess: #2288: 1: Success after binutils/gcc/linux [...] new 87ed578bac68 185: onsuccess: #2290: 1: Success after binutils/gcc/linux [...] new afb2fefdf696 186: onsuccess: #2291: 1: Success after binutils/gcc/linux [...] new 7cb9bd9ab963 187: onsuccess: #2294: 1: Success after binutils/gcc/linux [...] new ffc47a46422b 188: onsuccess: #2295: 1: Success after binutils/gcc/linux [...] new 4968dbed1034 189: onsuccess: #2299: 1: Success after binutils/gcc/linux [...] new 9f850ee279f8 190: onsuccess: #2330: 1: Success after binutils/gcc/linux [...] new 1974d4a77632 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new 9eead97e62e0 192: onsuccess: #2338: 1: Success after binutils/gcc/linux [...] new bee3e0f276a2 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc [...] new 4331f974ccaa 194: onsuccess: #2340: 1: Success after binutils/gcc/linux [...] new 2bd7056beecf 195: onsuccess: #2341: 1: Success after binutils/gcc/linux [...] new 287343f9aa6c 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: [...] new a6814c01d55f 197: onsuccess: #2348: 1: Success after linux: 190 commits new 5e518f0a1ea4 198: onsuccess: #2360: 1: Success after binutils/gcc/linux [...] new 7f2e1e4d00a1 199: onsuccess: #2363: 1: Success after binutils/gcc/linux [...] new f0247b0608f3 200: onsuccess: #2427: 1: Success after binutils: 274 commits new 22ac5ed94353 201: onsuccess: #2430: 1: Success after glibc: 26 commits new 65fab6855e2d 202: onsuccess: #2431: 1: Success after linux: 944 commits new 5b267dd6ba1d 203: onsuccess: #2433: 1: Success after binutils: 27 commits new 6035b1c3aae7 204: onsuccess: #2435: 1: Success after linux: 3 commits new 8554aaf0f838 205: onsuccess: #2444: 1: Success after binutils/gcc/linux [...] new a6dc8e19c198 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc [...] new 5b5df1992c7e 207: onsuccess: #2446: 1: Success after binutils/gcc/linux [...] new 41156105407c 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: [...] new 34c5d36e149f 209: onsuccess: #2448: 1: Success after binutils/gcc/linux [...] new 9025c4741e0b 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: [...] new d65770796a4b 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new f16305d5d57d 212: onsuccess: #2451: 1: Success after binutils/gcc/linux [...] new c658ed1408d8 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: [...] new 987a1db73e8b 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc [...] new 157cc2e9a211 215: onsuccess: #2455: 1: Success after binutils: 3 commits new 2b67534644ad 216: onsuccess: #2457: 1: Success after linux: 1736 commits new 5c5aac28c072 217: onsuccess: #2459: 1: Success after binutils: 3 commits new 2765e9829b5f 218: onsuccess: #2461: 1: Success after linux: 916 commits new 29e74ffce393 219: onsuccess: #2463: 1: Success after binutils: 3 commits new d6747feaabd8 220: onsuccess: #2465: 1: Success after linux: 572 commits new 1e63974accb6 221: onsuccess: #2467: 1: Success after binutils: 3 commits new 49926335880f 222: onsuccess: #2469: 1: Success after binutils/gcc/linux [...] new 2eeca990561a 223: onsuccess: #2470: 1: Success after binutils/gcc/linux [...] new 908838598702 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: [...] new fa9ed8785d98 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new 3f2ab46d5a4f 226: onsuccess: #2473: 1: Success after binutils/gcc/linux [...] new d4f6cdd90633 227: onsuccess: #2474: 1: Success after gcc: 2 commits new e40ecb320648 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/q [...] new 8c625b832ef2 229: onsuccess: #2476: 1: Success after binutils/gcc/linux [...] new 511fd9b37564 230: onsuccess: #2477: 1: Success after binutils/gcc/linux [...] new f20baee0a564 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/q [...] new c12cc75c60b7 232: onsuccess: #2480: 1: Success after binutils/gcc/linux [...] new 29af24afd4ab 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/q [...] new 2042f381ea97 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 9d96c53ad4f0 235: onsuccess: #2483: 1: Success after linux: 108 commits new 01ad5e0a9032 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 2dab1b890696 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/q [...] new 677b6b2681ad 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: [...] new 645c11cc170d 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: [...] new b61ce124277e 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 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 (6950fdc42a6b) \ 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 1764 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 32160 -> 32032 bytes 04-build_abe-stage1/console.log.xz | Bin 73256 -> 73076 bytes 06-build_abe-linux/console.log.xz | Bin 8628 -> 8604 bytes 07-build_abe-glibc/console.log.xz | Bin 243284 -> 243632 bytes 08-build_abe-stage2/console.log.xz | Bin 204160 -> 204088 bytes 09-build_abe-gdb/console.log.xz | Bin 39380 -> 39148 bytes 10-build_abe-qemu/console.log.xz | Bin 31408 -> 31096 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3912 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2804 -> 2940 bytes 13-check_regression/console.log.xz | Bin 5988 -> 5924 bytes 13-check_regression/fails.sum | 17 +- 13-check_regression/mail-body.txt | 114 +- 13-check_regression/results.compare | 44 +- 13-check_regression/results.compare2 | 50 +- 13-check_regression/results.regressions | 44 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 116 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 44 +- sumfiles/g++.log.xz | Bin 3412980 -> 3438904 bytes sumfiles/g++.sum | 69 +- sumfiles/gcc.log.xz | Bin 3037112 -> 3019076 bytes sumfiles/gcc.sum | 4333 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1038344 -> 1032408 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214688 -> 214776 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2696 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 425736 -> 421208 bytes sumfiles/libstdc++.sum | 8 +- 40 files changed, 2461 insertions(+), 2490 deletions(-)