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 4fdc0d110425 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: [...] discards 25f92b21f1c2 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: [...] discards a24ed22e2359 244: onsuccess: #2492: 1: Success after binutils/gcc/linux [...] discards fad600b0e926 243: onsuccess: #2491: 1: Success after binutils/gcc/linux [...] discards fa7ca31052d0 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: [...] discards cfad8cb40e8b 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc [...] discards 78dc2a975cfb 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 9a050c08f804 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: [...] discards c909efb14aaa 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: [...] discards 5fa26ee1c096 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/q [...] discards d25c79a390ed 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 98374c6d1509 235: onsuccess: #2483: 1: Success after linux: 108 commits discards 854db103a4ce 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards c2d8de73cd04 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/q [...] discards 0e2fcbbe09db 232: onsuccess: #2480: 1: Success after binutils/gcc/linux [...] discards 7ee3b9fc9b3a 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/q [...] discards b48b687da633 230: onsuccess: #2477: 1: Success after binutils/gcc/linux [...] discards 73e3f54ab0ce 229: onsuccess: #2476: 1: Success after binutils/gcc/linux [...] discards 3ea438d8e124 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/q [...] discards 586a5ec5f295 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards 8419a18ab6ba 226: onsuccess: #2473: 1: Success after binutils/gcc/linux [...] discards 1662fa243f80 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards 35eeff875535 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: [...] discards 4b65abb2a22a 223: onsuccess: #2470: 1: Success after binutils/gcc/linux [...] discards 6adaac5fb013 222: onsuccess: #2469: 1: Success after binutils/gcc/linux [...] discards 33a35c310aea 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards 4bfa4af27b8c 220: onsuccess: #2465: 1: Success after linux: 572 commits discards da26d644d8ee 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards b04a602c1902 218: onsuccess: #2461: 1: Success after linux: 916 commits discards 85d72d9aaf4e 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards 84faa5ae8c62 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards 0d15c4800a36 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards 5219f35c460f 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc [...] discards cd8e373aa399 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: [...] discards d5df6d744b30 212: onsuccess: #2451: 1: Success after binutils/gcc/linux [...] discards 7e8165962a13 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards 7cefc2397304 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: [...] discards 973a6b9940f6 209: onsuccess: #2448: 1: Success after binutils/gcc/linux [...] discards 6f8b3fe4d0cd 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: [...] discards 36857b0771d8 207: onsuccess: #2446: 1: Success after binutils/gcc/linux [...] discards 69eade064b7f 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc [...] discards ca2fefbd22c6 205: onsuccess: #2444: 1: Success after binutils/gcc/linux [...] discards ee57fcfaa221 204: onsuccess: #2435: 1: Success after linux: 3 commits discards 7cbdfacabedb 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards a2fd54ae7cb4 202: onsuccess: #2431: 1: Success after linux: 944 commits discards 98a5be3f7217 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards c066776b7d1e 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards f09b9b098e29 199: onsuccess: #2363: 1: Success after binutils/gcc/linux [...] discards 3cef5eb1c2c7 198: onsuccess: #2360: 1: Success after binutils/gcc/linux [...] discards d311ed408fd3 197: onsuccess: #2348: 1: Success after linux: 190 commits discards 6ad4bbf29856 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: [...] discards 85b5786c73aa 195: onsuccess: #2341: 1: Success after binutils/gcc/linux [...] discards d1dafb83e680 194: onsuccess: #2340: 1: Success after binutils/gcc/linux [...] discards 14f3cb28ffb9 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc [...] discards e0a95d0c5131 192: onsuccess: #2338: 1: Success after binutils/gcc/linux [...] discards d07601ad1bcb 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards 21ee896d038a 190: onsuccess: #2330: 1: Success after binutils/gcc/linux [...] discards 5d32185d8933 189: onsuccess: #2299: 1: Success after binutils/gcc/linux [...] discards 9456232aa546 188: onsuccess: #2295: 1: Success after binutils/gcc/linux [...] discards 12e41145b7ff 187: onsuccess: #2294: 1: Success after binutils/gcc/linux [...] discards 496865595445 186: onsuccess: #2291: 1: Success after binutils/gcc/linux [...] discards 04dddebf262c 185: onsuccess: #2290: 1: Success after binutils/gcc/linux [...] discards 449bddf24df1 184: onsuccess: #2288: 1: Success after binutils/gcc/linux [...] discards fec4d0a7d165 183: onsuccess: #2270: 1: Success after binutils/gcc/linux [...] discards ce1b5dc5c904 182: onsuccess: #2247: 1: Success after binutils/gcc/linux [...] discards d52a13162fe4 181: onsuccess: #2239: 1: Success after binutils/gcc/linux [...] discards b061e2d78546 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc [...] discards a7c5ea192c51 179: onsuccess: #2230: 1: Success after binutils/gcc/linux [...] discards 24a22f9d669a 178: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] discards a17850d785ce 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards 29e81768f80b 176: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] discards 2fca50e66e8c 175: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] discards ddcbee2d37fb 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: [...] discards 590f35f1eb87 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards bc2e634ef143 172: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] discards e3be40241c3d 171: onsuccess: #2206: 1: Success after binutils/gcc/linux [...] discards c092fa210e8a 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc [...] discards 98bf7a08999e 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc [...] discards 608a64a62b8a 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc [...] discards 711ba736014c 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qe [...] discards 504a89fef9cd 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 [...] discards 876b08980a56 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 79c1751ef1e6 164: onsuccess: #2199: 1: Success after binutils/gcc/linux [...] discards 758704bf16ee 163: onsuccess: #2198: 1: Success after binutils/gcc/linux [...] discards bae7d16d2857 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc [...] discards 2154d63b7e46 161: onsuccess: #2196: 1: Success after binutils/gcc/linux [...] discards 6ac6ef8617c1 160: onsuccess: #2195: 1: Success after binutils/gcc/linux [...] discards f75f010e9d8f 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 1 [...] discards 09c3dc48e147 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc [...] discards 8eecda686977 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: [...] discards b72c58e0bb49 156: onsuccess: #2191: 1: Success after binutils/gcc/linux [...] discards bda730901f2d 155: onsuccess: #2190: 1: Success after binutils/gcc/linux [...] discards 27b78e875da5 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: [...] discards 102adbf172d0 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: [...] discards 5f50bdce082e 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 2 [...] discards d55b4cb35d41 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards c21ec9e7bb87 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards fa260befba3a 149: onsuccess: #2184: 1: Success after binutils/gcc/linux [...] discards 8cb0ab22e61d 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 6 [...] discards 6712d054035e 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: [...] discards 850341afcea2 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb [...] new b75bfa69ac08 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb [...] new ce68c289e64f 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: [...] new 9938f6724408 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 6 [...] new 45d50003f4c7 149: onsuccess: #2184: 1: Success after binutils/gcc/linux [...] new d3b6994cc2d0 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 29f31815ae16 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 580aab613dd5 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 2 [...] new 89d43a23f05b 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: [...] new 8fa3e02272cf 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: [...] new a03063c461d6 155: onsuccess: #2190: 1: Success after binutils/gcc/linux [...] new 97781d1b6c0b 156: onsuccess: #2191: 1: Success after binutils/gcc/linux [...] new a0c36c26a317 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: [...] new 929829883693 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc [...] new 60df589af9b7 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 1 [...] new e3708ec9218e 160: onsuccess: #2195: 1: Success after binutils/gcc/linux [...] new e1dcb955289d 161: onsuccess: #2196: 1: Success after binutils/gcc/linux [...] new c467f1dff88f 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc [...] new fce765b1da2f 163: onsuccess: #2198: 1: Success after binutils/gcc/linux [...] new 05750e8cfe53 164: onsuccess: #2199: 1: Success after binutils/gcc/linux [...] new c85de1661e53 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new c5361a0847af 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 [...] new 03ffa12800af 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qe [...] new e31f23ee21a0 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc [...] new adfd8d28099d 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc [...] new f736a6c6fecc 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc [...] new 7b6c96d6d34b 171: onsuccess: #2206: 1: Success after binutils/gcc/linux [...] new 4f51ce23e482 172: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] new e3e04d375551 173: onsuccess: #2208: 1: Success after gcc: 10 commits new d6b548a7ffe1 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: [...] new ba3dd6fea906 175: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] new bb36d5dac572 176: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] new 82aeacdb6574 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new dd5adf302222 178: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] new d81c79d62f9b 179: onsuccess: #2230: 1: Success after binutils/gcc/linux [...] new 9d31b84173c0 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc [...] new 42c1934de566 181: onsuccess: #2239: 1: Success after binutils/gcc/linux [...] new 7534f1acf5e7 182: onsuccess: #2247: 1: Success after binutils/gcc/linux [...] new 2e6cf1823a1a 183: onsuccess: #2270: 1: Success after binutils/gcc/linux [...] new 0bd88d37be5d 184: onsuccess: #2288: 1: Success after binutils/gcc/linux [...] new c172828a370c 185: onsuccess: #2290: 1: Success after binutils/gcc/linux [...] new 618365551d9f 186: onsuccess: #2291: 1: Success after binutils/gcc/linux [...] new 26b47d7e82dd 187: onsuccess: #2294: 1: Success after binutils/gcc/linux [...] new 0136f79b010c 188: onsuccess: #2295: 1: Success after binutils/gcc/linux [...] new ae409ac4d5cd 189: onsuccess: #2299: 1: Success after binutils/gcc/linux [...] new 9805cb7c546b 190: onsuccess: #2330: 1: Success after binutils/gcc/linux [...] new c74119211f02 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new aa4431c55bee 192: onsuccess: #2338: 1: Success after binutils/gcc/linux [...] new 2f89840d2f72 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc [...] new e0378190605a 194: onsuccess: #2340: 1: Success after binutils/gcc/linux [...] new ad69528baee3 195: onsuccess: #2341: 1: Success after binutils/gcc/linux [...] new 7a871d68a723 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: [...] new 3c0ce3fa391a 197: onsuccess: #2348: 1: Success after linux: 190 commits new 53ef143c0e66 198: onsuccess: #2360: 1: Success after binutils/gcc/linux [...] new f2dcc4e219ff 199: onsuccess: #2363: 1: Success after binutils/gcc/linux [...] new b5758812bfe7 200: onsuccess: #2427: 1: Success after binutils: 274 commits new 24dcbd865b98 201: onsuccess: #2430: 1: Success after glibc: 26 commits new 807ec45b3eca 202: onsuccess: #2431: 1: Success after linux: 944 commits new 0082c8ebb98e 203: onsuccess: #2433: 1: Success after binutils: 27 commits new 48e23fe5bf3c 204: onsuccess: #2435: 1: Success after linux: 3 commits new 07ff7b8c0c20 205: onsuccess: #2444: 1: Success after binutils/gcc/linux [...] new d22383529a0b 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc [...] new ab143936a17c 207: onsuccess: #2446: 1: Success after binutils/gcc/linux [...] new 414f4b29d64e 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: [...] new 4d15c9b39b47 209: onsuccess: #2448: 1: Success after binutils/gcc/linux [...] new b8c1110ae84e 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: [...] new 4c944ea8fffb 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new 3d58e10c0958 212: onsuccess: #2451: 1: Success after binutils/gcc/linux [...] new 24d4e70e65d7 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: [...] new 9cf690082325 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc [...] new 90f395eead27 215: onsuccess: #2455: 1: Success after binutils: 3 commits new bfc3fb8f976d 216: onsuccess: #2457: 1: Success after linux: 1736 commits new 2ba20a12ba39 217: onsuccess: #2459: 1: Success after binutils: 3 commits new ad697d3978f5 218: onsuccess: #2461: 1: Success after linux: 916 commits new 447c8dc03bd5 219: onsuccess: #2463: 1: Success after binutils: 3 commits new c40d09c34fb2 220: onsuccess: #2465: 1: Success after linux: 572 commits new 8086748c4267 221: onsuccess: #2467: 1: Success after binutils: 3 commits new 034a08469d3a 222: onsuccess: #2469: 1: Success after binutils/gcc/linux [...] new 89024ffbe1a3 223: onsuccess: #2470: 1: Success after binutils/gcc/linux [...] new c6ee4a1c2c40 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: [...] new 56bad0f57a01 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new 5705582ecc0b 226: onsuccess: #2473: 1: Success after binutils/gcc/linux [...] new 56c032e3eb30 227: onsuccess: #2474: 1: Success after gcc: 2 commits new 656f39dc8f47 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/q [...] new 8758df9b3047 229: onsuccess: #2476: 1: Success after binutils/gcc/linux [...] new d7dbf7dfae5a 230: onsuccess: #2477: 1: Success after binutils/gcc/linux [...] new 8cc4f0e476fc 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/q [...] new 24eb7431962c 232: onsuccess: #2480: 1: Success after binutils/gcc/linux [...] new c7e29b79cfc8 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/q [...] new 2e8998bf1227 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 21506034a260 235: onsuccess: #2483: 1: Success after linux: 108 commits new 21526e4d8c3d 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 8a953336fb16 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/q [...] new 4537c9cc990a 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: [...] new 609ef7d3536a 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: [...] new e8acfecf4421 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new dd1c5f58da4d 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc [...] new a0230781f540 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: [...] new e601b61668c8 243: onsuccess: #2491: 1: Success after binutils/gcc/linux [...] new 8dc4f5d3cb35 244: onsuccess: #2492: 1: Success after binutils/gcc/linux [...] new 806dad2dcbad 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: [...] new d823828561a2 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: [...] new 7b7143ffbac3 247: onsuccess: #2495: 1: Success after binutils/gcc/linux [...]

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 (4fdc0d110425) \ 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 1884 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2808 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 32356 -> 32192 bytes 04-build_abe-stage1/console.log.xz | Bin 73972 -> 73488 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 9240 -> 8544 bytes 07-build_abe-glibc/console.log.xz | Bin 245552 -> 244716 bytes 08-build_abe-stage2/console.log.xz | Bin 205312 -> 204496 bytes 09-build_abe-gdb/console.log.xz | Bin 39524 -> 39408 bytes 10-build_abe-qemu/console.log.xz | Bin 31240 -> 31336 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3944 -> 3908 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2816 -> 2984 bytes 13-check_regression/console.log.xz | Bin 6640 -> 7620 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 38 +- 13-check_regression/mail-body.txt | 148 +- 13-check_regression/results.compare | 96 +- 13-check_regression/results.compare2 | 161 +- 13-check_regression/results.regressions | 96 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 150 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 96 +- sumfiles/g++.log.xz | Bin 3421280 -> 3413036 bytes sumfiles/g++.sum | 202 +- sumfiles/gcc.log.xz | Bin 3040116 -> 3034624 bytes sumfiles/gcc.sum | 4631 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1041024 -> 1038504 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 214460 -> 214516 bytes sumfiles/libgomp.sum | 21 +- sumfiles/libitm.log.xz | Bin 2700 -> 2692 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 434128 -> 428204 bytes sumfiles/libstdc++.sum | 78 +- 45 files changed, 3011 insertions(+), 2882 deletions(-)