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 fca47daa7bc 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g [...] discards 91ea351c2a2 228: force: #74: 1: Success after gdb: 53 commits discards 4308ad7c0f9 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] discards ad5b220159a 226: force: #70: 1: Success after baseline build: no new commits discards 3abafdb6f0b 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] discards 5d0277a895b 224: force: #65: 1: Success after gdb: 50 commits discards a7b4a0426d0 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] discards 1cabebf56c2 222: force: #60: 1: Success after gdb: 16 commits discards 1715025972f 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] discards 8e08e7403d5 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] discards 10cf5950eec 219: force: #50: 1: Failure after linux: 2520 commits discards 0a28d1364b4 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] discards 3cfd9e64f86 217: force: #45: 1: Success after linux: 1 commits discards bf833128a3c 216: force: #43: : Failure after baseline build: no new commits discards 279c2f53b28 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] discards de615f0f2da 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 929301a510f 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 7e3fb20e0e4 212: force: #27: : Failure after baseline build: no new commits discards 867cda970a4 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards fcaaa55e06b 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 0d89a04706e 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards dfd22beed80 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards e1380276169 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards c503e326273 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 4430cb3d21b 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards f6299d13e3a 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards bd60b441477 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards b6a6dccc290 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards f89c705fe02 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 99389e31edf 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards a390dace9ee 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 0ce8218ed17 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 5bc0489af66 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 9737f14fd29 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 5b830a62ad0 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 08b4d54810f 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 2949a1c6bd4 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 4398a08257b 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 4555e39022c 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 2183f541b05 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 85f45e478e4 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards a744fb07a9b 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards 7f60c14e12b 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 7cf4a290acd 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards 57d7689cbeb 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards 60b0c546768 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards ab137f5830f 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards a1a9f8115e2 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 060a3585fe4 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 25ed98ae4b5 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards 21c8ae19b60 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards 3d990817926 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 3b7ca1716e2 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 50b660e1991 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 25861ae3454 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards dd7253882e9 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 9a057f56f78 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 6c50981249f 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards a3880810063 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 7850328a6a2 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards d520b212b34 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards fa1225686ee 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards e8cb1bcf9f0 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 165fe23dd7f 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 9f8b0d9644c 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 4ff7c143750 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards 7f26f6088e3 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards bcdea786f6c 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards a1b9bedabc2 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards ba46021760d 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards b6e835b869b 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards d1a4c8ec347 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards a87ae6bd837 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards a5fa3be7f6a 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards c9dbb47bce7 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 20a91c77fc7 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards 768b71c613a 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 3ee6c6715ac 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 700acc1c4c2 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards dda44b46ca0 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards ec541d18870 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 968843769d8 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 027d831225e 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards 38324158c0d 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards 4cad7e10733 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 5ea0909c7d7 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards af419546f42 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 307322fd444 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards a03d638229c 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards b1adfd9ff13 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 69b501a4e22 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 8678209b2f7 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 6a0f08f8f1c 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards 99782e90723 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 73d69190797 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 6ae4e283819 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 22728b60961 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards c18b0f96864 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 8247660e299 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards be3c345491c 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards f9ec5cfe7ca 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 51a28bd42d9 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 6d63f5e6d5b 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new fbbb4ba903b 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 49144a02b4c 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 856c6e5422a 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new 7b8b4080f11 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new abf65ee89f7 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 8ddfa9988fa 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 2b97408e9e8 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 8c3410e3f85 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new b21c0652085 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 620b899fc60 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new f3809aff780 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new d36b88721da 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new bca52960e27 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 29ad9a8e14b 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new 21d94433507 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 48dfbfc5452 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 169dfeee396 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new f265ccd6174 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new e05e5c5d1bb 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 1d58a740227 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 69cfc214f46 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 9b455770bf8 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new f1ba4c8f42e 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 711c849e9a9 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new c010943b0c1 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new d099974afc5 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new f524582ae60 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new f155fc513a7 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new e2f6410b940 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 42cfd3857c7 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 4b5d7e53e67 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 68d904a383f 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 57bf3d77874 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new c9e20393df0 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new 9ee49ffcc7e 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new f5947f9d85c 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new cfdea43ef81 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 88fa5900b15 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 2fe6f1be44d 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new d2ba2c5fb6d 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new 01eb26e3eb2 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new be5bd0441ee 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new aa205daa26a 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new b830a83978a 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 29ee549f47c 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new e0a8c2b0b3c 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 3d77550f50c 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 46dfc7b6989 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 3ffb806cf94 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 262a2a5d57e 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new d865065c7ed 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 0da7666a235 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new ab8079fdd2c 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new d18251dc393 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new 344f0370818 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 1bd511feba3 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new f3013aab3a2 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new d5ec857da98 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new a02d6a4c586 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 09440d44783 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 33a590e474c 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new c3bb6781464 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 638d0b23b71 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new a461fe1a7fe 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 997f86df36f 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 8efb835b206 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new d3a5d50a75d 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 837b805a3b5 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 4799b8abc0f 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new e747d481107 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new b06efa0ecf8 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 41fce251548 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new cbe318a26c1 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 3022aa96bce 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 7f825e4c152 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 557e3b70a4c 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new a8ed2f51e69 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 237be255142 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 144b293af74 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new fbac7c0b44f 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 992b3c137ea 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new d3dc3f889bb 212: force: #27: : Failure after baseline build: no new commits new 8787a00621e 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 6b6cca93328 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] new c95c2e0d21e 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] new f2d3e9a154d 216: force: #43: : Failure after baseline build: no new commits new 90252a5c9d6 217: force: #45: 1: Success after linux: 1 commits new b6f78fab9a7 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] new 62a6745f1f1 219: force: #50: 1: Failure after linux: 2520 commits new 4dee74cc6b6 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] new f185c6b7368 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] new a35094b7e4f 222: force: #60: 1: Success after gdb: 16 commits new f96743f6f57 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] new 892da422ffa 224: force: #65: 1: Success after gdb: 50 commits new 8ccaaf315f0 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] new 0fa6d38785d 226: force: #70: 1: Success after baseline build: no new commits new 5101877455b 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] new 1f56396f620 228: force: #74: 1: Success after gdb: 53 commits new 7cb6833f922 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g [...] new 73b50b2cb85 230: onsuccess: #78: 1: Success after gdb: 2 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 (fca47daa7bc) \ 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 1956 -> 1996 bytes 02-prepare_abe/console.log.xz | Bin 2520 -> 2536 bytes 03-build_abe-binutils/console.log.xz | Bin 49200 -> 49112 bytes 04-build_abe-gcc/console.log.xz | Bin 234456 -> 234700 bytes 06-build_abe-linux/console.log.xz | Bin 8484 -> 8544 bytes 07-build_abe-glibc/console.log.xz | Bin 232396 -> 232968 bytes 08-build_abe-gdb/console.log.xz | Bin 46484 -> 46368 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3768 -> 3768 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4420 -> 4448 bytes 11-check_regression/console.log.xz | Bin 4092 -> 4212 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 6 - 11-check_regression/mail-body.txt | 30 ++-- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results.compare | 9 +- 11-check_regression/results.compare2 | 113 ++++++++++++++- 11-check_regression/results.regressions | 14 -- 11-check_regression/trigger-bisect | 3 - 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 42 +++--- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- jenkins/mail-body.draft | 239 -------------------------------- jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/mail-body-header.txt | 49 ------- mail/mail-body.txt | 30 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 20 +-- results | 14 -- sumfiles/gdb.log.0.xz | Bin 2893016 -> 2895788 bytes sumfiles/gdb.log.1.xz | Bin 143636 -> 143188 bytes sumfiles/gdb.log.10.xz | Bin 0 -> 10108 bytes sumfiles/gdb.log.2.xz | Bin 20012 -> 20312 bytes sumfiles/gdb.log.3.xz | Bin 10240 -> 10088 bytes sumfiles/gdb.log.4.xz | Bin 10088 -> 10240 bytes sumfiles/gdb.log.5.xz | Bin 10120 -> 10236 bytes sumfiles/gdb.log.6.xz | Bin 0 -> 10172 bytes sumfiles/gdb.log.7.xz | Bin 0 -> 10320 bytes sumfiles/gdb.log.8.xz | Bin 0 -> 10240 bytes sumfiles/gdb.log.9.xz | Bin 0 -> 9900 bytes sumfiles/gdb.sum | 49 ++----- sumfiles/gdb.sum.0 | 52 +++---- sumfiles/gdb.sum.1 | 63 ++++++--- sumfiles/{gdb.sum.4 => gdb.sum.10} | 14 +- sumfiles/gdb.sum.2 | 44 ++++-- sumfiles/gdb.sum.3 | 20 ++- sumfiles/gdb.sum.4 | 20 +-- sumfiles/gdb.sum.5 | 23 +-- sumfiles/{gdb.sum.4 => gdb.sum.6} | 25 +++- sumfiles/{gdb.sum.4 => gdb.sum.7} | 25 ++-- sumfiles/{gdb.sum.4 => gdb.sum.8} | 32 +++-- sumfiles/{gdb.sum.5 => gdb.sum.9} | 78 ++--------- 54 files changed, 375 insertions(+), 653 deletions(-) delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.regressions delete mode 100644 11-check_regression/trigger-bisect delete mode 100644 11-check_regression/trigger-notify delete mode 100644 jenkins/mail-body.draft delete mode 100644 jenkins/mail-recipients.draft delete mode 100644 jenkins/mail-subject.draft delete mode 100755 jenkins/notify.sh delete mode 100644 mail/mail-body-header.txt create mode 100644 sumfiles/gdb.log.10.xz create mode 100644 sumfiles/gdb.log.6.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.4 => gdb.sum.6} (99%) copy sumfiles/{gdb.sum.4 => gdb.sum.7} (99%) copy sumfiles/{gdb.sum.4 => gdb.sum.8} (99%) copy sumfiles/{gdb.sum.5 => gdb.sum.9} (97%)