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 ae0ee150ac4e 243: onsuccess: #2491: 1: Success after binutils/gcc/linux [...] discards 003044abbd57 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: [...] discards 0fbe9e3ea839 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc [...] discards 3bacabb91412 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 099d3f115aa2 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: [...] discards 731b546083ee 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: [...] discards ac8528527551 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/q [...] discards b4e2fc6910fb 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards f5e82daadaec 235: onsuccess: #2483: 1: Success after linux: 108 commits discards 40bfbcd1ec55 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards b1f7ef953409 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/q [...] discards f31bf1b2aef7 232: onsuccess: #2480: 1: Success after binutils/gcc/linux [...] discards 3057152cc025 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/q [...] discards de017cd75ee7 230: onsuccess: #2477: 1: Success after binutils/gcc/linux [...] discards 57c8cd85238a 229: onsuccess: #2476: 1: Success after binutils/gcc/linux [...] discards 230bee753e48 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/q [...] discards 2222ded3fb45 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards f297cc348f10 226: onsuccess: #2473: 1: Success after binutils/gcc/linux [...] discards c91979a2d468 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards 393fd97d5485 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: [...] discards 45a2948085fb 223: onsuccess: #2470: 1: Success after binutils/gcc/linux [...] discards a19db0626ec7 222: onsuccess: #2469: 1: Success after binutils/gcc/linux [...] discards 9e27cd74cea1 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards 99e462edf527 220: onsuccess: #2465: 1: Success after linux: 572 commits discards 201bef1dc770 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards 4d61ead8ca58 218: onsuccess: #2461: 1: Success after linux: 916 commits discards 45b92cd38ac5 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards 83cbf67ebf9b 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards 41555cbfc792 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards 8d77e274ff66 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc [...] discards 0a89aca04d41 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: [...] discards 75ddfd08a795 212: onsuccess: #2451: 1: Success after binutils/gcc/linux [...] discards 6bf33b83dbc7 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards dc7dc1177f79 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: [...] discards 981c2bfab897 209: onsuccess: #2448: 1: Success after binutils/gcc/linux [...] discards e8f3568b7928 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: [...] discards 509a0d256f41 207: onsuccess: #2446: 1: Success after binutils/gcc/linux [...] discards 97f6db3e7ca3 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc [...] discards 357ea9699e05 205: onsuccess: #2444: 1: Success after binutils/gcc/linux [...] discards c3a0a74c4d79 204: onsuccess: #2435: 1: Success after linux: 3 commits discards 02a79c7d5a19 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards 11664ff7bee4 202: onsuccess: #2431: 1: Success after linux: 944 commits discards 131cd13d6fc5 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards 209aa17dfa63 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards 2cc8892db37d 199: onsuccess: #2363: 1: Success after binutils/gcc/linux [...] discards b87accb51a3a 198: onsuccess: #2360: 1: Success after binutils/gcc/linux [...] discards 03ef8708c572 197: onsuccess: #2348: 1: Success after linux: 190 commits discards d15d7658abdd 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: [...] discards a55666d44da1 195: onsuccess: #2341: 1: Success after binutils/gcc/linux [...] discards 029720ab8470 194: onsuccess: #2340: 1: Success after binutils/gcc/linux [...] discards 312363e50983 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc [...] discards cf6c627e5363 192: onsuccess: #2338: 1: Success after binutils/gcc/linux [...] discards fc7c97a0ed03 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards 71269c58a8b7 190: onsuccess: #2330: 1: Success after binutils/gcc/linux [...] discards 32a912ae6a51 189: onsuccess: #2299: 1: Success after binutils/gcc/linux [...] discards 8ace039f7bf5 188: onsuccess: #2295: 1: Success after binutils/gcc/linux [...] discards 9e3b35ad2403 187: onsuccess: #2294: 1: Success after binutils/gcc/linux [...] discards 1ac8c3ddbf9c 186: onsuccess: #2291: 1: Success after binutils/gcc/linux [...] discards c5b99a30e650 185: onsuccess: #2290: 1: Success after binutils/gcc/linux [...] discards 59b9b7f38ff4 184: onsuccess: #2288: 1: Success after binutils/gcc/linux [...] discards 1f69688f598c 183: onsuccess: #2270: 1: Success after binutils/gcc/linux [...] discards a1e15d41e22f 182: onsuccess: #2247: 1: Success after binutils/gcc/linux [...] discards a77c803a9c68 181: onsuccess: #2239: 1: Success after binutils/gcc/linux [...] discards 7d58d376d65d 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc [...] discards 53c0458bed13 179: onsuccess: #2230: 1: Success after binutils/gcc/linux [...] discards 4a2fa2753491 178: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] discards cc7b5d5e6e14 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards 8244fca2110b 176: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] discards ecf9641cde49 175: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] discards 4bc08fd5c321 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: [...] discards ce4458807160 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 51194b2c43a1 172: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] discards bb01396d9c06 171: onsuccess: #2206: 1: Success after binutils/gcc/linux [...] discards d77ce3849bbd 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc [...] discards c6533cc17b7f 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc [...] discards e389fdba1be9 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc [...] discards 003f0f54de3b 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qe [...] discards 4de73dc03844 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 [...] discards c2975e9a0b57 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 560365c1bf20 164: onsuccess: #2199: 1: Success after binutils/gcc/linux [...] discards a69cd75297f6 163: onsuccess: #2198: 1: Success after binutils/gcc/linux [...] discards 732fffa304ca 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc [...] discards d19615b47d5d 161: onsuccess: #2196: 1: Success after binutils/gcc/linux [...] discards 4df7c766cd18 160: onsuccess: #2195: 1: Success after binutils/gcc/linux [...] discards f5a42b6833e1 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 1 [...] discards 463a3addffa4 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc [...] discards f06bc1c98efe 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: [...] discards f581ddb9e649 156: onsuccess: #2191: 1: Success after binutils/gcc/linux [...] discards ba664d16eabc 155: onsuccess: #2190: 1: Success after binutils/gcc/linux [...] discards e6ff8c2aeec8 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: [...] discards e9edd5bbcb87 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: [...] discards 64e077f2398d 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 2 [...] discards d8e2ff4999b5 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 42750da34b75 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 464c550f375b 149: onsuccess: #2184: 1: Success after binutils/gcc/linux [...] discards 67ce07038552 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 6 [...] discards 08f666ae89fb 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: [...] discards 10450e16cb66 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb [...] discards bd1fc977b3f7 145: onsuccess: #2180: 1: Success after binutils/gcc/linux [...] discards a70ecdbbf229 144: onsuccess: #2179: 1: Success after binutils/gcc/linux [...] discards c08475c768bb 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/q [...] new cfe9c388c698 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/q [...] new b09d83cede85 144: onsuccess: #2179: 1: Success after binutils/gcc/linux [...] new c953b78dab47 145: onsuccess: #2180: 1: Success after binutils/gcc/linux [...] new 5405b22889ac 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb [...] new 2f40df239495 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: [...] new 8db42cab4d16 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 6 [...] new bf3d94196cc4 149: onsuccess: #2184: 1: Success after binutils/gcc/linux [...] new aabe9140278f 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 2b07b0fc96cb 151: onsuccess: #2186: 1: Success after gcc: 2 commits new fd6c321c77dc 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 2 [...] new 7db90f4cb450 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: [...] new 5963f3aba745 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: [...] new 2ea0c489346a 155: onsuccess: #2190: 1: Success after binutils/gcc/linux [...] new 2e2e7886411b 156: onsuccess: #2191: 1: Success after binutils/gcc/linux [...] new 2879c5e7cb12 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: [...] new f2dfed83ff14 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc [...] new b6ce37700dc7 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 1 [...] new 289362a38316 160: onsuccess: #2195: 1: Success after binutils/gcc/linux [...] new 3f89ab5b86bd 161: onsuccess: #2196: 1: Success after binutils/gcc/linux [...] new 16d9bf6cba12 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc [...] new ce603e4c8765 163: onsuccess: #2198: 1: Success after binutils/gcc/linux [...] new d0ce293d38d8 164: onsuccess: #2199: 1: Success after binutils/gcc/linux [...] new ebee463770f0 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 5a290c8dc658 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 [...] new ea422a7adade 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qe [...] new 14ca4803fa38 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc [...] new 257903847062 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc [...] new 2a8d76573c22 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc [...] new 27021d1aa6c1 171: onsuccess: #2206: 1: Success after binutils/gcc/linux [...] new 85139fc4302c 172: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] new 1b85fb8ad0c9 173: onsuccess: #2208: 1: Success after gcc: 10 commits new f770d21bc147 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: [...] new c03612513120 175: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] new f005209ae3b0 176: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] new 3302c90e65bc 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new 59d21f8dfec1 178: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] new a8de37a5fd35 179: onsuccess: #2230: 1: Success after binutils/gcc/linux [...] new 958f5d88cefc 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc [...] new ee6f73ef183c 181: onsuccess: #2239: 1: Success after binutils/gcc/linux [...] new 7bba3fce1c34 182: onsuccess: #2247: 1: Success after binutils/gcc/linux [...] new 17fad929a503 183: onsuccess: #2270: 1: Success after binutils/gcc/linux [...] new 2f4ec67a9fa2 184: onsuccess: #2288: 1: Success after binutils/gcc/linux [...] new fdde9e04bf85 185: onsuccess: #2290: 1: Success after binutils/gcc/linux [...] new 03dd7806d76f 186: onsuccess: #2291: 1: Success after binutils/gcc/linux [...] new a3168ce8465a 187: onsuccess: #2294: 1: Success after binutils/gcc/linux [...] new 0521d35d5069 188: onsuccess: #2295: 1: Success after binutils/gcc/linux [...] new 2062f18834f2 189: onsuccess: #2299: 1: Success after binutils/gcc/linux [...] new 6104db74bc5f 190: onsuccess: #2330: 1: Success after binutils/gcc/linux [...] new 3c1d5c3bc6d0 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new ba43099bc98c 192: onsuccess: #2338: 1: Success after binutils/gcc/linux [...] new fcf5ec9a4aeb 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc [...] new cafc7d48ca60 194: onsuccess: #2340: 1: Success after binutils/gcc/linux [...] new 6f47834b8bd1 195: onsuccess: #2341: 1: Success after binutils/gcc/linux [...] new 829177dd6087 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: [...] new f2fe0d30bde8 197: onsuccess: #2348: 1: Success after linux: 190 commits new f23d4ba4f82b 198: onsuccess: #2360: 1: Success after binutils/gcc/linux [...] new 934fd77141a0 199: onsuccess: #2363: 1: Success after binutils/gcc/linux [...] new f00a21524806 200: onsuccess: #2427: 1: Success after binutils: 274 commits new dc0edfae3579 201: onsuccess: #2430: 1: Success after glibc: 26 commits new 3c5381f0367c 202: onsuccess: #2431: 1: Success after linux: 944 commits new c631abd9f86b 203: onsuccess: #2433: 1: Success after binutils: 27 commits new b9a7b8ab6252 204: onsuccess: #2435: 1: Success after linux: 3 commits new 5f3297d36cec 205: onsuccess: #2444: 1: Success after binutils/gcc/linux [...] new 569ad41463a2 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc [...] new f41866fb3327 207: onsuccess: #2446: 1: Success after binutils/gcc/linux [...] new 737fcc1181d8 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: [...] new 30531642623a 209: onsuccess: #2448: 1: Success after binutils/gcc/linux [...] new 5ea8b58bb52c 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: [...] new b3e22d82d30a 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new 81abb4537667 212: onsuccess: #2451: 1: Success after binutils/gcc/linux [...] new 4f3ae91876b1 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: [...] new 69120a2ec96a 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc [...] new e15eeba66a7c 215: onsuccess: #2455: 1: Success after binutils: 3 commits new cf3766af79e8 216: onsuccess: #2457: 1: Success after linux: 1736 commits new c81665d30248 217: onsuccess: #2459: 1: Success after binutils: 3 commits new 266ce9f830cc 218: onsuccess: #2461: 1: Success after linux: 916 commits new de8ebf0a0d83 219: onsuccess: #2463: 1: Success after binutils: 3 commits new a3cfddd23ca3 220: onsuccess: #2465: 1: Success after linux: 572 commits new be83f2eaaf43 221: onsuccess: #2467: 1: Success after binutils: 3 commits new 93b18bcb1ca8 222: onsuccess: #2469: 1: Success after binutils/gcc/linux [...] new 3050355cb7e1 223: onsuccess: #2470: 1: Success after binutils/gcc/linux [...] new 4651c7f1dcc5 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: [...] new e1efe2688fb4 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new cad0ea77f632 226: onsuccess: #2473: 1: Success after binutils/gcc/linux [...] new c837e2c008d9 227: onsuccess: #2474: 1: Success after gcc: 2 commits new f7c9262fcfb7 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/q [...] new 753ac5dbf638 229: onsuccess: #2476: 1: Success after binutils/gcc/linux [...] new 378aeebcde46 230: onsuccess: #2477: 1: Success after binutils/gcc/linux [...] new 0ff1eed6060c 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/q [...] new 4b1a3ea25b0b 232: onsuccess: #2480: 1: Success after binutils/gcc/linux [...] new faaea6b3255f 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/q [...] new fb276bae7aa9 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 07fe5955de66 235: onsuccess: #2483: 1: Success after linux: 108 commits new 9fe2cd9c10aa 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 886a3a6ee973 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/q [...] new 97dc011824ab 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: [...] new f604d3dc7961 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: [...] new 9d92c612d529 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 453f798fb50b 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc [...] new 3e40a282a0bb 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: [...] new ad90c0bc8685 243: onsuccess: #2491: 1: Success after binutils/gcc/linux [...] new edb3d94b7660 244: onsuccess: #2492: 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 (ae0ee150ac4e) \ 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 1756 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 32260 -> 32740 bytes 04-build_abe-stage1/console.log.xz | Bin 73628 -> 74480 bytes 06-build_abe-linux/console.log.xz | Bin 9296 -> 9272 bytes 07-build_abe-glibc/console.log.xz | Bin 243416 -> 245696 bytes 08-build_abe-stage2/console.log.xz | Bin 205760 -> 206964 bytes 09-build_abe-gdb/console.log.xz | Bin 39540 -> 40316 bytes 10-build_abe-qemu/console.log.xz | Bin 31200 -> 31324 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3912 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2896 -> 2836 bytes 13-check_regression/console.log.xz | Bin 99184 -> 17944 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 281 +- 13-check_regression/mail-body.txt | 244 +- 13-check_regression/results.compare | 1608 +-- 13-check_regression/results.compare2 | 21588 ++---------------------------- 13-check_regression/results.regressions | 90 +- 14-update_baseline/console.log | 68 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 246 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 90 +- sumfiles/g++.log.xz | Bin 3411600 -> 3439500 bytes sumfiles/g++.sum | 118 +- sumfiles/gcc.log.xz | Bin 3033924 -> 3024020 bytes sumfiles/gcc.sum | 6617 +++++---- sumfiles/gfortran.log.xz | Bin 1038948 -> 1034064 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214668 -> 214592 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2696 -> 2700 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 427884 -> 435368 bytes sumfiles/libstdc++.sum | 74 +- 44 files changed, 5724 insertions(+), 25373 deletions(-)