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 defa9b711182 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: [...] discards 718336f03192 244: onsuccess: #2492: 1: Success after binutils/gcc/linux [...] discards d9810fba9ea2 243: onsuccess: #2491: 1: Success after binutils/gcc/linux [...] discards 80e77d3d9c2e 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: [...] discards 24bafd34ac09 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc [...] discards dfaabe97ca83 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 81749ee72615 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: [...] discards 2c64f652b835 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: [...] discards d9a525bc07b9 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/q [...] discards 11077f2ee3a1 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 1dedb5becd61 235: onsuccess: #2483: 1: Success after linux: 108 commits discards 238b7de75120 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards b340ef4bc933 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/q [...] discards 9ccabb8a4ade 232: onsuccess: #2480: 1: Success after binutils/gcc/linux [...] discards aa25bc0bffcb 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/q [...] discards eee806afaf5c 230: onsuccess: #2477: 1: Success after binutils/gcc/linux [...] discards 3524560ed74c 229: onsuccess: #2476: 1: Success after binutils/gcc/linux [...] discards 8a3a02b9b645 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/q [...] discards 56b271fcf005 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards 0dd95df68ed3 226: onsuccess: #2473: 1: Success after binutils/gcc/linux [...] discards 5586b3070acd 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards 25349e208e83 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: [...] discards 6f7773de0b33 223: onsuccess: #2470: 1: Success after binutils/gcc/linux [...] discards 4d5a1d40995e 222: onsuccess: #2469: 1: Success after binutils/gcc/linux [...] discards 014860a48eae 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards 33579ec642db 220: onsuccess: #2465: 1: Success after linux: 572 commits discards 3e6334d6656a 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards cd271d91986e 218: onsuccess: #2461: 1: Success after linux: 916 commits discards e5a75c6eb6c8 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards e2698588df80 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards 7c758b863b18 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards d492cbc5308f 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc [...] discards f7ddaee97837 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: [...] discards 58b0d323d125 212: onsuccess: #2451: 1: Success after binutils/gcc/linux [...] discards 675958d04b6e 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards 5898caf5efa0 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: [...] discards 2c557a499a55 209: onsuccess: #2448: 1: Success after binutils/gcc/linux [...] discards 50f8f31126d8 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: [...] discards 2c4ee23f71de 207: onsuccess: #2446: 1: Success after binutils/gcc/linux [...] discards 638657d72b3d 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc [...] discards 44bf76533e79 205: onsuccess: #2444: 1: Success after binutils/gcc/linux [...] discards 12cda3c556f6 204: onsuccess: #2435: 1: Success after linux: 3 commits discards 088f8d982a6b 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards c4bc4b8ddd48 202: onsuccess: #2431: 1: Success after linux: 944 commits discards 0a7c21515613 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards 24e9afbe55fe 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards bac93d59fd8b 199: onsuccess: #2363: 1: Success after binutils/gcc/linux [...] discards 73cea7e973f2 198: onsuccess: #2360: 1: Success after binutils/gcc/linux [...] discards 819fba6be1c8 197: onsuccess: #2348: 1: Success after linux: 190 commits discards 69aa439e62a2 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: [...] discards 66398e7e14cc 195: onsuccess: #2341: 1: Success after binutils/gcc/linux [...] discards a64bda68764d 194: onsuccess: #2340: 1: Success after binutils/gcc/linux [...] discards 55043f2e2568 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc [...] discards 25603d6511b9 192: onsuccess: #2338: 1: Success after binutils/gcc/linux [...] discards e9a01b9384aa 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards 7b0da2394101 190: onsuccess: #2330: 1: Success after binutils/gcc/linux [...] discards b6a50b8e81c5 189: onsuccess: #2299: 1: Success after binutils/gcc/linux [...] discards c7113d3135ed 188: onsuccess: #2295: 1: Success after binutils/gcc/linux [...] discards 5d9b739b6dde 187: onsuccess: #2294: 1: Success after binutils/gcc/linux [...] discards bbf940c1987e 186: onsuccess: #2291: 1: Success after binutils/gcc/linux [...] discards 34e38583afb0 185: onsuccess: #2290: 1: Success after binutils/gcc/linux [...] discards 2c1296250809 184: onsuccess: #2288: 1: Success after binutils/gcc/linux [...] discards c63ffae17ee8 183: onsuccess: #2270: 1: Success after binutils/gcc/linux [...] discards ff500cc34c77 182: onsuccess: #2247: 1: Success after binutils/gcc/linux [...] discards a25f6d61b68c 181: onsuccess: #2239: 1: Success after binutils/gcc/linux [...] discards 32eb260da4c0 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc [...] discards 45213e40a261 179: onsuccess: #2230: 1: Success after binutils/gcc/linux [...] discards a5f924b27464 178: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] discards 0ec6daa52170 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards f35cbf723a1f 176: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] discards cbf88bd6b44e 175: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] discards 56317adc7d5f 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: [...] discards 0ea82b9082dd 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards aafb9b08a45f 172: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] discards 69ccd026f525 171: onsuccess: #2206: 1: Success after binutils/gcc/linux [...] discards b47a289579ff 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc [...] discards b5a2c46e3450 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc [...] discards db11160d2bfb 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc [...] discards 853bf98ef441 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qe [...] discards 6b221b146401 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 [...] discards 7f9e0c2a86bb 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 306342120982 164: onsuccess: #2199: 1: Success after binutils/gcc/linux [...] discards e807016e027b 163: onsuccess: #2198: 1: Success after binutils/gcc/linux [...] discards e182eb87bb2f 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc [...] discards 6e3fa6f38973 161: onsuccess: #2196: 1: Success after binutils/gcc/linux [...] discards 1beb973c2cde 160: onsuccess: #2195: 1: Success after binutils/gcc/linux [...] discards afc1c29a4d44 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 1 [...] discards cb3406914ff7 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc [...] discards 314cfdd7324c 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: [...] discards 74dda44e971c 156: onsuccess: #2191: 1: Success after binutils/gcc/linux [...] discards 9112c89b78b9 155: onsuccess: #2190: 1: Success after binutils/gcc/linux [...] discards 71113fa50cc0 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: [...] discards 4cb153611c90 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: [...] discards 5ea44261eb61 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 2 [...] discards 0547c10e621c 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 1507bd8d319d 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 02f88612e9fa 149: onsuccess: #2184: 1: Success after binutils/gcc/linux [...] discards e323dc22be31 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 6 [...] discards c17dec035ab7 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: [...] discards b18bf8a68058 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb [...] discards 87b6252a939e 145: onsuccess: #2180: 1: Success after binutils/gcc/linux [...] new 0d06974541ed 145: onsuccess: #2180: 1: Success after binutils/gcc/linux [...] new 850341afcea2 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb [...] new 6712d054035e 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: [...] new 8cb0ab22e61d 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 6 [...] new fa260befba3a 149: onsuccess: #2184: 1: Success after binutils/gcc/linux [...] new c21ec9e7bb87 150: onsuccess: #2185: 1: Success after gcc: 3 commits new d55b4cb35d41 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 5f50bdce082e 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 2 [...] new 102adbf172d0 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: [...] new 27b78e875da5 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: [...] new bda730901f2d 155: onsuccess: #2190: 1: Success after binutils/gcc/linux [...] new b72c58e0bb49 156: onsuccess: #2191: 1: Success after binutils/gcc/linux [...] new 8eecda686977 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: [...] new 09c3dc48e147 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc [...] new f75f010e9d8f 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 1 [...] new 6ac6ef8617c1 160: onsuccess: #2195: 1: Success after binutils/gcc/linux [...] new 2154d63b7e46 161: onsuccess: #2196: 1: Success after binutils/gcc/linux [...] new bae7d16d2857 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc [...] new 758704bf16ee 163: onsuccess: #2198: 1: Success after binutils/gcc/linux [...] new 79c1751ef1e6 164: onsuccess: #2199: 1: Success after binutils/gcc/linux [...] new 876b08980a56 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 504a89fef9cd 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 [...] new 711ba736014c 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qe [...] new 608a64a62b8a 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc [...] new 98bf7a08999e 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc [...] new c092fa210e8a 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc [...] new e3be40241c3d 171: onsuccess: #2206: 1: Success after binutils/gcc/linux [...] new bc2e634ef143 172: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] new 590f35f1eb87 173: onsuccess: #2208: 1: Success after gcc: 10 commits new ddcbee2d37fb 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: [...] new 2fca50e66e8c 175: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] new 29e81768f80b 176: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] new a17850d785ce 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new 24a22f9d669a 178: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] new a7c5ea192c51 179: onsuccess: #2230: 1: Success after binutils/gcc/linux [...] new b061e2d78546 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc [...] new d52a13162fe4 181: onsuccess: #2239: 1: Success after binutils/gcc/linux [...] new ce1b5dc5c904 182: onsuccess: #2247: 1: Success after binutils/gcc/linux [...] new fec4d0a7d165 183: onsuccess: #2270: 1: Success after binutils/gcc/linux [...] new 449bddf24df1 184: onsuccess: #2288: 1: Success after binutils/gcc/linux [...] new 04dddebf262c 185: onsuccess: #2290: 1: Success after binutils/gcc/linux [...] new 496865595445 186: onsuccess: #2291: 1: Success after binutils/gcc/linux [...] new 12e41145b7ff 187: onsuccess: #2294: 1: Success after binutils/gcc/linux [...] new 9456232aa546 188: onsuccess: #2295: 1: Success after binutils/gcc/linux [...] new 5d32185d8933 189: onsuccess: #2299: 1: Success after binutils/gcc/linux [...] new 21ee896d038a 190: onsuccess: #2330: 1: Success after binutils/gcc/linux [...] new d07601ad1bcb 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new e0a95d0c5131 192: onsuccess: #2338: 1: Success after binutils/gcc/linux [...] new 14f3cb28ffb9 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc [...] new d1dafb83e680 194: onsuccess: #2340: 1: Success after binutils/gcc/linux [...] new 85b5786c73aa 195: onsuccess: #2341: 1: Success after binutils/gcc/linux [...] new 6ad4bbf29856 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: [...] new d311ed408fd3 197: onsuccess: #2348: 1: Success after linux: 190 commits new 3cef5eb1c2c7 198: onsuccess: #2360: 1: Success after binutils/gcc/linux [...] new f09b9b098e29 199: onsuccess: #2363: 1: Success after binutils/gcc/linux [...] new c066776b7d1e 200: onsuccess: #2427: 1: Success after binutils: 274 commits new 98a5be3f7217 201: onsuccess: #2430: 1: Success after glibc: 26 commits new a2fd54ae7cb4 202: onsuccess: #2431: 1: Success after linux: 944 commits new 7cbdfacabedb 203: onsuccess: #2433: 1: Success after binutils: 27 commits new ee57fcfaa221 204: onsuccess: #2435: 1: Success after linux: 3 commits new ca2fefbd22c6 205: onsuccess: #2444: 1: Success after binutils/gcc/linux [...] new 69eade064b7f 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc [...] new 36857b0771d8 207: onsuccess: #2446: 1: Success after binutils/gcc/linux [...] new 6f8b3fe4d0cd 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: [...] new 973a6b9940f6 209: onsuccess: #2448: 1: Success after binutils/gcc/linux [...] new 7cefc2397304 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: [...] new 7e8165962a13 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new d5df6d744b30 212: onsuccess: #2451: 1: Success after binutils/gcc/linux [...] new cd8e373aa399 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: [...] new 5219f35c460f 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc [...] new 0d15c4800a36 215: onsuccess: #2455: 1: Success after binutils: 3 commits new 84faa5ae8c62 216: onsuccess: #2457: 1: Success after linux: 1736 commits new 85d72d9aaf4e 217: onsuccess: #2459: 1: Success after binutils: 3 commits new b04a602c1902 218: onsuccess: #2461: 1: Success after linux: 916 commits new da26d644d8ee 219: onsuccess: #2463: 1: Success after binutils: 3 commits new 4bfa4af27b8c 220: onsuccess: #2465: 1: Success after linux: 572 commits new 33a35c310aea 221: onsuccess: #2467: 1: Success after binutils: 3 commits new 6adaac5fb013 222: onsuccess: #2469: 1: Success after binutils/gcc/linux [...] new 4b65abb2a22a 223: onsuccess: #2470: 1: Success after binutils/gcc/linux [...] new 35eeff875535 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: [...] new 1662fa243f80 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new 8419a18ab6ba 226: onsuccess: #2473: 1: Success after binutils/gcc/linux [...] new 586a5ec5f295 227: onsuccess: #2474: 1: Success after gcc: 2 commits new 3ea438d8e124 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/q [...] new 73e3f54ab0ce 229: onsuccess: #2476: 1: Success after binutils/gcc/linux [...] new b48b687da633 230: onsuccess: #2477: 1: Success after binutils/gcc/linux [...] new 7ee3b9fc9b3a 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/q [...] new 0e2fcbbe09db 232: onsuccess: #2480: 1: Success after binutils/gcc/linux [...] new c2d8de73cd04 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/q [...] new 854db103a4ce 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 98374c6d1509 235: onsuccess: #2483: 1: Success after linux: 108 commits new d25c79a390ed 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 5fa26ee1c096 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/q [...] new c909efb14aaa 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: [...] new 9a050c08f804 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: [...] new 78dc2a975cfb 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new cfad8cb40e8b 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc [...] new fa7ca31052d0 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: [...] new fad600b0e926 243: onsuccess: #2491: 1: Success after binutils/gcc/linux [...] new a24ed22e2359 244: onsuccess: #2492: 1: Success after binutils/gcc/linux [...] new 25f92b21f1c2 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: [...] new 4fdc0d110425 246: onsuccess: #2494: 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 (defa9b711182) \ 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 1780 -> 1884 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2808 bytes 03-build_abe-binutils/console.log.xz | Bin 32552 -> 32356 bytes 04-build_abe-stage1/console.log.xz | Bin 73888 -> 73972 bytes 06-build_abe-linux/console.log.xz | Bin 9220 -> 9240 bytes 07-build_abe-glibc/console.log.xz | Bin 244508 -> 245552 bytes 08-build_abe-stage2/console.log.xz | Bin 203612 -> 205312 bytes 09-build_abe-gdb/console.log.xz | Bin 39212 -> 39524 bytes 10-build_abe-qemu/console.log.xz | Bin 31180 -> 31240 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3912 -> 3944 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2680 -> 2816 bytes 13-check_regression/console.log.xz | Bin 6736 -> 6640 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 36 +- 13-check_regression/mail-body.txt | 157 +- 13-check_regression/results.compare | 52 +- 13-check_regression/results.compare2 | 117 +- 13-check_regression/results.regressions | 52 +- 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 | 159 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 52 +- sumfiles/g++.log.xz | Bin 3415084 -> 3421280 bytes sumfiles/g++.sum | 75 +- sumfiles/gcc.log.xz | Bin 3037680 -> 3040116 bytes sumfiles/gcc.sum | 4503 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1033312 -> 1041024 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214640 -> 214460 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2700 -> 2700 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 423316 -> 434128 bytes sumfiles/libstdc++.sum | 12 +- 42 files changed, 2649 insertions(+), 2693 deletions(-)