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 e0fd557f44 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 0ec9ae2ecd 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 900bd145ba 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards ea9d89cbaa 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 139658eaef 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 332b6f8780 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 645c525333 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 74f334b2fe 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards b14f9a3fe4 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 1907ffe5d4 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards c317c3b416 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards a6ad34daba 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 1db6d3b651 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards a96bcf8251 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 7224eb8e13 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards e08aafc445 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards d04a7ac694 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 18df2c0782 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards f5011bf064 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards cd660e6c18 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 1f1b83e20d 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards b20c42cac7 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards bbbba05a4a 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 580ce59d68 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards 2a5c5f0470 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards 4a734f213a 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards c8167f328f 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards 05c1b80c32 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards 9bd21d4450 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 6da67d3bd5 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 135de779ed 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards afcd2147a9 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards 69e9727443 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards 8039bf096c 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 1ea3349456 235: onsuccess: #2483: 1: Success after linux: 108 commits discards 67563a0d9c 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards 795b7d0501 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards d8103a03e8 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards ca598ab425 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards 2951d45ac5 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards ff7fcc39ca 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards d892aa7d52 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards a0bd51dce1 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards c23fc9f858 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards b697ebb349 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards 971ad28e8b 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] discards 859c153c9f 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] discards 93cc07030e 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] discards 5a2b847dce 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards 9807c5ef8b 220: onsuccess: #2465: 1: Success after linux: 572 commits discards 089a014a90 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards cd11317d20 218: onsuccess: #2461: 1: Success after linux: 916 commits discards 10c06ea905 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards f2922b9916 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards 81f5f53961 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards ba064db63e 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] discards 65dee626d1 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] discards f62ed6fb01 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] discards 342ae7e42b 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards e45591d911 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits discards a97fb4c94a 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] discards 4aecf4d6fb 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] discards f1ffc7005b 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] discards 39e46a0377 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] discards 3fb1f50cf1 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] discards b8b127c883 204: onsuccess: #2435: 1: Success after linux: 3 commits discards 8003f0f19a 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards eb2e0c73fa 202: onsuccess: #2431: 1: Success after linux: 944 commits discards e0805e7be6 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards 49fb2dc780 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards 400e1b599a 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/g [...] discards 35be303ebc 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] discards be8e550ae3 197: onsuccess: #2348: 1: Success after linux: 190 commits discards 101bac5ba7 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] discards 4358f99038 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] discards 67cb639f2f 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] discards ed935a7e03 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] discards 1e195c46e4 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] discards b34d16e2b0 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards 0e0babde1f 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] discards 126865817b 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] discards 22768a87a7 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] discards 20584fe781 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] discards 232661ea08 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] discards a3061be8d6 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] discards 29ce4a8a6a 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] discards 60d521b634 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] discards 2918c2e7ca 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] discards 9fdc249480 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] discards 81fcde585f 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] discards 6a5e50300a 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] discards f11c930197 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards e65995fd81 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards e83198e080 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 184d80fb74 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards ce28b16716 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] discards 7eda894484 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 2a9cd3ef1a 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 727590be72 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards 527bce7075 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards 05e5523683 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new aebd580221 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new 8321a5f21a 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new e39401301e 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new 180be4ab40 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 62ecbf7581 173: onsuccess: #2208: 1: Success after gcc: 10 commits new 46b5026ffe 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new 98fcd61141 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new d8a3d44cd0 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new d5515d9f1e 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new efad91306c 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 3c02ad570e 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] new ff3933cb66 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] new 0436910588 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] new ed93452233 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] new 83d6970e9f 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] new e540acf041 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] new 925e3fa447 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] new 2bd2827385 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] new a5f701290c 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] new c6e86cd87b 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] new f5ab901ac6 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] new cecc89360f 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] new 650b0abc50 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new bf591ad0d4 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] new 6063523251 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] new d28c3a2ce5 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] new ab9a16da3d 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] new ac2db18905 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] new fc3eb4e9db 197: onsuccess: #2348: 1: Success after linux: 190 commits new b6b239adbd 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] new c89d15678a 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/g [...] new fc15d16a64 200: onsuccess: #2427: 1: Success after binutils: 274 commits new 7b9295d987 201: onsuccess: #2430: 1: Success after glibc: 26 commits new d41224c4dd 202: onsuccess: #2431: 1: Success after linux: 944 commits new af88437bb5 203: onsuccess: #2433: 1: Success after binutils: 27 commits new 7a709c7d1e 204: onsuccess: #2435: 1: Success after linux: 3 commits new f75b9f6f3e 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] new cf8314dd0f 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] new 067384e596 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] new 801fa34b6d 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] new de7305de15 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] new a5a0bdbf40 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits new cc1ccbfb7c 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new 390a82b2ad 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] new e428d4c89e 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] new f7d1c90443 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] new 7a309b0635 215: onsuccess: #2455: 1: Success after binutils: 3 commits new 140c7f805d 216: onsuccess: #2457: 1: Success after linux: 1736 commits new bdafef7868 217: onsuccess: #2459: 1: Success after binutils: 3 commits new f736eb381c 218: onsuccess: #2461: 1: Success after linux: 916 commits new 2445bce6de 219: onsuccess: #2463: 1: Success after binutils: 3 commits new 16a64f0024 220: onsuccess: #2465: 1: Success after linux: 572 commits new 7a1d57116e 221: onsuccess: #2467: 1: Success after binutils: 3 commits new 76facc860f 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] new 1619250c45 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] new 1adbd9083e 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new 68a97f66b4 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new bb8942384f 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new 340ad792c3 227: onsuccess: #2474: 1: Success after gcc: 2 commits new e6f98f3f56 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new 32a93cffb9 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new 61abda7f20 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new 03b16af32f 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new f21080e232 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new 81ec43de99 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new 66cc070954 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 53d291795d 235: onsuccess: #2483: 1: Success after linux: 108 commits new 22b938560c 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 4a424c023d 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new 03a78b13e0 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new c1faedc056 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new bd219ba7ef 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 39534a7946 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 9627a1f93f 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new 1be321fc10 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new 66792af038 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new faf50ed19e 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 89b95f23ea 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new ebcb7e1ebb 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new dacc5c1042 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new b7258c4d14 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new c17279e02d 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 4281e7122e 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new a876e68ce1 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new e60c856859 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 6245d7fc44 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 40672864a9 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 2bd0d0c530 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new ea887ea314 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new 9a51b1804c 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new 00dba2f876 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new bd5d8ffb64 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new b0cc611c23 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 9622db1fc3 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 08e029e2fe 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 7f32d80b95 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new fb6fe9b60c 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 4f89c285d0 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new dcbba98852 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 2639136a54 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 32f774b11b 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 56c4e64037 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...]
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 (e0fd557f44) \ 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 1744 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 31968 -> 32536 bytes 04-build_abe-stage1/console.log.xz | Bin 73376 -> 74740 bytes 06-build_abe-linux/console.log.xz | Bin 8400 -> 8340 bytes 07-build_abe-glibc/console.log.xz | Bin 245036 -> 246704 bytes 08-build_abe-stage2/console.log.xz | Bin 204880 -> 207172 bytes 09-build_abe-gdb/console.log.xz | Bin 39296 -> 40060 bytes 10-build_abe-qemu/console.log.xz | Bin 31720 -> 31700 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3912 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2632 -> 3696 bytes 13-check_regression/console.log.xz | Bin 5476 -> 6208 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 70 +- 13-check_regression/results.compare | 37 +- 13-check_regression/results.compare2 | 39 +- .../{mail-body.txt => results.regressions} | 83 +- 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 | 72 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 44 + sumfiles/g++.log.xz | Bin 3410936 -> 3409180 bytes sumfiles/g++.sum | 8 +- sumfiles/gcc.log.xz | Bin 3039024 -> 3036304 bytes sumfiles/gcc.sum | 4668 ++++++++++---------- sumfiles/gfortran.log.xz | Bin 1037708 -> 1040036 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214772 -> 214916 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2696 -> 2696 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 431420 -> 430304 bytes sumfiles/libstdc++.sum | 15 +- 42 files changed, 2621 insertions(+), 2540 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum copy 13-check_regression/{mail-body.txt => results.regressions} (63%)