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 4f442b10fe1 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] discards d088f8cffb2 217: force: #45: 1: Success after linux: 1 commits discards 78b211587d0 216: force: #43: : Failure after baseline build: no new commits discards 942284f256c 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 27ce6313635 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 5996526e2c7 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards f8e1dc6ade8 212: force: #27: : Failure after baseline build: no new commits discards 44eb6f0c344 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 65e4da196bc 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 14650a91100 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards e699d1d3524 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 8c2da54faaf 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards fe36572d5da 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 9417e7729aa 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards c10071aaaf3 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 0950df0dbd7 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards af42457880a 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 212086d898d 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards f7d18ce4028 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 21e5ae73e45 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 4cd9e67d6bd 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 7077345b988 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 9d23a72c38a 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 6f747a4b221 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards d6fd0eb84e2 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards f659d2647e9 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards b6b68951c94 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 8aec99d28fb 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards d6fca64daca 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards fb9b14c3116 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards fca3cb986a8 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards a502e23b90c 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 971c14c6aff 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards b846d337a88 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards bf26db6d1d3 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 343536495d0 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 9e8639e8991 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards de0f6357dcf 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 6a785fa0de1 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards 5897a440eb8 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards 088a8ff2b4f 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 739e511c99f 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 2cc7edb7c14 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 2967953e14c 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 1c4ad314abc 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 5413b7fd8dc 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 018523d28a0 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards aeced05fc0a 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 3f419ba6e4e 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards a0a7a69afd0 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 85566a3e71f 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards b29d512f85e 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards f9331250c6b 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 07876f18cfc 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 499019f063b 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards fe87c0cd3aa 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 0ab0913ff57 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards e41e06728de 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 3a276f5a8fa 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards bdec28b4dfb 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 6b0ead88823 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards b5993977ab6 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 398850b30f3 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 5d658824bbb 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 1b32280c654 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards 5d477027aa9 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 6edc229b083 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards fa1e3845820 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 7bc92d8fb16 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 755ca60d52a 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 751b3ad64ad 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 3207ce33ad2 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards 98dcd280626 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards b55569286e0 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 5fc1e4434a5 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards 2e07691f6f5 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 413b9f62e53 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 92ba4e632c5 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards f4698b96506 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards b7bc9540ae5 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards a9500d907d3 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards a14b8ef6456 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards 73dd29645ea 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards d8149f5fb54 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 21ecad44f19 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards a01c9b2dbee 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 79c6ed89196 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 77bb5ef11fd 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards 9083f3e0f4e 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards 0e63c9a6858 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 79a8ce55444 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 2fba6caca25 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards c085cd8086c 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 03ffe5282f3 125: onsuccess: #614: 1: Success after linux: 12 commits discards 3d3d5e4d78d 124: onsuccess: #612: 1: Success after binutils: 18 commits discards f06846c43f1 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 99e3ed9471d 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards fce5f1de1c4 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards a494311d269 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 52da933907f 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 56273677dff 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new ad1c6e475fd 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new fafd36d2aac 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 6e03ad8ce87 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 697af3fff7f 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new e44d67eea42 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new d55bd582c07 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new e8a5278b492 124: onsuccess: #612: 1: Success after binutils: 18 commits new b029c74ff93 125: onsuccess: #614: 1: Success after linux: 12 commits new 3916587e940 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 1fb0b6a7cc1 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new aa2b0135ef6 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 01b8912a3a0 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new c9b46e6bdd9 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new fabe771589e 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 7a827db5a77 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 7a505a45cf2 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new 3f059379c9d 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new aed9b949719 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new b3265938a99 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 9fda78451ca 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new a202aa2d031 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 6304fb04d48 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new c73600a3e05 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 71514a0114d 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new ef2b68b575b 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new ec5c5226f26 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 320bdc1bf2c 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new c7ebed1aad4 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new c1b6e2e6ac8 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 42f515d1b0d 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new a8d3a66b5e3 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 4afb60d88a4 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 016a420abdf 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 8fd66189543 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new a5a32b6dfca 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new bee202c31f5 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new cd98bce463b 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new c8d5138a335 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 89c422e4f64 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 5bf45591bca 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 37e2263e13b 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 845a1f1a1f4 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 362cc80cf70 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new f00b1a533aa 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 3c2a5ac286a 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 261f40f6dcf 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 112f3db1365 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new aeaa902838d 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 915d85d5ede 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 49935017e70 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 29f4dc396f0 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 0cb39d84b54 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 525837abf10 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new d1fa86bc386 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 0c0eee27ce9 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 84273248dc9 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new a81e473433c 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new a0e66d41fab 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new e46285503f9 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new a946b25437d 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 3b5317682a4 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new a13e578fbf4 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new fcb89a6d20a 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new 3a55c30e808 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 3dccd36b4d3 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 4cee1173fef 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 394f629fc61 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new d4f39c2594b 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 2dd0013f9c0 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new 37c9f01fa8c 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new 6141b1841c3 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new 333e80ac5b8 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 8a90294ed95 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new e04d6c616e3 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 01384e7e3b8 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 4e37b093872 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 040881e3539 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 7d7edc2b19c 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 91e3187aaf8 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 647b8df6804 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 6e08953a61a 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new f1d94dfee23 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 1fad1ddbba4 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new b891fb01913 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new f0bae86d0e0 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 50a03fb2999 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new c11dadcfcb7 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new ba86da17e4a 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new ac8c66161c1 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new b2469842739 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new f5b012ec2e9 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new bd6ea2b19e4 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new fe0f9f2cdff 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 6e5eb42edaf 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new cc44ec0fad8 212: force: #27: : Failure after baseline build: no new commits new 9e035a4081a 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 20a3aac3888 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] new b71ef31bd35 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] new 8661a1af9b1 216: force: #43: : Failure after baseline build: no new commits new d326c61e358 217: force: #45: 1: Success after linux: 1 commits new 35ebf39bcf1 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] new e37c75ffcf5 219: force: #50: 1: Failure after linux: 2520 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 (4f442b10fe1) \ 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 2236 -> 2232 bytes 02-prepare_abe/console.log.xz | Bin 2488 -> 2492 bytes 03-build_abe-binutils/console.log.xz | Bin 49020 -> 49152 bytes 04-build_abe-gcc/console.log.xz | Bin 235568 -> 236336 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8824 -> 8436 bytes 07-build_abe-glibc/console.log.xz | Bin 233700 -> 233536 bytes 08-build_abe-gdb/console.log.xz | Bin 46584 -> 46992 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3768 -> 3820 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4416 -> 4556 bytes 11-check_regression/console.log.xz | Bin 3352 -> 3924 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 10 + 11-check_regression/jira-body.txt | 2 +- 11-check_regression/mail-body.txt | 20 +- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results.compare | 20 +- 11-check_regression/results.regressions | 18 ++ 11-check_regression/trigger-bisect | 3 + 12-update_baseline/console.log | 42 +-- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 20 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- results | 18 ++ sumfiles/gdb.log.0.xz | Bin 2961736 -> 2885416 bytes sumfiles/gdb.log.1.xz | Bin 139020 -> 142996 bytes sumfiles/gdb.log.10.xz | Bin 0 -> 10012 bytes sumfiles/gdb.log.2.xz | Bin 12340 -> 12228 bytes sumfiles/gdb.log.3.xz | Bin 10256 -> 10320 bytes sumfiles/gdb.log.4.xz | Bin 10240 -> 10260 bytes sumfiles/gdb.log.5.xz | Bin 10312 -> 10100 bytes sumfiles/gdb.log.6.xz | Bin 10184 -> 10292 bytes sumfiles/gdb.log.7.xz | Bin 0 -> 10308 bytes sumfiles/gdb.log.8.xz | Bin 0 -> 10132 bytes sumfiles/gdb.log.9.xz | Bin 0 -> 10028 bytes sumfiles/gdb.sum | 88 +++--- sumfiles/gdb.sum.0 | 107 ++++---- sumfiles/gdb.sum.1 | 464 ++++++++++++++++++++------------ sumfiles/{gdb.sum.4 => gdb.sum.10} | 31 +-- sumfiles/gdb.sum.2 | 23 +- sumfiles/gdb.sum.3 | 57 +--- sumfiles/gdb.sum.4 | 70 ++--- sumfiles/gdb.sum.5 | 15 +- sumfiles/gdb.sum.6 | 30 +-- sumfiles/{gdb.sum.6 => gdb.sum.7} | 70 +++-- sumfiles/{gdb.sum.4 => gdb.sum.8} | 19 +- sumfiles/{gdb.sum.4 => gdb.sum.9} | 32 +-- 50 files changed, 638 insertions(+), 548 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 create mode 100644 sumfiles/gdb.log.10.xz create mode 100644 sumfiles/gdb.log.7.xz create mode 100644 sumfiles/gdb.log.8.xz create mode 100644 sumfiles/gdb.log.9.xz copy sumfiles/{gdb.sum.4 => gdb.sum.10} (99%) copy sumfiles/{gdb.sum.6 => gdb.sum.7} (99%) copy sumfiles/{gdb.sum.4 => gdb.sum.8} (99%) copy sumfiles/{gdb.sum.4 => gdb.sum.9} (99%)