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 4317ec921f 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards b70f317226 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 67f222f496 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards e304e4c615 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards fb4143cedb 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 3c69ea42e7 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards ca7f9df227 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards bc5baa35e1 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards e443eb1a06 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards 66ec59538d 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 928bc15dae 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards d7515c5c8a 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 45a1fa7e72 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 861e2e0ac9 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards 0286ff95df 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 6fc7a7e2f5 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards fab7327bd4 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards 0dab2568a6 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 51f7410afb 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 48c7411565 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards d0f18dbef8 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards d9f2101989 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 6ce53d114c 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards 419626c1b0 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards c293eaaac3 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards ccc8c4a9eb 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards 1604f78dfc 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards c0a6d704d2 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 61f144966a 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 785fa34a7f 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards bbf5553a92 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards 3a7f2c160b 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards df67fe0984 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 2ffcd4fc05 235: onsuccess: #2483: 1: Success after linux: 108 commits discards e597447aa1 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards 4ff8d72e21 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards 4825aa17d8 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards 8f4da0c39f 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards 3e816f2977 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards 08671433d1 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards ec1796323f 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards a766295005 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards d1ad4ac1c9 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards b2e5e31934 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards 91d82ad878 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] discards e7df1ec971 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] discards c8f9dab539 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] discards 0f86336ddd 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards 7a9fa58a59 220: onsuccess: #2465: 1: Success after linux: 572 commits discards a83c768998 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards cbdd96b9b9 218: onsuccess: #2461: 1: Success after linux: 916 commits discards bbdf2aef91 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards d03911f344 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards e843a86e15 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards 4572e60654 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] discards 49db4402af 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] discards 45f3435a07 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] discards f4a78a3f10 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards bd1ced2164 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits discards c163112d36 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] discards bdcfec3caf 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] discards 63f1d35031 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] discards 1a3951f53a 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] discards 5699cb3980 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] discards a35abb74c9 204: onsuccess: #2435: 1: Success after linux: 3 commits discards 5a33cc0dd5 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards 10e3aa4bb2 202: onsuccess: #2431: 1: Success after linux: 944 commits discards 7e25a5fc9e 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards 98d6eea361 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards 9914df04b2 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/g [...] discards 8f1a5af30f 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] discards 59a49dd986 197: onsuccess: #2348: 1: Success after linux: 190 commits discards 77b1a3d34d 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] discards 41f6bc4bf7 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] discards 4600b84423 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] discards 4cd82f6af7 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] discards 843e0ddd53 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] discards 355e4506fc 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards cabd4ae667 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] discards 438c330ece 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] discards 595b839aa0 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] discards e344ce6da5 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] discards 72249f2118 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] discards fb4dcf7907 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] discards cc57233d12 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] discards 5a0651e5f0 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] discards 1a528297e9 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] discards 5eca127b66 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] discards fae7751356 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] discards 8b81cf0075 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] discards 38b16fa4e7 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 94b56748f3 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards ceb940c4f2 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards d493fea974 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 59d17e7a4f 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] discards bab11f76e4 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards 585dd2c6e0 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards f894fe2abd 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] discards 07fa30e09e 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] discards 9aacaea62e 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards 75ec8e9980 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new 0716cbe775 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new 05e5523683 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new 527bce7075 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/g [...] new 727590be72 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/g [...] new 2a9cd3ef1a 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 7eda894484 173: onsuccess: #2208: 1: Success after gcc: 10 commits new ce28b16716 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 20 [...] new 184d80fb74 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new e83198e080 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new e65995fd81 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new f11c930197 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 6a5e50300a 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/g [...] new 81fcde585f 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] new 9fdc249480 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] new 2918c2e7ca 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] new 60d521b634 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] new 29ce4a8a6a 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] new a3061be8d6 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] new 232661ea08 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] new 20584fe781 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] new 22768a87a7 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] new 126865817b 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] new 0e0babde1f 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] new b34d16e2b0 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new 1e195c46e4 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] new ed935a7e03 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] new 67cb639f2f 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] new 4358f99038 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] new 101bac5ba7 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] new be8e550ae3 197: onsuccess: #2348: 1: Success after linux: 190 commits new 35be303ebc 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] new 400e1b599a 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/g [...] new 49fb2dc780 200: onsuccess: #2427: 1: Success after binutils: 274 commits new e0805e7be6 201: onsuccess: #2430: 1: Success after glibc: 26 commits new eb2e0c73fa 202: onsuccess: #2431: 1: Success after linux: 944 commits new 8003f0f19a 203: onsuccess: #2433: 1: Success after binutils: 27 commits new b8b127c883 204: onsuccess: #2435: 1: Success after linux: 3 commits new 3fb1f50cf1 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] new 39e46a0377 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] new f1ffc7005b 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] new 4aecf4d6fb 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] new a97fb4c94a 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] new e45591d911 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits new 342ae7e42b 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new f62ed6fb01 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] new 65dee626d1 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] new ba064db63e 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] new 81f5f53961 215: onsuccess: #2455: 1: Success after binutils: 3 commits new f2922b9916 216: onsuccess: #2457: 1: Success after linux: 1736 commits new 10c06ea905 217: onsuccess: #2459: 1: Success after binutils: 3 commits new cd11317d20 218: onsuccess: #2461: 1: Success after linux: 916 commits new 089a014a90 219: onsuccess: #2463: 1: Success after binutils: 3 commits new 9807c5ef8b 220: onsuccess: #2465: 1: Success after linux: 572 commits new 5a2b847dce 221: onsuccess: #2467: 1: Success after binutils: 3 commits new 93cc07030e 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] new 859c153c9f 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] new 971ad28e8b 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new b697ebb349 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new c23fc9f858 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new a0bd51dce1 227: onsuccess: #2474: 1: Success after gcc: 2 commits new d892aa7d52 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new ff7fcc39ca 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new 2951d45ac5 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new ca598ab425 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new d8103a03e8 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new 795b7d0501 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new 67563a0d9c 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new 1ea3349456 235: onsuccess: #2483: 1: Success after linux: 108 commits new 8039bf096c 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 69e9727443 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new afcd2147a9 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new 135de779ed 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 6da67d3bd5 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 9bd21d4450 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 05c1b80c32 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new c8167f328f 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new 4a734f213a 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new 2a5c5f0470 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 580ce59d68 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new bbbba05a4a 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new b20c42cac7 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 1f1b83e20d 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new cd660e6c18 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new f5011bf064 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 18df2c0782 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new d04a7ac694 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new e08aafc445 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 7224eb8e13 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new a96bcf8251 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 1db6d3b651 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new a6ad34daba 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new c317c3b416 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 1907ffe5d4 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new b14f9a3fe4 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 74f334b2fe 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 645c525333 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 332b6f8780 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 139658eaef 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new ea9d89cbaa 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 900bd145ba 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 0ec9ae2ecd 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new e0fd557f44 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 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 (4317ec921f) \ 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 1804 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 32188 -> 31968 bytes 04-build_abe-stage1/console.log.xz | Bin 73700 -> 73376 bytes 06-build_abe-linux/console.log.xz | Bin 8368 -> 8400 bytes 07-build_abe-glibc/console.log.xz | Bin 245600 -> 245036 bytes 08-build_abe-stage2/console.log.xz | Bin 205112 -> 204880 bytes 09-build_abe-gdb/console.log.xz | Bin 39532 -> 39296 bytes 10-build_abe-qemu/console.log.xz | Bin 31700 -> 31720 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3908 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2908 -> 2632 bytes 13-check_regression/console.log.xz | Bin 7364 -> 5476 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 62 +- 13-check_regression/results.compare | 25 +- 13-check_regression/results.compare2 | 420 +--- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 36 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/mail-body.txt | 62 +- manifest.sh | 32 +- results | 26 - sumfiles/g++.log.xz | Bin 3411260 -> 3410936 bytes sumfiles/g++.sum | 18 +- sumfiles/gcc.log.xz | Bin 3038824 -> 3039024 bytes sumfiles/gcc.sum | 4098 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1045952 -> 1037708 bytes sumfiles/gfortran.sum | 8 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214580 -> 214772 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2700 -> 2696 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 433808 -> 431420 bytes sumfiles/libstdc++.sum | 10 +- 40 files changed, 2162 insertions(+), 2682 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions