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 4a5dde3a43 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards c46137787a 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 6f76821b34 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards c2254cf325 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 8b4ca474e2 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards c7d500b097 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 5c13eba16e 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards a3329f3e3f 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 01226dce74 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards 81b9463d72 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards 84c8c34272 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 97d1709e94 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards c9e229177f 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards fdd3057a3c 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards a37e28c1eb 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 3b5c5a1749 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 3f190588f4 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards 267b07219f 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards d6c30fbf20 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards f56359a6b4 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 6d97da88a2 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 5e36c64d7f 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 3e682dc7df 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 7db558b65c 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 11160eb66f 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 3e6b35e057 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 5a1290964b 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards f22305a94b 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 522d1723eb 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 132b4b6d00 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards d364d65037 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 9cc9c52787 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 21cc04c0e7 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 89b533d1c2 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 7c006a7cab 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards fdd1c4fbb8 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 62e282b5ed 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards a01a4634d0 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards 04b7445a12 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 710f454310 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 6aa10f38c3 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards f928add155 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 450e932a3b 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 3964570696 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 7c43cf3421 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 102f0bd871 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards bff6bc2ed7 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 0255a16353 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 44f3407687 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards bbbdb9aba9 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 4c7232d7b3 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards ec5578f0e2 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 246e110830 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 63763374b9 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards c5c3d00f3e 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 64775d03cd 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards d002648c25 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 737ffa8328 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 137138db35 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 0d760ca2a3 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards d38de3a4ac 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 2a683ebb6c 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards c7ac2c91d7 295: onsuccess: #2545: 1: Success after linux: 10 commits discards a0d6c98e3b 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 62111bcd3e 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 2546cdbb33 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 30a323f6ab 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards bd781b928a 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 984f6c54d6 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 4a76cbcef3 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 53a4058ea7 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 33aed78eb8 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards cdc83eb74a 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards da91177d19 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 945eb1ae38 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 4854ae4e11 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 2bf508d1dd 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards c0da93d7fb 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 5123d518f8 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 4759395528 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 29ccbf52f6 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 2f75d65327 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 1e33d0ef7c 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards ec303e7ed6 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards e28be57255 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards b811e23a2d 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 47d65447eb 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 8d49b43804 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards b86e06f60f 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 675d426a4c 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards e85364b44f 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 94752432bd 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards dd40d86b8b 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards a7c81f08bd 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 3f608a3f8e 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 40b4a8c740 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 23eb2f9155 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 2200f0b08c 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards 672bea5bcf 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 85bcb73405 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 3f34d23752 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new 81a837b9a3 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new aa8e3fa518 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new 9b12a9c1d7 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 5e029819db 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 1d40124d2c 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new e4c1a66f65 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 83f601949e 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 4a2e8a525d 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new a76a86ab2e 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 8d97b40b3d 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 70b3fd6235 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 1734903af1 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 85fad45fa9 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new cb9d7eec0f 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new f71bea3b8b 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new d9738da735 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 735b63fa46 273: onsuccess: #2521: 1: Success after gcc: 2 commits new cfd446f14a 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new f0f717936e 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 4cc17d6ed2 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new b739338dd0 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new d409b57496 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 6503154082 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 92dfaf3dbb 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new cb012e468e 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 0a60be4f0d 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 553f14f3df 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 014f6fab85 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new cc42d95ffa 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new f6428c946c 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new d3df1fa284 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new e9870c09ce 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 3eb220291d 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 07b7c5674b 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 40cf575d9a 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new eda3f8da8d 292: onsuccess: #2541: 1: Success after binutils: 13 commits new c932b9dc88 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 6f7f71dbf6 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 3501c33534 295: onsuccess: #2545: 1: Success after linux: 10 commits new 7de0fa2da4 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 2c0d0a6032 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 20dadbf1ec 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 04ccaf4854 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new ed3e64722f 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 6d5a814d41 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 608b11dfe2 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 2d192ab24a 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 5aedfe07e2 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new c5902b2693 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 3386f98fd8 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new c8e8436453 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new adfa81836a 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new b35a9e9050 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 824d7b3da2 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 2800a8f3c8 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 7b8204660e 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new be57a965d5 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 31d7320a82 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new bcfbb9a1ef 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new f73aca767f 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new fd47efb0ce 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new 571f9a12f7 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 4f7e5c40a4 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 5b244c7a47 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 5710918412 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 17956c8053 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 02e62cf3b5 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 9ae2ddb524 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new f026cda932 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 06cc24850e 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 681910f6f0 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new d9dc01bcaf 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 973df13baa 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 8e158952b4 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 5fb296b7d6 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new d48e33b784 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new a4c4f00d6d 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new db68738bdc 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new c2a6a93112 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 5deb365816 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new c56c4d2de8 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 3c02207bfd 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 0c4ef64826 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new beea0f0ca3 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new a5690234f4 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 3676d7a201 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 307bcdce39 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new f42673841f 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new fe683e5fca 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 4df9b455b0 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new d9b66d9c73 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 252b85fd90 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 63454d5d20 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 38bf71933e 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 20e7b3cd49 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 35038f6b32 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new e9e0af6567 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 4dac961ce1 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 612821792a 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 4d84f947b8 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 29b2af5d43 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new 755433d25f 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...]
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 (4a5dde3a43) \ 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 1768 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31564 -> 35836 bytes 04-build_abe-stage1/console.log.xz | Bin 73540 -> 73416 bytes 06-build_abe-linux/console.log.xz | Bin 8624 -> 8640 bytes 07-build_abe-glibc/console.log.xz | Bin 244944 -> 244452 bytes 08-build_abe-stage2/console.log.xz | Bin 205056 -> 204912 bytes 09-build_abe-gdb/console.log.xz | Bin 38692 -> 42948 bytes 10-build_abe-qemu/console.log.xz | Bin 31492 -> 32540 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3928 -> 3908 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2804 -> 3220 bytes 13-check_regression/console.log.xz | Bin 7676 -> 8084 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 19 + 13-check_regression/mail-body.txt | 90 +- 13-check_regression/results.compare | 61 +- 13-check_regression/results.compare2 | 282 +- 13-check_regression/results.regressions | 59 + 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 92 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 59 + sumfiles/g++.log.xz | Bin 3421156 -> 3401764 bytes sumfiles/g++.sum | 26 +- sumfiles/gcc.log.xz | Bin 3016644 -> 3017128 bytes sumfiles/gcc.sum | 4628 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1039252 -> 1032512 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214972 -> 215240 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2660 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 435912 -> 430692 bytes sumfiles/libstdc++.sum | 60 +- 44 files changed, 2876 insertions(+), 2640 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions