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 0bb077feff 253: force: #131: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards 98d02b0635 252: force: #130: 1: [TCWG CI] Success after gdb: 15 commits discards 0585bca8af 251: onsuccess: #129: 1: [TCWG CI] Success after linux: 121 commits discards 90d403dccb 250: onsuccess: #128: 1: [TCWG CI] Success after glibc: 2 commits discards 8a4272c790 249: onsuccess: #127: 1: [TCWG CI] Success after gcc: 98 commits discards e4b85ca3fe 248: onsuccess: #121: 1: [TCWG CI] Success after binutils/gc [...] discards 47ae1d7b0b 247: force: #120: 1: [TCWG CI] Success after baseline build: [...] discards a3aa54120b 246: onsuccess: #118: 1: [TCWG CI] Success after glibc: 7 commits discards c7b12b40f9 245: onsuccess: #117: 1: [TCWG CI] Success after gcc: 16 commits discards f3aa839f4d 244: onsuccess: #112: 1: [TCWG CI] Success after binutils/gc [...] discards d41aa24508 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/gc [...] discards ebbe9ce2a5 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits discards b302436e59 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/gc [...] discards 396739d674 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/gc [...] discards 4166f368c6 239: force: #106: 1: [TCWG CI] Success after baseline build: [...] discards 838cef2bc7 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards 3111b822b3 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits discards 6065af79b7 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 22 [...] discards 718f3adc3c 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards fa9672b5df 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards fbee4a6df0 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards e5e2f8c26a 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 1078a97ee4 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits discards 4b4f1bbad0 230: onsuccess: #78: 1: Success after gdb: 2 commits discards fa7af0c1cd 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g4 [...] discards 461ab6c6af 228: force: #74: 1: Success after gdb: 53 commits discards cc61624d1e 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 7eb0fd24cc 226: force: #70: 1: Success after baseline build: no new commits discards 78d5a7fe47 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g4 [...] discards 0a9a1b20e7 224: force: #65: 1: Success after gdb: 50 commits discards b29811e330 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g2 [...] discards 0ca793d191 222: force: #60: 1: Success after gdb: 16 commits discards 6153179389 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g6 [...] discards b8d9185fa3 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02ddb [...] discards c530cc48f4 219: force: #50: 1: Failure after linux: 2520 commits discards b084900c6d 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g3 [...] discards 4bec5f30ad 217: force: #45: 1: Success after linux: 1 commits discards 0d917b2259 216: force: #43: : Failure after baseline build: no new commits discards a3df11cfae 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g1 [...] discards d5cd1ca36f 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g1 [...] discards 674fa80ba5 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards a16be7fc59 212: force: #27: : Failure after baseline build: no new commits discards 48c33c7e15 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards dabf018996 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 45883090a4 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 31379d3281 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards afbc256190 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 3b78213f5f 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 49fbc2e2d2 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 76bdc54233 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 59164c0d1e 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards c278664e23 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 0f9221acaa 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards fe1d8ddae7 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 388c86984f 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 42c1e37299 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 1572b2b69a 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards feb02a56ee 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards d3a602b4a0 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 26eff09f18 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards a49977a494 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 476cbc5c71 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards 4059a1665f 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] discards 04a271ffb1 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards 9798793bef 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] discards 012e47a97e 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] discards 90fd8f9b69 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] discards dd73cbec14 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] discards c120af586d 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] discards 48e100272a 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] discards 673fd1e1ee 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] discards 24034ee08e 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] discards 1d1d3a2896 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 7b110092f9 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] discards 78743bd49a 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] discards c747e8d676 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] discards 9c0fc92e11 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] discards de5170bfab 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards 4474393fea 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards 5d65cb444a 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 552316cd54 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] discards 6baf38673a 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] discards 17b6138486 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards 54f705bb98 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] discards 470c175582 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards 2bfd0f132d 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards 756472befa 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards 089afc7314 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards 279e1fd86e 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 2816bfbfb5 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] discards d574fde7be 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards 638d2fdd2c 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards e8055ce355 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] discards 92cec42a24 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards 573af6c529 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards 58c87585b2 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards 99c3b893db 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 12ac42bd49 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 3ad2d884d1 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards f12413cd19 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] discards c199916e09 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new 769d14c667 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new 43d3d85b52 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] new 5daa977086 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 9ace95be01 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new d56e4a54a2 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 6bff4b0bb4 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new c1e7092a48 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new bc9f3deb96 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new 453acd8375 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] new a2db62ba4e 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new e888471c0f 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new ef0f6ad494 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] new 0c356b2641 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 8bbdfc2eec 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new 73cff71471 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new f832ec949c 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new adaa8d7214 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new 1747dcc1b7 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] new 3baff1ac39 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new 92ffc99b3a 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] new 5ffb263078 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] new 1068fbc38d 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new 0a57180077 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new 52bae7b828 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new aa81b289b7 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] new 44df017d43 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] new 564e92cc0f 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] new 1eeb4621e2 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] new 2fa9d3d33c 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 0da53ef74f 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] new 6d409ab4c5 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] new 36ca4dc238 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] new 040d137592 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] new 6ebeace7a9 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] new 21bfe3f137 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] new 6ef402ec0a 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] new eb97b0790c 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] new 3e9cfe0603 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new 95bf489b80 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] new f48784fbac 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new 91601c4fd9 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 3b8c7b90fe 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 40d1eeb82c 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new f26fea9ac8 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new c7988f7365 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new a13b33795f 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 68becb9b01 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 7e84b8fae6 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new a3c5c07e2c 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 57693c8562 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new b775edca73 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new ce6e2876ef 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new d5ab65087b 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 0b2b34aa7d 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 597397faeb 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 372cdfecf7 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 3d26cf621c 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 55bafa087f 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 2332086def 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 271f099dff 212: force: #27: : Failure after baseline build: no new commits new 9c2cac765b 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new f2380d92e3 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g1 [...] new a68f4ee3b4 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g1 [...] new 0c37abf0ec 216: force: #43: : Failure after baseline build: no new commits new 130e77ae7e 217: force: #45: 1: Success after linux: 1 commits new f8098364c4 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g3 [...] new b617e9b159 219: force: #50: 1: Failure after linux: 2520 commits new 481e8cd294 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02ddb [...] new 43c97628a3 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g6 [...] new ab8de2012c 222: force: #60: 1: Success after gdb: 16 commits new 07f232000a 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g2 [...] new 3a7936d10c 224: force: #65: 1: Success after gdb: 50 commits new 840b367e43 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g4 [...] new 95d464ba7a 226: force: #70: 1: Success after baseline build: no new commits new f5ca058af8 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 9cd1374fdd 228: force: #74: 1: Success after gdb: 53 commits new e3e9fc8b30 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g4 [...] new a56ef7a854 230: onsuccess: #78: 1: Success after gdb: 2 commits new 5010d41529 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits new e9b8abe42a 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new fb238b6d4b 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 7991046c6e 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new f704a6c0e0 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new 3ddeb5a43e 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 22 [...] new 360d9612d5 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits new 854b6c99a6 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new a6e72f5a00 239: force: #106: 1: [TCWG CI] Success after baseline build: [...] new 04cb169312 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/gc [...] new 95c0eacaf1 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/gc [...] new cdc272969b 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits new 3b8d6f4e65 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/gc [...] new df919a8e10 244: onsuccess: #112: 1: [TCWG CI] Success after binutils/gc [...] new eb2252778a 245: onsuccess: #117: 1: [TCWG CI] Success after gcc: 16 commits new 07bb5bf151 246: onsuccess: #118: 1: [TCWG CI] Success after glibc: 7 commits new 1e04421c12 247: force: #120: 1: [TCWG CI] Success after baseline build: [...] new a6cfe7425f 248: onsuccess: #121: 1: [TCWG CI] Success after binutils/gc [...] new c94642aaab 249: onsuccess: #127: 1: [TCWG CI] Success after gcc: 98 commits new 4e8470f4ea 250: onsuccess: #128: 1: [TCWG CI] Success after glibc: 2 commits new 23704d3435 251: onsuccess: #129: 1: [TCWG CI] Success after linux: 121 commits new 1a1d9d3469 252: force: #130: 1: [TCWG CI] Success after gdb: 15 commits new 10628921d6 253: force: #131: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new d1cb4adf5d 254: onsuccess: #132: 1: [TCWG CI] 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 (0bb077feff) \ 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 2044 -> 2020 bytes 02-prepare_abe/console.log.xz | Bin 2532 -> 2532 bytes 03-build_abe-binutils/console.log.xz | Bin 49428 -> 49664 bytes 04-build_abe-gcc/console.log.xz | Bin 235124 -> 235996 bytes 06-build_abe-linux/console.log.xz | Bin 8652 -> 8624 bytes 07-build_abe-glibc/console.log.xz | Bin 232872 -> 232772 bytes 08-build_abe-gdb/console.log.xz | Bin 46792 -> 46512 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3804 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4476 -> 4448 bytes 11-check_regression/console.log.xz | Bin 3768 -> 4032 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 10 -- 11-check_regression/results.compare | 13 +- 11-check_regression/results.compare2 | 119 ++++++++++++++++- 11-check_regression/results.regressions | 18 --- 11-check_regression/trigger-bisect | 3 - 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 46 +++---- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- jenkins/notify.sh | 3 - mail/changes-list-long.txt | 7 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 16 +-- mail/short-diag.txt | 2 +- manifest.sh | 20 +-- results | 18 --- sumfiles/gdb.log.0.xz | Bin 2888792 -> 2890712 bytes sumfiles/gdb.log.1.xz | Bin 143280 -> 138404 bytes sumfiles/gdb.log.2.xz | Bin 19600 -> 15212 bytes sumfiles/gdb.log.3.xz | Bin 9920 -> 10072 bytes sumfiles/gdb.log.4.xz | Bin 10076 -> 9764 bytes sumfiles/gdb.log.5.xz | Bin 9972 -> 9972 bytes sumfiles/gdb.log.6.xz | Bin 0 -> 10068 bytes sumfiles/gdb.log.7.xz | Bin 0 -> 10136 bytes sumfiles/gdb.log.8.xz | Bin 0 -> 10120 bytes sumfiles/gdb.log.9.xz | Bin 0 -> 10012 bytes sumfiles/gdb.sum | 43 ++----- sumfiles/gdb.sum.0 | 53 ++------ sumfiles/gdb.sum.1 | 199 +++------------------------- sumfiles/gdb.sum.2 | 221 ++++++-------------------------- sumfiles/gdb.sum.3 | 43 +++---- sumfiles/gdb.sum.4 | 27 ++-- sumfiles/gdb.sum.5 | 97 ++++++++------ sumfiles/{gdb.sum.4 => gdb.sum.6} | 21 ++- sumfiles/{gdb.sum.5 => gdb.sum.7} | 34 +++-- sumfiles/{gdb.sum.3 => gdb.sum.8} | 48 +++---- sumfiles/{gdb.sum.4 => gdb.sum.9} | 14 +- 48 files changed, 410 insertions(+), 672 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 100755 jenkins/notify.sh 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.6} (99%) copy sumfiles/{gdb.sum.5 => gdb.sum.7} (99%) copy sumfiles/{gdb.sum.3 => gdb.sum.8} (99%) copy sumfiles/{gdb.sum.4 => gdb.sum.9} (99%)