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 c7a9a1e93df 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards aaec93ffbb9 212: force: #27: : Failure after baseline build: no new commits discards 5a3f8f1daaa 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 1f6156a8c5f 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 6b8c7ea305d 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 0be96fcce1c 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards ac6f74b0b58 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 5de8d3bb7ad 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards cdaec2e3782 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards c540f53224e 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 80b6dd1520f 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 0795d7971b9 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 01d24c12448 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 99b9f0667ac 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 84c8f909092 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards d399fcafed1 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards e855a2db69a 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 1b8247508eb 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards ecf18b6c16c 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards a8610336b33 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 9548071fdb2 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards ba04da506a5 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards adc40b51e6a 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 4493354ec97 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 680f602e556 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards 8471b105b65 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards f99b2971a4f 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 1ec26b89439 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards abf5cbe5766 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards a2df8bec62b 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards e41c1044aea 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 6c3cd268238 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 64956667714 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards a90d3c6f5e7 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards 8216d13d994 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards 493e1f0c6a6 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards ae49b4023af 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 42bd1a77ae0 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 603fe4d38f8 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 8aa0e25fd40 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 5d9b5e2abc8 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 9698fa494e0 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards fd574bd8c58 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 853f732d924 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards 1f8a6c5f3b7 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards f6bbe07cab2 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 1cf277552a5 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 5936d098563 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 8616588729a 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards e0d5a6fa056 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards dc88531c7db 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 77ea73703b6 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 85f81b66d62 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards bc29733c75d 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 459e4b590c7 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 48a5ccaeca9 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 732af35775b 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 41ec8d1abff 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 5267e68ba6c 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 1836b0f0026 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards 4dc1e22d43b 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 4825837ebd1 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards daf14d5c8b7 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 61b8403248d 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 4f1db502acb 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards d5fbed22ae6 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 0985375defe 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards 7962867e53f 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards 59ac70b1158 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 7b0297a51a1 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards 09b2e47f935 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards c58fc1fa257 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards de26541bfd5 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards c3caa69c4a5 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards f45cffb766f 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards b87f406018d 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards d3c1ac52cfd 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards b6d5ca7cb1a 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 03dcc80a50a 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards ed919065905 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 6adc19b5c68 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards db3658805fb 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 5fdc56251f3 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards f17ba0c4bfc 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards 482c3fda64d 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards e00d79ffb37 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards b6bc0c87a5f 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards ce3ab4c50e5 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 247f3226efd 125: onsuccess: #614: 1: Success after linux: 12 commits discards c5d30ba3ba0 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 82ab3569b48 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 547e0bcb7a6 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards b952d75cf48 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 687f74aecf9 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards ad7dcfa9562 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 2a3e518e546 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards b47c4eb8804 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards b9e79a01ae6 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards a8bf816de35 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 3764eabb360 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards a5c6ace0201 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 1c76f32c626 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 3e01d58d919 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new b55e11d75c7 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 9ebf8f063cc 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 51d267f64e4 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new 06601bd4324 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 55d19e681d3 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new fa28484c5b0 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new bdc67e1a5cd 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new efdc5bcb13a 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 4cc00bd0cbb 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 268291889aa 124: onsuccess: #612: 1: Success after binutils: 18 commits new 7a19bb1a737 125: onsuccess: #614: 1: Success after linux: 12 commits new 5a5820d3054 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 702748885ea 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 5b51ab6e589 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new a26d87cd55c 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 116a06fb1aa 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new 134a122417c 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 46770088f2b 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 879088841ab 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new e8f75af1c09 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 6e9be0c1123 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 07fb3acc66c 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 64351355b22 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new a16112f8193 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new cbfbe511d5c 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 1dc48009a5c 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new fd5dc163941 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new b2244cb7ece 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new d5b690fb3cd 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 5b95fe31b3a 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new c9569d9860f 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new e484f6ccf79 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new d02b8a0b8a3 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new bf8a493aaf4 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 9d554ab7a57 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 5ab5bf2d2f0 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 0bf96192d4e 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 4ac005be718 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new facde2cf4cd 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 34661ea0d39 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new 85b5467555b 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new a17f1b7174b 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 096e449abe5 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 2495137c9e1 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 63bfe1be284 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new fdc8f874d94 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 69f9ef63991 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new d2c67c9a72a 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 5b954218a11 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 0c90325d0ec 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new 9eec578adf9 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 8287172bd27 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new f4148710c21 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 345abae9523 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 40c75315e30 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new b614d5f9c25 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new fcb316ac5d3 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new e23d7f8762c 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 118a27b875d 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new 7863a8c7fa5 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new a48260e0843 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 7269354c677 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 8dce8e34b23 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 227fbe1f453 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 715d3a5f63b 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 8b994d33784 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new 8dd64944ab7 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 334593c4a89 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 420aba9c8d4 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 97e4e0f3646 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new 4d2d33a9af0 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 114bc8bda89 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new f57a96a9a0b 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new 8ca20f7788f 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new 5dceab0d3ca 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 59877a584ed 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 88c2b9aad99 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 7759901b099 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 3297dc81b03 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new daaddba1d89 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new fa2cf194c53 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new ed8c0a27494 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new ad67fab3356 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 8d0331431f2 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new d7dedbf4575 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 19a2ad84848 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new c6a6f5c783a 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new d89eadc44a0 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new e6632f330ca 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 16d35b753d6 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 50b3e8465be 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 781c4d3ac08 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 829e82c2cb2 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 48eff13626e 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 5e493d860bd 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new a2690632cc2 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 9e5600e9fc5 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 5b9c0d9c960 212: force: #27: : Failure after baseline build: no new commits new 8cbe83380c6 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 45727ffcebf 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-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 (c7a9a1e93df) \ 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 1760 -> 2072 bytes 02-prepare_abe/console.log.xz | Bin 2452 -> 2516 bytes 03-build_abe-binutils/console.log.xz | Bin 48356 -> 48596 bytes 04-build_abe-gcc/console.log.xz | Bin 236520 -> 235220 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8556 -> 8668 bytes 07-build_abe-glibc/console.log.xz | Bin 233108 -> 233692 bytes 08-build_abe-gdb/console.log.xz | Bin 47420 -> 46984 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3772 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4248 -> 4436 bytes 11-check_regression/console.log.xz | Bin 4072 -> 4500 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 12 + 11-check_regression/jira-body.txt | 2 +- 11-check_regression/mail-body.txt | 51 +- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results.compare | 46 + 11-check_regression/results.compare2 | 1 + 11-check_regression/results.regressions | 46 + 11-check_regression/trigger-bisect | 3 + 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 148 ++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 51 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +- results | 46 + sumfiles/gdb.log.0.xz | Bin 2932132 -> 2937136 bytes sumfiles/gdb.log.1.xz | Bin 143088 -> 143240 bytes sumfiles/gdb.log.2.xz | Bin 16976 -> 21432 bytes sumfiles/gdb.log.3.xz | Bin 14948 -> 19932 bytes sumfiles/gdb.log.4.xz | Bin 10396 -> 14860 bytes sumfiles/gdb.log.5.xz | Bin 10256 -> 6480 bytes sumfiles/gdb.sum | 149 +- sumfiles/gdb.sum.0 | 153 +- sumfiles/gdb.sum.1 | 284 ++-- sumfiles/gdb.sum.2 | 340 ++++- sumfiles/gdb.sum.3 | 333 ++++- sumfiles/gdb.sum.4 | 348 ++++- sumfiles/gdb.sum.5 | 2454 ++++--------------------------- 47 files changed, 1979 insertions(+), 2608 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.compare create mode 100644 11-check_regression/results.compare2 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/jira-status.draft 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