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 36cd9ded455 224: force: #65: 1: Success after gdb: 50 commits discards c7f34ab4b85 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] discards f281cc03e6e 222: force: #60: 1: Success after gdb: 16 commits discards 28a8b45f97b 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] discards 4cdd3676623 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] discards 70a62d0f070 219: force: #50: 1: Failure after linux: 2520 commits discards 6004ebb1353 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] discards b9730160d4e 217: force: #45: 1: Success after linux: 1 commits discards 28ccbe48786 216: force: #43: : Failure after baseline build: no new commits discards db1c0217ff5 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 00e4df4fc9d 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 4ab7e5e2b97 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 42f1ecbae16 212: force: #27: : Failure after baseline build: no new commits discards dcd02ee8772 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 50fd581f60c 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards be4aa6fbfdf 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards f3696b30807 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 2a5b21be30b 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 9838d2f0be8 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards e85dfcf2683 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 5506841ac79 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 6e4cdfb90c4 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards e6061622fd6 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 6f0fe88ab99 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 832669d31a0 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 1ed3c473aca 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards e655b198477 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 80e24cafd27 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 2a5e0949717 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 395db87ff7b 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 6e756f4657f 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 5b3956c979d 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 477f0c571c6 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 0c5e4893f15 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 6804464aca6 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards c3d3c1aeb91 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards 3c145092772 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards c6e8ceaefaf 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 6007543a4d9 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards 885a4b1367c 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards 5fd0b63329b 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 7665eb71eae 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 457615a8764 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 2b202476094 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 510f605830e 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards e940b20d9ed 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards 0b03c692b27 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 2c3ec93598e 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 6e7ad2509a0 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards de57d88786a 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards dca41017c4d 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 61e6b04c398 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 48f4007858f 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 1d7091cfd9a 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 8a096489a55 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards 407246d5fea 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards bf7f2fff794 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 6d2fdcca39f 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 920acdce0c1 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards ed012150161 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 99e577c9c87 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards 00f1f3ec2c3 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards e0f87e86fbf 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 2b2c3248f94 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 7d591e23d1c 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 9fe685b559c 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards e8f581c33cf 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 476ff996f9b 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards d4bdb1507fb 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 69a6f2623f6 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 8ad774091ae 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards e463f013e50 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 94172abe4c2 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards fafb4bebf5f 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 692cc2e7bf9 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 7c9c703e0e8 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards b0bf38e7010 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 8bd12d88013 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards 9c01af8c9fc 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards 9b491b59fbd 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 135b8db0dca 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards 7722913e484 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards f8c9cee5d09 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 05b1d79a045 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 938e78c6296 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 09743d53b43 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 2509c6af857 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards e5f356bd8a0 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards 75bcab541c5 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 2f5d464498c 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 71171d70119 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards d87efd6f35f 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 25bd5a2f2d5 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 205c7bf54d4 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards 259e60470e5 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards 35be5acdfa7 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 8e81dd3c4f8 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards b69eb01981b 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 179a572a94d 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards c6dcd0b26aa 125: onsuccess: #614: 1: Success after linux: 12 commits discards f33a30ae62f 124: onsuccess: #612: 1: Success after binutils: 18 commits new 679c2cfd986 124: onsuccess: #612: 1: Success after binutils: 18 commits new 43d7136b2ac 125: onsuccess: #614: 1: Success after linux: 12 commits new fd9b07042c5 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new a506c7245fd 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 3a3cb44a4b2 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new f155b1a7f53 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 89b579477cc 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new 64bb2727267 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 6325d095378 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 4e7112a31a2 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new 0a98dc8ec59 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 0be18bc6d20 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new f7c168577dc 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 310e4039281 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new d2faccc582d 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 29bf0d3564c 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 65633f6d29b 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 8b2b1f0ee5c 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new cf554ef4d8a 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new da7bcee51aa 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 853fc7ebf5b 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new 04e2172fd03 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new f0845750cf2 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new a579fefd0ee 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new bfd83bf72e9 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 0f687f03ec6 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 93e76ed6afe 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 565fbaa5439 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 2a2baf54648 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new 8be02fadc5a 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 6fa44611d25 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new 9ab384690a6 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new f4c450c8286 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new da854851005 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 03c64063d66 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new a67e6130ed4 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 721ef5ac15d 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 36e526d509a 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 43bea156207 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 8135a88b4e0 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 5030bfe5189 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new e865c91933a 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new d96e46f8cf9 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new e7656b97aef 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 97a60f4416d 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 72a89e76093 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 74910014b27 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new 0c84f9ab671 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new fdfbdd792d5 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new f155e2bb4e6 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new 7df6b106f39 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new c825ff829b0 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new b3634a1892b 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new bcc3e6e91f5 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 678f007e80e 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 1750aaaa29c 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 9991ab5690b 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new 5c17b28a7f7 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new f80282e3b1b 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 29fa1f8ab9e 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new c40e38ff1ae 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new 00145cefb8d 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 35df03247fc 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new 93cb6b6095e 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new 6261cad2162 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new 9a004d7a8c0 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 9f0be6f2cc6 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 6c375ce44c0 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 556b0d5a333 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 2479289494e 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 5f0f4d4699f 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 2c0fb16250e 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new c7cc41839ab 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 908f6b564a3 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 8b36972914e 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 4c33f5991d8 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 81c94e177e3 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new a61e83c1383 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new c3493c8d470 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 88fb863bc0c 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 203ed4a3186 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 66d1f325a14 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 201a9f8655b 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 2e12ea58e09 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 74797c910b9 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 477d9f60d73 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new a10470fbb7d 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 68876426025 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new a89f0fe5252 212: force: #27: : Failure after baseline build: no new commits new df3646e188d 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 87289a1bd18 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] new ee61d0a676f 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] new 620c7d73590 216: force: #43: : Failure after baseline build: no new commits new edf6bb51168 217: force: #45: 1: Success after linux: 1 commits new 2053df3f758 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] new cf36114eb1a 219: force: #50: 1: Failure after linux: 2520 commits new 380fb9ab22f 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] new 9ec0c92fbc2 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] new 7bed66ffcf9 222: force: #60: 1: Success after gdb: 16 commits new 51d9b700ae9 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] new d3fd534e740 224: force: #65: 1: Success after gdb: 50 commits new 599f63f7e86 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...]
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 (36cd9ded455) \ 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 2280 -> 2064 bytes 02-prepare_abe/console.log.xz | Bin 2496 -> 2560 bytes 03-build_abe-binutils/console.log.xz | Bin 49128 -> 49364 bytes 04-build_abe-gcc/console.log.xz | Bin 236252 -> 235184 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8600 -> 8608 bytes 07-build_abe-glibc/console.log.xz | Bin 233916 -> 233340 bytes 08-build_abe-gdb/console.log.xz | Bin 47200 -> 50424 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3772 -> 3828 bytes 10-build_abe-check_gdb/console.log.xz | Bin 5224 -> 7872 bytes 11-check_regression/console.log.xz | Bin 3528 -> 4108 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 6 + 11-check_regression/mail-body.txt | 84 +- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results.compare | 20 +- 11-check_regression/results.regressions | 14 + 11-check_regression/trigger-bisect | 3 + 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 52 +- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 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 | 84 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- results | 14 + sumfiles/gdb.log.0.xz | Bin 2865716 -> 2903160 bytes sumfiles/gdb.log.1.xz | Bin 188708 -> 146428 bytes sumfiles/gdb.log.2.xz | Bin 20384 -> 20152 bytes sumfiles/gdb.log.3.xz | Bin 10332 -> 15304 bytes sumfiles/gdb.log.4.xz | Bin 10124 -> 10268 bytes sumfiles/gdb.log.5.xz | Bin 9980 -> 10436 bytes sumfiles/gdb.log.6.xz | Bin 10256 -> 10076 bytes sumfiles/gdb.log.7.xz | Bin 10232 -> 10024 bytes sumfiles/gdb.log.8.xz | Bin 10048 -> 10080 bytes sumfiles/gdb.sum | 3841 +++++++++++++- sumfiles/gdb.sum.0 | 3848 +++++++++++++- sumfiles/gdb.sum.1 | 8381 +------------------------------ sumfiles/gdb.sum.2 | 53 +- sumfiles/gdb.sum.3 | 215 +- sumfiles/gdb.sum.4 | 15 +- sumfiles/gdb.sum.5 | 88 +- sumfiles/gdb.sum.6 | 51 +- sumfiles/gdb.sum.7 | 33 +- sumfiles/gdb.sum.8 | 20 +- 50 files changed, 8623 insertions(+), 8798 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 11-check_regression/trigger-notify create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh create mode 100644 mail/mail-body-header.txt