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 05480db981cc 235: onsuccess: #2483: 1: Success after linux: 108 commits discards a91721ea04c1 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards 664bf0d05f8b 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/q [...] discards 0ae7294dffa7 232: onsuccess: #2480: 1: Success after binutils/gcc/linux [...] discards 24920e1afabe 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/q [...] discards 74099d885020 230: onsuccess: #2477: 1: Success after binutils/gcc/linux [...] discards f25a7fcf0f11 229: onsuccess: #2476: 1: Success after binutils/gcc/linux [...] discards 9bab29d66ff5 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/q [...] discards 0391c6c787b7 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards 63deabcea3ee 226: onsuccess: #2473: 1: Success after binutils/gcc/linux [...] discards 41af2ba85fee 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards f576cbc9f95b 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: [...] discards b9e0f8a480f9 223: onsuccess: #2470: 1: Success after binutils/gcc/linux [...] discards 9e7851859900 222: onsuccess: #2469: 1: Success after binutils/gcc/linux [...] discards f6a04f184333 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards a4f3e77cb694 220: onsuccess: #2465: 1: Success after linux: 572 commits discards af3f67c3dfc8 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards 6d0b11bc9ca7 218: onsuccess: #2461: 1: Success after linux: 916 commits discards 13e0c043ee7a 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards c9e03b0c07b4 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards 9b0b35b5d64d 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards 02a2f202fe65 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc [...] discards 93d69d99f5c7 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: [...] discards 642aac5ad24f 212: onsuccess: #2451: 1: Success after binutils/gcc/linux [...] discards cd05a9d37afd 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards 17b371a13fee 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: [...] discards b21b20050d33 209: onsuccess: #2448: 1: Success after binutils/gcc/linux [...] discards 61f6b30e96ef 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: [...] discards 187a0bd6ea5a 207: onsuccess: #2446: 1: Success after binutils/gcc/linux [...] discards 662935a259dc 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc [...] discards 9a45c7e1462b 205: onsuccess: #2444: 1: Success after binutils/gcc/linux [...] discards cbba783fadc3 204: onsuccess: #2435: 1: Success after linux: 3 commits discards cfeacf3e76f9 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards d424e80636e1 202: onsuccess: #2431: 1: Success after linux: 944 commits discards 94f6a03dff3c 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards efb46aea24e9 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards 0937708d913c 199: onsuccess: #2363: 1: Success after binutils/gcc/linux [...] discards 836bade184f3 198: onsuccess: #2360: 1: Success after binutils/gcc/linux [...] discards 1982eeedd78f 197: onsuccess: #2348: 1: Success after linux: 190 commits discards 379a7dbfb1ff 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: [...] discards 8b792baa0fff 195: onsuccess: #2341: 1: Success after binutils/gcc/linux [...] discards a9e38639804c 194: onsuccess: #2340: 1: Success after binutils/gcc/linux [...] discards a20fd05362cb 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc [...] discards c26cde125713 192: onsuccess: #2338: 1: Success after binutils/gcc/linux [...] discards c863c181aee5 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards c3f0842a1dfb 190: onsuccess: #2330: 1: Success after binutils/gcc/linux [...] discards ced0082325c6 189: onsuccess: #2299: 1: Success after binutils/gcc/linux [...] discards 54e2c09549ed 188: onsuccess: #2295: 1: Success after binutils/gcc/linux [...] discards b17d3d53b4ef 187: onsuccess: #2294: 1: Success after binutils/gcc/linux [...] discards a355d8fee0df 186: onsuccess: #2291: 1: Success after binutils/gcc/linux [...] discards 8dbdabd12821 185: onsuccess: #2290: 1: Success after binutils/gcc/linux [...] discards 2a9a7b95d32c 184: onsuccess: #2288: 1: Success after binutils/gcc/linux [...] discards 98933741ed6d 183: onsuccess: #2270: 1: Success after binutils/gcc/linux [...] discards d74b2dee51c1 182: onsuccess: #2247: 1: Success after binutils/gcc/linux [...] discards 7f2d87f253ad 181: onsuccess: #2239: 1: Success after binutils/gcc/linux [...] discards 523f59024e54 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc [...] discards 83b709169452 179: onsuccess: #2230: 1: Success after binutils/gcc/linux [...] discards ff613413009f 178: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] discards e838f3747d69 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards eb4af4f4aceb 176: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] discards 9520933e1ac3 175: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] discards 58644466f42d 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: [...] discards 3ff90628f962 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards ed86b36d7cde 172: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] discards 3d90942f8dc0 171: onsuccess: #2206: 1: Success after binutils/gcc/linux [...] discards ae87a6042d4b 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc [...] discards 8cea94703d13 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc [...] discards ecf136ab6cac 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc [...] discards e52a275b6a99 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qe [...] discards 6e6681faa5c9 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 [...] discards 78355b3da323 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 479a3b5bea8b 164: onsuccess: #2199: 1: Success after binutils/gcc/linux [...] discards 0be85bad8b3f 163: onsuccess: #2198: 1: Success after binutils/gcc/linux [...] discards 331ac83d4971 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc [...] discards 2de9b051faa7 161: onsuccess: #2196: 1: Success after binutils/gcc/linux [...] discards 1f355d9f3571 160: onsuccess: #2195: 1: Success after binutils/gcc/linux [...] discards 6494e7e0ddee 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 1 [...] discards fae9c13a2768 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc [...] discards 43dcce4d408f 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: [...] discards 8cbf8deece99 156: onsuccess: #2191: 1: Success after binutils/gcc/linux [...] discards cfc8609a8b6c 155: onsuccess: #2190: 1: Success after binutils/gcc/linux [...] discards d163f9997504 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: [...] discards 38b7d518514d 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: [...] discards 019aeea9a699 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 2 [...] discards 68665f590eac 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 7a95650df3ec 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 36540cf709cf 149: onsuccess: #2184: 1: Success after binutils/gcc/linux [...] discards 2d0b11f0dc85 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 6 [...] discards daa7d00832e0 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: [...] discards 1eff3435a988 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb [...] discards bae69f4cb3bf 145: onsuccess: #2180: 1: Success after binutils/gcc/linux [...] discards 46ee5686f66e 144: onsuccess: #2179: 1: Success after binutils/gcc/linux [...] discards 6e838a45dd1f 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/q [...] discards 6e2509653469 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 6146aaf97eac 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: [...] discards c8d695d958a9 140: onsuccess: #2175: 1: Success after binutils/gcc/linux [...] discards ae73c9280f33 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: [...] discards 57489713c1d7 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: [...] discards e7440081b5f2 137: onsuccess: #2172: 1: Success after binutils/gcc/linux [...] discards eaed85a8fed3 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/q [...] discards 4451d2515aff 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 [...] new 159623d71471 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 [...] new c2636e32ba6d 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/q [...] new f9270b1f38ab 137: onsuccess: #2172: 1: Success after binutils/gcc/linux [...] new b7808e5c78b3 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: [...] new 0a6b72d5877a 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: [...] new c2763438ce07 140: onsuccess: #2175: 1: Success after binutils/gcc/linux [...] new 8e0000a25e61 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: [...] new 14534eb71cee 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new afd353c2bfb0 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/q [...] new 14237cee2972 144: onsuccess: #2179: 1: Success after binutils/gcc/linux [...] new 54f34554f441 145: onsuccess: #2180: 1: Success after binutils/gcc/linux [...] new 072d4104b7be 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb [...] new d8929a60b748 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: [...] new 276d372d9794 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 6 [...] new c303bc8e62aa 149: onsuccess: #2184: 1: Success after binutils/gcc/linux [...] new d693c9d0e1a9 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 716d789c7d23 151: onsuccess: #2186: 1: Success after gcc: 2 commits new e4d726515e78 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 2 [...] new a72178afe25b 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: [...] new f276dc8b79ff 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: [...] new 55806516f524 155: onsuccess: #2190: 1: Success after binutils/gcc/linux [...] new caec00940011 156: onsuccess: #2191: 1: Success after binutils/gcc/linux [...] new 66a86f13c9ff 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: [...] new 6e178829e428 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc [...] new f602d19e36be 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 1 [...] new a7024584f764 160: onsuccess: #2195: 1: Success after binutils/gcc/linux [...] new 9600a46f64a6 161: onsuccess: #2196: 1: Success after binutils/gcc/linux [...] new ca66ae0cab8e 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc [...] new c1bfb50ebbf0 163: onsuccess: #2198: 1: Success after binutils/gcc/linux [...] new 9ab3f9f7df9c 164: onsuccess: #2199: 1: Success after binutils/gcc/linux [...] new 9042c41405c6 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new b60ee463b070 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 [...] new 7f546425d292 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qe [...] new 1b9809626d49 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc [...] new ffdaf0800495 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc [...] new c56334a3af20 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc [...] new e3bc1b26221e 171: onsuccess: #2206: 1: Success after binutils/gcc/linux [...] new 901f8f80b3cf 172: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] new 68f5ee2ad20e 173: onsuccess: #2208: 1: Success after gcc: 10 commits new 4f251c4a4aa3 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: [...] new f2a88fcd0e9a 175: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] new ec1950ec59b3 176: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] new 0c8104da3b6f 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new 38922da70640 178: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] new 914d37784917 179: onsuccess: #2230: 1: Success after binutils/gcc/linux [...] new 27c6b5aaa6fa 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc [...] new 906a4538d707 181: onsuccess: #2239: 1: Success after binutils/gcc/linux [...] new e0a30c954630 182: onsuccess: #2247: 1: Success after binutils/gcc/linux [...] new df41a6616998 183: onsuccess: #2270: 1: Success after binutils/gcc/linux [...] new 676b056180f9 184: onsuccess: #2288: 1: Success after binutils/gcc/linux [...] new 17e4e5688a6d 185: onsuccess: #2290: 1: Success after binutils/gcc/linux [...] new 5c10ed66359e 186: onsuccess: #2291: 1: Success after binutils/gcc/linux [...] new cf0035aa4adb 187: onsuccess: #2294: 1: Success after binutils/gcc/linux [...] new 608995f33f8e 188: onsuccess: #2295: 1: Success after binutils/gcc/linux [...] new 2547fb541330 189: onsuccess: #2299: 1: Success after binutils/gcc/linux [...] new a0aacbb9a6e8 190: onsuccess: #2330: 1: Success after binutils/gcc/linux [...] new b0f67b959aab 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new 794a73126571 192: onsuccess: #2338: 1: Success after binutils/gcc/linux [...] new e280d8fc0256 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc [...] new acff68b9ce23 194: onsuccess: #2340: 1: Success after binutils/gcc/linux [...] new 2cf6afe7d088 195: onsuccess: #2341: 1: Success after binutils/gcc/linux [...] new d467e6597b15 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: [...] new 3376e92b2c19 197: onsuccess: #2348: 1: Success after linux: 190 commits new 41dac5803c91 198: onsuccess: #2360: 1: Success after binutils/gcc/linux [...] new 2c7cac22c98e 199: onsuccess: #2363: 1: Success after binutils/gcc/linux [...] new f6bb67742b50 200: onsuccess: #2427: 1: Success after binutils: 274 commits new 3babb90102ac 201: onsuccess: #2430: 1: Success after glibc: 26 commits new 29e3206042cd 202: onsuccess: #2431: 1: Success after linux: 944 commits new 8b8767eef1d0 203: onsuccess: #2433: 1: Success after binutils: 27 commits new a789563b5469 204: onsuccess: #2435: 1: Success after linux: 3 commits new ca8111ed0ce1 205: onsuccess: #2444: 1: Success after binutils/gcc/linux [...] new 7e34b9b66744 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc [...] new 094f6e55f5aa 207: onsuccess: #2446: 1: Success after binutils/gcc/linux [...] new d40b06bf827b 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: [...] new cf623ccd1103 209: onsuccess: #2448: 1: Success after binutils/gcc/linux [...] new 6213e5d1ca1d 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: [...] new 3d9970fcbb2f 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new bfc671869a30 212: onsuccess: #2451: 1: Success after binutils/gcc/linux [...] new c2394e00a3d6 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: [...] new 0a3da19b286b 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc [...] new c82cc3c96b8f 215: onsuccess: #2455: 1: Success after binutils: 3 commits new 4821c737c0b5 216: onsuccess: #2457: 1: Success after linux: 1736 commits new bb0b16958022 217: onsuccess: #2459: 1: Success after binutils: 3 commits new c6f17b3ea12f 218: onsuccess: #2461: 1: Success after linux: 916 commits new a40d1d62f56a 219: onsuccess: #2463: 1: Success after binutils: 3 commits new 9fa3a3c465bd 220: onsuccess: #2465: 1: Success after linux: 572 commits new 8ec585a28fb9 221: onsuccess: #2467: 1: Success after binutils: 3 commits new c54eeccc1066 222: onsuccess: #2469: 1: Success after binutils/gcc/linux [...] new 2031d440e3aa 223: onsuccess: #2470: 1: Success after binutils/gcc/linux [...] new 1820bfb73351 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: [...] new c33545c9b0b6 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new d3e6ca5c043f 226: onsuccess: #2473: 1: Success after binutils/gcc/linux [...] new dca9950515ee 227: onsuccess: #2474: 1: Success after gcc: 2 commits new cd8bb589a3de 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/q [...] new eac51b695714 229: onsuccess: #2476: 1: Success after binutils/gcc/linux [...] new b46d8c7186a4 230: onsuccess: #2477: 1: Success after binutils/gcc/linux [...] new 9563bb532137 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/q [...] new 283a806994de 232: onsuccess: #2480: 1: Success after binutils/gcc/linux [...] new ff662e1f503b 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/q [...] new f76a0dbf5b95 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 11b3b8d33798 235: onsuccess: #2483: 1: Success after linux: 108 commits new 0346094795b5 236: onsuccess: #2484: 1: Success after gcc: 2 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 (05480db981cc) \ 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 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 32572 -> 32300 bytes 04-build_abe-stage1/console.log.xz | Bin 73248 -> 73144 bytes 06-build_abe-linux/console.log.xz | Bin 8628 -> 8620 bytes 07-build_abe-glibc/console.log.xz | Bin 243540 -> 243520 bytes 08-build_abe-stage2/console.log.xz | Bin 204096 -> 204308 bytes 09-build_abe-gdb/console.log.xz | Bin 39628 -> 39836 bytes 10-build_abe-qemu/console.log.xz | Bin 31548 -> 31968 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3968 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2884 -> 2916 bytes 13-check_regression/console.log.xz | Bin 9664 -> 5880 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 13 +- 13-check_regression/mail-body.txt | 166 +- 13-check_regression/results.compare | 112 +- 13-check_regression/results.compare2 | 758 +---- 13-check_regression/results.regressions | 94 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 168 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 +- results | 94 +- sumfiles/g++.log.xz | Bin 3441732 -> 3411176 bytes sumfiles/g++.sum | 120 +- sumfiles/gcc.log.xz | Bin 3030528 -> 3037844 bytes sumfiles/gcc.sum | 5279 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1034996 -> 1039636 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214772 -> 214600 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2696 -> 2696 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 432792 -> 433600 bytes sumfiles/libstdc++.sum | 8 +- 40 files changed, 2971 insertions(+), 3949 deletions(-)