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 33353c897a3 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] discards b5b344afd64 222: force: #60: 1: Success after gdb: 16 commits discards e075be965de 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] discards 7184c4772de 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] discards 18f9a039bac 219: force: #50: 1: Failure after linux: 2520 commits discards 8689f8aa97b 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] discards 91cc950b931 217: force: #45: 1: Success after linux: 1 commits discards b6c1c9c2bb1 216: force: #43: : Failure after baseline build: no new commits discards 0a6d7a90fb2 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 41152e95863 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] discards b433203af9d 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards c5a04ce66a9 212: force: #27: : Failure after baseline build: no new commits discards 1998240b733 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 77a0d7f43d0 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards fdb65b13d27 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards d2137e1cbfb 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 77dbb4efbd9 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 1b76ed4a7b1 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 322662ce43f 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards d1c3909bab4 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 23f56cbae7c 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 7796499d2d3 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 2f7ddeaf469 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 57186f9ebfe 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 592d7c1c493 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 28d2cfa1c2a 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards ac74fa60b77 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards e10135d7ba3 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards abb2ede7267 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 996f829ee1b 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 27ec94f5481 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards df98b3ad609 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 33abfb68c88 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards b1e40df860a 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 8d82d299bcf 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards 057a9b18d35 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards c9605622626 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 6c411da8691 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards c8099b38897 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards 67546a791d4 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 08438775d13 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards dd33c1cd15b 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards f2ddcf4e2d9 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 5f4f1adff7d 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards 28e8b9ba655 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards e09be13d13c 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 9106fc50bd7 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 6626336cf2b 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 86ad5e8e8c0 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 7e01ab61b41 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 80288974e63 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards b96444751ea 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards f16d737b5f4 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards c0b938e2108 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards 637579edfae 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 0d7583ffb5f 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 4294ddda11c 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 7fe4e0f13b9 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 2f6d4d85995 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 5fd8dbeeea9 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards 525136267b3 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 4adb0571cb1 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 716cb3c9a59 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 53405e50f1a 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 18e18ff28d5 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards a7b36ef7b5b 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards a9b1473fac1 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 661a8fe411e 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 767ae4939b5 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 73a2290bb44 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards 1c999adc42f 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 57087b3b76f 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 4e996a43332 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 000d5c99023 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 6306f82df6c 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 9daa074f90a 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 567127904c5 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards 461558dfa93 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards ce4a6513db1 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 7d73f9e7c63 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards 220559cb486 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 9b635d4b790 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards f5e62d68e19 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards df1ff6cf443 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 2109aaa185b 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 4d2df565175 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 6b476fca3b0 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards 585ee0b556e 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 9ffe0a9ed23 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards b558b23fe87 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 1149bd3d64b 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 16add6241e6 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 0b27ba3794b 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards 8cad1ee59ad 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards e0cd19f44ba 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 8286a02742a 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 56d6ecacd5c 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards ef1833682d0 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards f9d46409131 125: onsuccess: #614: 1: Success after linux: 12 commits discards d4bea1b71f6 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 968e24eb572 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 3e6da4d4738 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new f33a30ae62f 124: onsuccess: #612: 1: Success after binutils: 18 commits new c6dcd0b26aa 125: onsuccess: #614: 1: Success after linux: 12 commits new 179a572a94d 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new b69eb01981b 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 8e81dd3c4f8 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 35be5acdfa7 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 259e60470e5 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new 205c7bf54d4 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 25bd5a2f2d5 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new d87efd6f35f 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new 71171d70119 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 2f5d464498c 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 75bcab541c5 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new e5f356bd8a0 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 2509c6af857 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 09743d53b43 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 938e78c6296 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 05b1d79a045 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new f8c9cee5d09 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 7722913e484 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 135b8db0dca 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new 9b491b59fbd 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 9c01af8c9fc 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 8bd12d88013 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new b0bf38e7010 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 7c9c703e0e8 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 692cc2e7bf9 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new fafb4bebf5f 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 94172abe4c2 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new e463f013e50 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 8ad774091ae 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new 69a6f2623f6 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new d4bdb1507fb 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 476ff996f9b 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new e8f581c33cf 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 9fe685b559c 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 7d591e23d1c 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 2b2c3248f94 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new e0f87e86fbf 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 00f1f3ec2c3 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 99e577c9c87 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new ed012150161 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 920acdce0c1 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 6d2fdcca39f 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new bf7f2fff794 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 407246d5fea 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 8a096489a55 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new 1d7091cfd9a 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 48f4007858f 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 61e6b04c398 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new dca41017c4d 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new de57d88786a 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 6e7ad2509a0 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 2c3ec93598e 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 0b03c692b27 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new e940b20d9ed 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 510f605830e 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new 2b202476094 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 457615a8764 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 7665eb71eae 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 5fd0b63329b 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new 885a4b1367c 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 6007543a4d9 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new c6e8ceaefaf 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new 3c145092772 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new c3d3c1aeb91 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 6804464aca6 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 0c5e4893f15 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 477f0c571c6 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 5b3956c979d 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 6e756f4657f 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 395db87ff7b 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 2a5e0949717 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 80e24cafd27 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new e655b198477 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 1ed3c473aca 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 832669d31a0 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 6f0fe88ab99 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new e6061622fd6 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 6e4cdfb90c4 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 5506841ac79 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new e85dfcf2683 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 9838d2f0be8 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 2a5b21be30b 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new f3696b30807 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new be4aa6fbfdf 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 50fd581f60c 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new dcd02ee8772 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 42f1ecbae16 212: force: #27: : Failure after baseline build: no new commits new 4ab7e5e2b97 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 00e4df4fc9d 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] new db1c0217ff5 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] new 28ccbe48786 216: force: #43: : Failure after baseline build: no new commits new b9730160d4e 217: force: #45: 1: Success after linux: 1 commits new 6004ebb1353 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] new 70a62d0f070 219: force: #50: 1: Failure after linux: 2520 commits new 4cdd3676623 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] new 28a8b45f97b 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] new f281cc03e6e 222: force: #60: 1: Success after gdb: 16 commits new c7f34ab4b85 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] new 36cd9ded455 224: force: #65: 1: Success after gdb: 50 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 (33353c897a3) \ 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 2328 -> 2280 bytes 02-prepare_abe/console.log.xz | Bin 2560 -> 2496 bytes 03-build_abe-binutils/console.log.xz | Bin 49216 -> 49128 bytes 04-build_abe-gcc/console.log.xz | Bin 235976 -> 236252 bytes 06-build_abe-linux/console.log.xz | Bin 8596 -> 8600 bytes 07-build_abe-glibc/console.log.xz | Bin 233332 -> 233916 bytes 08-build_abe-gdb/console.log.xz | Bin 47088 -> 47200 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3792 -> 3772 bytes 10-build_abe-check_gdb/console.log.xz | Bin 5048 -> 5224 bytes 11-check_regression/console.log.xz | Bin 4508 -> 3528 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 60 - 11-check_regression/mail-body.txt | 36 +- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results.compare | 62 +- 11-check_regression/results.regressions | 68 - 11-check_regression/trigger-bisect | 3 - 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 58 +- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- jenkins/mail-body.draft | 627 --- jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/mail-body-header.txt | 103 - mail/mail-body.txt | 36 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- results | 68 - sumfiles/gdb.log.0.xz | Bin 2937628 -> 2865716 bytes sumfiles/gdb.log.1.xz | Bin 146400 -> 188708 bytes sumfiles/gdb.log.2.xz | Bin 16692 -> 20384 bytes sumfiles/gdb.log.3.xz | Bin 10228 -> 10332 bytes sumfiles/gdb.log.4.xz | Bin 10156 -> 10124 bytes sumfiles/gdb.log.5.xz | Bin 10036 -> 9980 bytes sumfiles/gdb.log.6.xz | Bin 10120 -> 10256 bytes sumfiles/gdb.log.7.xz | Bin 10076 -> 10232 bytes sumfiles/gdb.log.8.xz | Bin 10200 -> 10048 bytes sumfiles/gdb.sum | 5520 ++++---------------- sumfiles/gdb.sum.0 | 5531 ++++---------------- sumfiles/gdb.sum.1 | 8663 +++++++++++++++++++++++++++++-- sumfiles/gdb.sum.2 | 661 +-- sumfiles/gdb.sum.3 | 55 +- sumfiles/gdb.sum.4 | 39 +- sumfiles/gdb.sum.5 | 37 +- sumfiles/gdb.sum.6 | 40 +- sumfiles/gdb.sum.7 | 26 +- sumfiles/gdb.sum.8 | 41 +- 49 files changed, 11105 insertions(+), 10659 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