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_gdb/master-arm in repository toolchain/ci/base-artifacts.

discards 810475275fe 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 2 [...] discards f21f104f1e6 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gc [...] discards e5320c6721c 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 33945303afe 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards cea7e033f37 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards 2a044806e75 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits discards 245f58666bd 230: onsuccess: #78: 1: Success after gdb: 2 commits discards 1971e31e2ac 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g [...] discards 6d121a1bf40 228: force: #74: 1: Success after gdb: 53 commits discards cb52d981d1e 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] discards 02e829718f4 226: force: #70: 1: Success after baseline build: no new commits discards f26d9e1f492 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] discards 8651564a164 224: force: #65: 1: Success after gdb: 50 commits discards 1f26487ef65 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] discards 7f9ef1c722a 222: force: #60: 1: Success after gdb: 16 commits discards 637bb9569b2 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] discards 155926634a2 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] discards c4f239a450b 219: force: #50: 1: Failure after linux: 2520 commits discards 87984b8a47b 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] discards 1f8683f8ac8 217: force: #45: 1: Success after linux: 1 commits discards 1228d15408f 216: force: #43: : Failure after baseline build: no new commits discards 20f4643d442 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 7b5ee1ffd20 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 37e4523d95d 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 25d8b7b03f8 212: force: #27: : Failure after baseline build: no new commits discards eecd5f41b4a 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 8e5603170dc 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards fa436d10387 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards d691106a575 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 52463747929 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 72ec946c69f 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 8f2a16c5dab 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 54b545dfea5 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards bcdeb872b19 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 615a8dbf72a 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards a8bcab171e8 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 7352d333318 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards b1f4d7fc431 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 0bbb89146d5 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 98abe9dfaa3 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 5984e356b68 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 53a712768a7 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 3c7617816a6 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 2d5f4b4efe4 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 1f49326814a 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 53e2495ccf1 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards b785ad2a8dc 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 6969bae15c2 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards 8059f5a6f51 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards 0a47210cd32 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 1d8fe2bd735 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards 1ed27951ee2 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards e473edc1457 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards ac1a7640337 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards fca67ba0190 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 5a5c94d5100 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards db374538e03 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards 09fc82554ad 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards 7a809030ba2 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards edd566a23fc 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 40ab0d4fe9b 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 70dc454a3d4 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 593864d89c6 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards fd7dc6d64ed 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 2ab680078b8 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 95e8d8d255f 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards d38d6a65d51 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards 05474d3d340 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 93d501ea451 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 659ddf8d2b6 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 98dddcc06fb 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 1a1a829b4df 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 552c8235942 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards 66ab3fa02b4 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 81734ffdfb7 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 94b3879e5c6 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards eda2ff0c315 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 9d773150ae9 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards c5e876a282b 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards bddd9111274 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards e927f799a1f 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 131f7f022de 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 3145dc561a1 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards b6c81383ba8 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards bd40ef53d3d 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 966e3fc2eef 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 94fee7537e1 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 719d1c195e3 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 11351a58ab7 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 72b3afc5bf5 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards dac8cc8c9a0 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards ec70921bfd3 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 53bc519ffda 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards d264c4d2d8d 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 371ecb3fee5 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 2433530a120 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 46a6a63215e 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 761fee34cc9 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 5741681b4f2 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 80b8e1dda20 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards 0c1aad49c19 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 8a825b4e0a3 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new f39864b813a 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 591afbf896a 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new ab4e4356ae6 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new bb5c995212f 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new b9c9103045d 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new a5c245db21d 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 74b3c2bac81 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 1a583cf47fe 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new 75d4bab1fc4 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new de699975b36 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 2b7217c3ec2 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new 35f04532903 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new ad75aac1ca6 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 521b5311ab8 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 5a4dbd33a57 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new ef2569a1a99 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new 846e839045f 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new db30820bf2d 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new b3c6942f56e 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 74b621c75ff 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 5610af7d92e 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new f0a5d4186cd 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 6810254810a 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new a94222542ef 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 4229fb78928 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new e107c32548f 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 9a9ec3400ec 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new cacffe9fe10 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new 38a2db45b85 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new ae6de604708 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new bc8a83948cd 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 91cffeda350 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new c3797b557cd 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 96c6d578a1a 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new 0e308b0cc58 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new ff5862d9fbc 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new f3c1984c771 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new 6760c192444 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 7a6e7f4c080 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new cfb39a1f446 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 89a7f80e0da 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 887a60295d4 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new a7c6a1027b0 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new af1ab342ce0 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new 82cc0148248 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new ca25cfc5efc 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 2cd9fc691c5 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 34968f50d23 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new 351bb3d2eae 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new d4bcbe8c01e 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new 4a2fb3a7137 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new 47e23eb95c8 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new b8a9dfd6188 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new db33d6882cc 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new aa0b8d95dec 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 2c7592fbe84 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 3bbd1960990 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 050ddd30a34 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new eba02527206 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new e5047ac5bb8 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 81e974c6d09 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 57c405493e6 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 4b16b16684e 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new b99baa9051d 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new a3c87d9a02f 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new e7c276aaa97 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 8daa112b3a7 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 3bd698e5ad7 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 5c7892262a3 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 69de0fedd6f 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 68f6b70b776 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new d55b86afe81 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new a87b969bed3 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new edf408e83c3 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 9f4bef9f716 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new b1839445489 212: force: #27: : Failure after baseline build: no new commits new 506a919e7f7 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new d8dfbad183c 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] new b9b80b1497c 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] new 0c3ee99dd17 216: force: #43: : Failure after baseline build: no new commits new 4134be77242 217: force: #45: 1: Success after linux: 1 commits new 9f555ebc43a 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] new b058c9d161a 219: force: #50: 1: Failure after linux: 2520 commits new 9487913cdbb 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] new 3d3c3354b4e 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] new fe9ab198947 222: force: #60: 1: Success after gdb: 16 commits new 4589c09f106 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] new e8699aec85c 224: force: #65: 1: Success after gdb: 50 commits new 5a078a95184 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] new c38a0ce5134 226: force: #70: 1: Success after baseline build: no new commits new 88b0d071226 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] new 4a7b6149def 228: force: #74: 1: Success after gdb: 53 commits new 16cacda252a 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g [...] new df96406026a 230: onsuccess: #78: 1: Success after gdb: 2 commits new 7528cd8e8f7 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits new a105e3ac71c 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new d436c9bb0c3 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new 9b2dee0ec15 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new e81971938e3 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gc [...] new bb7d1262e6d 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 2 [...] new c405221c08c 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 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 (810475275fe) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/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 2256 -> 2220 bytes 02-prepare_abe/console.log.xz | Bin 2492 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 48836 -> 48924 bytes 04-build_abe-gcc/console.log.xz | Bin 236328 -> 236144 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8664 -> 8660 bytes 07-build_abe-glibc/console.log.xz | Bin 232480 -> 232040 bytes 08-build_abe-gdb/console.log.xz | Bin 46636 -> 46892 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3792 -> 3772 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4676 -> 4692 bytes 11-check_regression/console.log.xz | Bin 4360 -> 3932 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 6 + 11-check_regression/results.compare | 27 +- 11-check_regression/results.compare2 | 130 +- 11-check_regression/results.regressions | 28 + 11-check_regression/trigger-bisect | 3 + 12-update_baseline/console.log | 68 +- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- mail/changes-list-long.txt | 14 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 28 +- mail/short-diag.txt | 2 +- manifest.sh | 20 +- results | 28 + sumfiles/gdb.log.0.xz | Bin 2940352 -> 2884104 bytes sumfiles/gdb.log.1.xz | Bin 143556 -> 143256 bytes sumfiles/gdb.log.10.xz | Bin 10388 -> 10236 bytes sumfiles/gdb.log.11.xz | Bin 10252 -> 10256 bytes sumfiles/gdb.log.12.xz | Bin 10320 -> 10128 bytes sumfiles/gdb.log.13.xz | Bin 10092 -> 10320 bytes sumfiles/gdb.log.14.xz | Bin 10240 -> 0 bytes sumfiles/gdb.log.15.xz | Bin 10272 -> 0 bytes sumfiles/gdb.log.2.xz | Bin 17440 -> 15512 bytes sumfiles/gdb.log.3.xz | Bin 15556 -> 10308 bytes sumfiles/gdb.log.4.xz | Bin 15244 -> 10168 bytes sumfiles/gdb.log.5.xz | Bin 15264 -> 10028 bytes sumfiles/gdb.log.6.xz | Bin 10364 -> 10356 bytes sumfiles/gdb.log.7.xz | Bin 10292 -> 10344 bytes sumfiles/gdb.log.8.xz | Bin 10284 -> 10160 bytes sumfiles/gdb.log.9.xz | Bin 10084 -> 10308 bytes sumfiles/gdb.sum | 1717 ++++++++++++++---------- sumfiles/gdb.sum.0 | 1727 ++++++++++++++---------- sumfiles/gdb.sum.1 | 813 ++++++------ sumfiles/gdb.sum.10 | 100 +- sumfiles/gdb.sum.11 | 62 +- sumfiles/gdb.sum.12 | 29 +- sumfiles/gdb.sum.13 | 31 +- sumfiles/gdb.sum.14 | 2155 ------------------------------ sumfiles/gdb.sum.15 | 2159 ------------------------------- sumfiles/gdb.sum.2 | 535 +++----- sumfiles/gdb.sum.3 | 309 +---- sumfiles/gdb.sum.4 | 310 +---- sumfiles/gdb.sum.5 | 313 +---- sumfiles/gdb.sum.6 | 44 +- sumfiles/gdb.sum.7 | 26 +- sumfiles/gdb.sum.8 | 48 +- sumfiles/gdb.sum.9 | 23 +- 59 files changed, 2961 insertions(+), 7801 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 create mode 100644 11-check_regression/trigger-bisect delete mode 100644 sumfiles/gdb.log.14.xz delete mode 100644 sumfiles/gdb.log.15.xz delete mode 100644 sumfiles/gdb.sum.14 delete mode 100644 sumfiles/gdb.sum.15