This is an automated email from the git hooks/post-receive script.

tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts.

discards dce316f9f5e 225: onsuccess: #32: 1: [TCWG CI] Success after binutils/gc [...] discards e8fec8b35a9 224: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 96426348837 223: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 14c796b47e6 222: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 4debb1ef9d9 221: onsuccess: #27: 1: Success after binutils/gcc/linux/gl [...] discards c6eb7c01183 220: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] discards e73b649bba7 219: onsuccess: #24: 1: Success after binutils/gcc/linux/gd [...] discards 029d73a2bc9 218: onsuccess: #23: 1: Success after binutils/gcc/linux/gd [...] discards c8966b7fb22 217: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] discards eb0d4dbffc9 216: onsuccess: #21: 1: Success after binutils/gcc/linux/gd [...] discards 3e184e8e078 215: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards ecb8b23e551 214: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 884a9be5b7e 213: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 31563dc9119 212: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards ea7bbdaa3f8 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards cfe72cf7eed 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 7fcaab822af 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 7a5311be258 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 6466de0dfbe 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 6d2b9e37745 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 53397625fde 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 92e1dcfe6a2 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 9fd005db17d 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 894ceb7e9d8 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 84eef4ca109 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 923205580e8 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards ef37f862578 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 973aa82ab99 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 46d03d4a006 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards e71556d0407 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards aeee8c7e97b 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 1ae6d7b4169 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 79a27870a48 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards f12178fd0af 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 6b1d4d03610 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 5269b83d880 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 9ac5b3e7a6a 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] discards cefb4aadb25 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards e7925610af9 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 2422d4fe7a6 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] discards c3216765e5a 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] discards 4b96ac102e5 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] discards 397baab793d 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] discards d024ce31dc2 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] discards a1e385494f4 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] discards c50edf78afb 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards fa1f7d9aaf1 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] discards b71ccf2f241 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards aeef2620ce2 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards 2e1e34dd82e 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards 1bdeb79e80a 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards efc55ef1e6e 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] discards 931df42565c 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] discards a7a816e6226 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] discards af584d8f25e 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 5f7721c719c 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] discards cf724cabe38 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 82e5b98ecf0 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards 1858a2356d1 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 0e049469c54 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 58aa373a348 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards d072fc4c5dd 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] discards 248710f7cdd 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 387790474bd 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards 0ce164546af 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards af0ab97db4a 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards c6194f997de 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 9fa7d3c4d4a 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] discards 51f1d5b00b5 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] discards e0cf5681313 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] discards fc5fd809adf 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] discards bf0af6f2ba6 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] discards fd3a9f4b9e0 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards b784a974082 152: onsuccess: #903: 1: Success after linux: 22 commits discards 21486a1e1d1 151: onsuccess: #902: 1: Success after glibc: 8 commits discards 7fca444cca8 150: onsuccess: #900: 1: Success after gcc: 11 commits discards 864c30ecdf6 149: onsuccess: #899: 1: Success after binutils: 15 commits discards e52adf33f4a 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] discards 656600ca0fb 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] discards 65efb041171 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] discards 99d1acb23eb 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards e84a61bb48e 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] discards 5e14b170e8f 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] discards 05b714f4b6d 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 92b091d98d6 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] discards 799e6fe15f7 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards d39fa59e5f3 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards 8feecf0b40b 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards b6e3beca889 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards cdca34746e1 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 05dba754f44 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 2aac19d2ba6 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] discards 3535284166e 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards 308ed031746 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards 1b44270d685 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] discards fe820d0754f 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] discards 0c3ccca2556 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 46203f548ed 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 2c4a92ff87e 127: onsuccess: #874: 1: Success after linux: 219 commits discards 89e034c7943 126: onsuccess: #873: 1: Success after glibc: 2 commits discards c3210a279c6 125: onsuccess: #871: 1: Success after binutils: 26 commits new 1e6d41c7215 125: onsuccess: #871: 1: Success after binutils: 26 commits new 9de0f837093 126: onsuccess: #873: 1: Success after glibc: 2 commits new 233a444b379 127: onsuccess: #874: 1: Success after linux: 219 commits new 43f273d7f60 128: onsuccess: #876: 1: Success after binutils: 12 commits new 0ab8ac42646 129: onsuccess: #878: 1: Success after linux: 3008 commits new 31ddd66b15e 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] new 5c009e8b412 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] new a0edbf9a5f5 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new e33b00897f7 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new 16c6602d988 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] new 8ee02a7b5b6 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new 3ad6b2e386e 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 9cc5b2f028d 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new 26d255dff20 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 4bb0c58a172 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new fabc135e68f 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new 6cd1faa849f 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] new c050a24de5b 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new 9531020f9a2 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] new b01ecce1f6b 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] new f3d03a4d263 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new be92880f3f4 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] new db16f997a78 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] new 14a821f9bf6 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] new 8280a04ea24 149: onsuccess: #899: 1: Success after binutils: 15 commits new 0cc7f469f99 150: onsuccess: #900: 1: Success after gcc: 11 commits new 5f069360230 151: onsuccess: #902: 1: Success after glibc: 8 commits new 28eae350249 152: onsuccess: #903: 1: Success after linux: 22 commits new 1f6392fc9d0 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new a6e2e54a705 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] new e7cfd2481d3 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] new 3f4026ff421 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] new 08db01a1644 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] new 926fb34a75d 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] new 85984009647 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 0398cff6e43 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 8ad09332145 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 7dd832b1086 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 073d0e85234 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new 02b5fdfae4d 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] new a862e4cdd1c 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 01177190359 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new d8afd0af51b 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 08f105abc08 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new c94161084f7 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 0eeadb816db 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] new 6c6552c9412 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 3632d35e3eb 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] new deedc36f314 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] new 7c588dbb5d1 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] new ec895955150 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new 7dfe7f5ae06 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new fd421acd20a 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 2ea476f8f1a 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new abd62c015d9 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] new ffbf9295c11 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new a14af96d7b5 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] new e2d1b1ead8d 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] new d6b0307f8dc 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] new cb985e556b5 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] new 7176aa208fb 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] new 70eaa7e49c3 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] new 3e69e013182 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new b490976a884 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new e6c181652c2 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] new 08c6921bae4 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 9d263f1508b 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new fa27b0c3ad5 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 9e414133c36 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new e15c462abd0 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 107e95b32eb 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new d830020582c 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 884d332cef9 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 7fd0c6ce387 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 19ec35388a1 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new fc8ae56c0ef 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new c602db19c8d 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 1e0f3cead52 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 03639a2bd2f 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new f395820450c 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 93f53373e22 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 17b0d3c94da 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 968e0603aff 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 02bba7e46f6 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 76917bba54e 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new aa827947acd 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 751e6215a46 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 8c54687f6b4 212: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 0327efa9b06 213: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 753bb439591 214: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 822bec1075b 215: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new b0310f5002d 216: onsuccess: #21: 1: Success after binutils/gcc/linux/gd [...] new c99a89c57c9 217: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] new b188918f3ad 218: onsuccess: #23: 1: Success after binutils/gcc/linux/gd [...] new 9cd052ed6ac 219: onsuccess: #24: 1: Success after binutils/gcc/linux/gd [...] new af99120c489 220: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] new 5cfd9d46cfa 221: onsuccess: #27: 1: Success after binutils/gcc/linux/gl [...] new 91dd675f3d0 222: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 041a82b4346 223: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 24b72745cdd 224: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 2a23d474b8f 225: onsuccess: #32: 1: [TCWG CI] Success after binutils/gc [...] new 7f1fd85dc75 226: onsuccess: #33: 1: [TCWG CI] Success after binutils/gc [...]

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 (dce316f9f5e) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...]

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 2212 -> 2116 bytes 02-prepare_abe/console.log.xz | Bin 2496 -> 2516 bytes 03-build_abe-binutils/console.log.xz | Bin 34960 -> 35012 bytes 04-build_abe-gcc/console.log.xz | Bin 203020 -> 204280 bytes 06-build_abe-linux/console.log.xz | Bin 8764 -> 8456 bytes 07-build_abe-glibc/console.log.xz | Bin 240160 -> 241344 bytes 08-build_abe-gdb/console.log.xz | Bin 35036 -> 34828 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3796 -> 3852 bytes 10-build_abe-check_gcc/console.log.xz | Bin 10044 -> 10708 bytes 11-check_regression/console.log.xz | Bin 5796 -> 6808 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 20 + 11-check_regression/results.compare | 43 +- 11-check_regression/results.compare2 | 217 +- 11-check_regression/results.regressions | 40 + 12-update_baseline/console.log | 42 +- 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/changes-list-long.txt | 60 +- mail/changes-list-short.txt | 2 +- manifest.sh | 38 +- results | 40 + sumfiles/g++.log.sep.xz | Bin 66204 -> 101052 bytes sumfiles/g++.log.xz | Bin 3684992 -> 3730404 bytes sumfiles/g++.sum | 55 +- sumfiles/g++.sum.sep | 8703 ++++++++++--------------- sumfiles/gcc.log.sep.xz | Bin 85492 -> 81692 bytes sumfiles/gcc.log.xz | Bin 3223848 -> 3232220 bytes sumfiles/gcc.sum | 43 +- sumfiles/gcc.sum.sep | 10349 ++++++++++++++++++------------ sumfiles/gfortran.log.sep.xz | Bin 22644 -> 14420 bytes sumfiles/gfortran.log.xz | Bin 1087936 -> 1083256 bytes sumfiles/gfortran.sum | 5 +- sumfiles/gfortran.sum.sep | 1864 ++---- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 235392 -> 231704 bytes sumfiles/libgomp.sum | 31 +- sumfiles/libitm.log.xz | Bin 2688 -> 2684 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 30964 -> 7064 bytes sumfiles/libstdc++.log.xz | Bin 447600 -> 459784 bytes sumfiles/libstdc++.sum | 15 +- sumfiles/libstdc++.sum.sep | 197 +- 48 files changed, 11143 insertions(+), 10638 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions