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 599f63f7e86 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] discards d3fd534e740 224: force: #65: 1: Success after gdb: 50 commits discards 51d9b700ae9 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] discards 7bed66ffcf9 222: force: #60: 1: Success after gdb: 16 commits discards 9ec0c92fbc2 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] discards 380fb9ab22f 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] discards cf36114eb1a 219: force: #50: 1: Failure after linux: 2520 commits discards 2053df3f758 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] discards edf6bb51168 217: force: #45: 1: Success after linux: 1 commits discards 620c7d73590 216: force: #43: : Failure after baseline build: no new commits discards ee61d0a676f 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 87289a1bd18 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] discards df3646e188d 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards a89f0fe5252 212: force: #27: : Failure after baseline build: no new commits discards 68876426025 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards a10470fbb7d 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 477d9f60d73 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 74797c910b9 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 2e12ea58e09 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 201a9f8655b 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 66d1f325a14 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 203ed4a3186 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 88fb863bc0c 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards c3493c8d470 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards a61e83c1383 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 81c94e177e3 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 4c33f5991d8 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 8b36972914e 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 908f6b564a3 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards c7cc41839ab 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 2c0fb16250e 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 5f0f4d4699f 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 2479289494e 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 556b0d5a333 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 6c375ce44c0 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 9f0be6f2cc6 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 9a004d7a8c0 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards 6261cad2162 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards 93cb6b6095e 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 35df03247fc 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards 00145cefb8d 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards c40e38ff1ae 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 29fa1f8ab9e 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards f80282e3b1b 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 5c17b28a7f7 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 9991ab5690b 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards 1750aaaa29c 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards 678f007e80e 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards bcc3e6e91f5 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards b3634a1892b 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards c825ff829b0 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 7df6b106f39 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards f155e2bb4e6 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards fdfbdd792d5 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 0c84f9ab671 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 74910014b27 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards 72a89e76093 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 97a60f4416d 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards e7656b97aef 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards d96e46f8cf9 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards e865c91933a 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 5030bfe5189 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards 8135a88b4e0 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 43bea156207 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 36e526d509a 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 721ef5ac15d 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards a67e6130ed4 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 03c64063d66 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards da854851005 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards f4c450c8286 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 9ab384690a6 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 6fa44611d25 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards 8be02fadc5a 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 2a2baf54648 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 565fbaa5439 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 93e76ed6afe 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 0f687f03ec6 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards bfd83bf72e9 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards a579fefd0ee 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards f0845750cf2 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards 04e2172fd03 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 853fc7ebf5b 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards da7bcee51aa 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards cf554ef4d8a 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 8b2b1f0ee5c 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 65633f6d29b 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 29bf0d3564c 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards d2faccc582d 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 310e4039281 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards f7c168577dc 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 0be18bc6d20 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 0a98dc8ec59 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 4e7112a31a2 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 6325d095378 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 64bb2727267 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards 89b579477cc 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards f155b1a7f53 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 3a3cb44a4b2 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards a506c7245fd 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards fd9b07042c5 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 43d7136b2ac 125: onsuccess: #614: 1: Success after linux: 12 commits new 2099fcbeb33 125: onsuccess: #614: 1: Success after linux: 12 commits new efc19995102 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 6044ea33321 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 9f7a3ee8cee 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new db05500338e 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new fbe5833aaaf 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new bf335ceb744 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new f83afb080e0 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 0c91d689103 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new 4f993c7e31a 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new d6f6a7961df 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new d48ae12d8ae 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new d62b83dea96 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 40c6a35b15c 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new dd1f104df68 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 4f601f28746 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new ecb23953ddb 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new d5d4ba71dc5 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new dc5d6395b35 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new b4b5a99c578 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new 73676157b9f 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new e5de2e0fc12 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new bd2d458ca5e 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new 6173a79524f 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new fb36448b6be 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 8181a0385a8 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 7aa42cf9cef 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new c21c6b9b946 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new d35b2209de4 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new d9a579691ec 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new 8a28a01f1ea 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 13ca79fb2fb 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 39088fcd250 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 88ab4618935 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new ce9e13440db 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 264f6be5384 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new c995f025ebe 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 85f5a725c48 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 5c1b2b713c6 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new b3cddb94c3e 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new 7845edc2317 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 0b3464669e1 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 1fef85a2e4f 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new f30e4cb0ee2 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 7f179cb8f0e 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new b3fc5603240 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new 466441485e0 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 7a0871a05ec 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 94e963b618f 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new ea20919cc3f 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new e20d54ae5bc 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new dc568408e61 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new eb0977bcbf1 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 58875dcc0cd 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new d989e54b68d 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new ff7470818f4 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new 190807954f7 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 34a0fdc800c 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 0120be4d64a 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 2f7ca58d158 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new d3dd7b1837e 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new b5834482b5b 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new bb092aa20ae 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new 698f31bece0 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new e75e0afd0d3 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new e217e3b86d6 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 7c572064eb0 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 26f2140554c 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 0d443980e17 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 650c0c5a754 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new b272eb0ef3e 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 23ba788ab5d 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new ecf16f44964 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new d70f98f39a5 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 02d44776646 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new ec7c584c646 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 0c58658bbc8 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 0443390c621 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 6b5a04eff25 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 4f84fe56100 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 4a77dea95db 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 4afc6d25b72 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new e513f41c3f3 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 070b3d2d32a 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new b276c9039a0 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 3be50482997 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 158bc5098ec 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 37b27b39293 212: force: #27: : Failure after baseline build: no new commits new df8b0f0260d 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 98752a10c41 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] new ec70c3dac99 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] new 3e28e47b3df 216: force: #43: : Failure after baseline build: no new commits new ab62f56d199 217: force: #45: 1: Success after linux: 1 commits new 2a336b7e2b3 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] new d628904170b 219: force: #50: 1: Failure after linux: 2520 commits new 90516df3c33 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] new bf344a90df7 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] new f5f61d12651 222: force: #60: 1: Success after gdb: 16 commits new 94dfbbd1229 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] new 0c6e5afc82c 224: force: #65: 1: Success after gdb: 50 commits new 62405cb0445 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] new 659f3e052b0 226: force: #70: 1: Success after baseline build: no new 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 (599f63f7e86) \ 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 2064 -> 2092 bytes 02-prepare_abe/console.log.xz | Bin 2560 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 49364 -> 49328 bytes 04-build_abe-gcc/console.log.xz | Bin 235184 -> 235344 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8608 -> 8580 bytes 07-build_abe-glibc/console.log.xz | Bin 233340 -> 233912 bytes 08-build_abe-gdb/console.log.xz | Bin 50424 -> 49900 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3760 bytes 10-build_abe-check_gdb/console.log.xz | Bin 7872 -> 7908 bytes 11-check_regression/console.log.xz | Bin 4108 -> 2528 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 | 13 +- 11-check_regression/results.regressions | 14 - 11-check_regression/trigger-bisect | 3 - 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 46 +- dashboard/dashboard-generate.sh | 2 +- jenkins/mail-body.draft | 520 -------- 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 | 11 +- results | 14 - sumfiles/gdb.log.0.xz | Bin 2903160 -> 2822600 bytes sumfiles/gdb.log.1.xz | Bin 146428 -> 146940 bytes sumfiles/gdb.log.2.xz | Bin 20152 -> 20104 bytes sumfiles/gdb.log.3.xz | Bin 15304 -> 10072 bytes sumfiles/gdb.log.4.xz | Bin 10268 -> 10276 bytes sumfiles/gdb.log.5.xz | Bin 10436 -> 10332 bytes sumfiles/gdb.log.6.xz | Bin 10076 -> 10148 bytes sumfiles/gdb.log.7.xz | Bin 10024 -> 10168 bytes sumfiles/gdb.log.8.xz | Bin 10080 -> 0 bytes sumfiles/gdb.sum | 54 +- sumfiles/gdb.sum.0 | 66 +- sumfiles/gdb.sum.1 | 242 ++-- sumfiles/gdb.sum.2 | 31 +- sumfiles/gdb.sum.3 | 215 +-- sumfiles/gdb.sum.4 | 19 +- sumfiles/gdb.sum.5 | 136 +- sumfiles/gdb.sum.6 | 29 +- sumfiles/gdb.sum.7 | 34 +- sumfiles/gdb.sum.8 | 2154 ------------------------------- 49 files changed, 414 insertions(+), 3314 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 delete mode 100644 sumfiles/gdb.log.8.xz delete mode 100644 sumfiles/gdb.sum.8