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 0df1857a44e 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards 1f59bae7d86 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards 4c7c9df8bf7 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits discards d713880761c 230: onsuccess: #78: 1: Success after gdb: 2 commits discards f793b2c5e4c 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g [...] discards 25f2aa5928b 228: force: #74: 1: Success after gdb: 53 commits discards b4dbcc47e41 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] discards 938dc4e39b1 226: force: #70: 1: Success after baseline build: no new commits discards 6b9c0137473 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] discards e04155de617 224: force: #65: 1: Success after gdb: 50 commits discards 2e388c2a8ce 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] discards b8e0bb1a369 222: force: #60: 1: Success after gdb: 16 commits discards d404028960d 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] discards cd072e72cbd 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] discards 559bf61eda2 219: force: #50: 1: Failure after linux: 2520 commits discards 3c14c0343af 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] discards 82d0560a3cd 217: force: #45: 1: Success after linux: 1 commits discards b08e2a03538 216: force: #43: : Failure after baseline build: no new commits discards 442b1cea363 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 5eb9f4d689c 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 5e47571d5e8 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 8202a50609a 212: force: #27: : Failure after baseline build: no new commits discards 5fc64186f7a 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards bfdf6bb346a 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 478ec287f79 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards ef5c0e2f095 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards a0bd31c1f7f 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 20282231116 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 567c5d2ec36 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards eaf524a9e99 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 61733e0aca1 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 216f97e4405 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards cea76038df5 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards e9533bbb42d 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 0ae4f67d40e 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards d93635b9023 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 1210b5ecfd8 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 0ace4a3afb2 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 2d937344323 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards e20907c89e2 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards f68fb6b235e 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards e5a55a91395 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards f74588c107f 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 1ebeea903af 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 8ff05d14532 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards 57b86d91d3d 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards deeda3f58e3 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 034fe6b225b 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards 5be6cf5a1b6 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards f8a94f49870 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 8bf35d81918 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards fda77d9d332 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards e8994b7da60 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 0de2d589cdd 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards f8f353fc30a 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards 833ced10b03 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards dc207eb0596 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards c38a6986d24 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards c1b38785f56 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards f68cb3e4d41 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 91342660a86 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 242c628e9a5 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards d844738b22d 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 5ddb1b7d472 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards 0f9c2df81a1 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards d1dd2939f62 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards a71548a6cb0 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 76dd41be068 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 391018708dd 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards d2a9abface5 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards c7c5172672d 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 1e069454e24 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards b6c5fe061ae 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards dc770e645d6 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 9c21f7c2736 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 6b3a19d8417 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 6636045d96c 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards fc79e8e35e6 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 41c3bcd1f3f 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 98f35b7de5b 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards 3bcac4d7e69 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards d50842bc1bc 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards b90819edb22 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 11f5ed77397 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 43a42468a48 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 2a90b1b7d0e 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards be785852915 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards c05c1920802 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards bb843ae2d31 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards ad48859c97d 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards 3244b3d14b9 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 7c5fc07bbac 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 43ce0aaa6d4 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 9b3975deb80 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 39a7012bb9b 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 985c272beef 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 477166a4d71 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards 36e3526965d 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 8e143242233 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards e2d8b00dcb1 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 2b6953c1da7 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new 51a4990d8f7 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new e846de3ee8d 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 087ebac7905 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new c8c9e505a6a 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 6af750d2e05 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 9a4d4de68ad 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new ffd48235b38 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 5d576cf6153 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new baaa5b58652 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new b86758ebb1f 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 3ee014b2938 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new a7ead3ac2c8 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new fc0cce9aa56 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new fcb9983fdbd 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 0bbf062cb14 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new a05be196643 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new e083bb11147 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 4209329e7c8 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 469a1f13c37 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 0daa1de141b 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new fe5a5d2e652 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 35f949f5381 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new f372a84e0ed 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new f88ee05776c 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 07f20c70460 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 58d31635af7 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 73ebefd8638 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 271869ee6f8 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new af2e4355dda 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 841ab09085e 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new fea0cd4643b 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 30cf0297f8b 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new 435984b53b5 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 897b8369acc 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 3be99e99c14 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 638068883ce 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 013df36a749 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new f908a51a903 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new 84281417fd7 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 0dce0d47dde 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new c02dcd6f5e6 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new c71f2e24fac 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 43a764e70c3 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 6d7511dff68 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 3d243f166c5 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 09c27630ffa 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 6acefcd7e6c 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 58bdcd09acf 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new 904f86ab0a5 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 25ab6baf076 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 07a87d7d0a8 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 952eceef36e 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new 5909aae0f20 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new ec3471af239 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new 244aefd4297 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new 0a802b5267c 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new ac5f6c9bbc3 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 9b6e96a637b 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new e09a9b1b897 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 1d7d17b7322 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new e0a92c36669 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 9c0dd9428fe 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 679ab1ea81a 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 2d30c0bfeff 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new f7931cbb25e 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new ba93010fad8 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 14b9f279e52 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 9d4e8c64ab5 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 58254dcaf9b 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 697524842ee 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 77a1794af98 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 2c215b8bf1e 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new e888a5238bc 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new ca899bf37b8 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 0acd00324dc 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new e2ff8e90007 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 26ca4a4580a 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new c7c44fa77ec 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new a25dd297a45 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 3ed856e9ea8 212: force: #27: : Failure after baseline build: no new commits new 23db9a84013 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 7e42503ec28 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] new 6a8cf6a8714 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] new d50cc8d4753 216: force: #43: : Failure after baseline build: no new commits new 5549baf7fc4 217: force: #45: 1: Success after linux: 1 commits new 15d4cd9e10a 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] new d865e59547a 219: force: #50: 1: Failure after linux: 2520 commits new 8770ec5fff9 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] new 16288d3ffa0 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] new 10f7b8fbe3c 222: force: #60: 1: Success after gdb: 16 commits new 43ba0597417 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] new 0d59d9e9417 224: force: #65: 1: Success after gdb: 50 commits new 088e6516926 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] new 1228697633b 226: force: #70: 1: Success after baseline build: no new commits new ed22e52f59a 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] new 0a8d3b6a5aa 228: force: #74: 1: Success after gdb: 53 commits new 4e741749d81 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g [...] new 3504180fae4 230: onsuccess: #78: 1: Success after gdb: 2 commits new 69bd9c8715d 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits new 22ff94ed266 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new 2b3a720a528 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new ceef47994d1 234: force: #94: 1: [TCWG CI] Success after baseline build: [...]

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 (0df1857a44e) \ 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 2112 -> 2272 bytes 02-prepare_abe/console.log.xz | Bin 2516 -> 2516 bytes 03-build_abe-binutils/console.log.xz | Bin 49400 -> 49304 bytes 04-build_abe-gcc/console.log.xz | Bin 234984 -> 235248 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8532 -> 8496 bytes 07-build_abe-glibc/console.log.xz | Bin 233288 -> 233448 bytes 08-build_abe-gdb/console.log.xz | Bin 46612 -> 47124 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3780 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4528 -> 4340 bytes 11-check_regression/console.log.xz | Bin 3876 -> 2440 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 6 - 11-check_regression/results.compare | 27 +- 11-check_regression/results.regressions | 28 - 11-check_regression/trigger-bisect | 3 - 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 52 +- dashboard/dashboard-generate.sh | 2 +- jenkins/notify.sh | 3 - mail/changes-list-long.txt | 5 +- mail/changes-list-short.txt | 2 +- mail/short-diag.txt | 2 +- manifest.sh | 11 +- results | 28 - sumfiles/gdb.log.0.xz | Bin 2906196 -> 2908432 bytes sumfiles/gdb.log.1.xz | Bin 143700 -> 143892 bytes sumfiles/gdb.log.10.xz | Bin 10308 -> 0 bytes sumfiles/gdb.log.11.xz | Bin 10236 -> 0 bytes sumfiles/gdb.log.2.xz | Bin 19888 -> 11384 bytes sumfiles/gdb.log.3.xz | Bin 15080 -> 6604 bytes sumfiles/gdb.log.4.xz | Bin 14716 -> 0 bytes sumfiles/gdb.log.5.xz | Bin 10120 -> 0 bytes sumfiles/gdb.log.6.xz | Bin 10076 -> 0 bytes sumfiles/gdb.log.7.xz | Bin 10284 -> 0 bytes sumfiles/gdb.log.8.xz | Bin 10220 -> 0 bytes sumfiles/gdb.log.9.xz | Bin 10400 -> 0 bytes sumfiles/gdb.sum | 26 +- sumfiles/gdb.sum.0 | 39 +- sumfiles/gdb.sum.1 | 291 ++-- sumfiles/gdb.sum.10 | 2185 ---------------------------- sumfiles/gdb.sum.11 | 2167 ---------------------------- sumfiles/gdb.sum.2 | 2156 +--------------------------- sumfiles/gdb.sum.3 | 2171 +--------------------------- sumfiles/gdb.sum.4 | 2343 ------------------------------- sumfiles/gdb.sum.5 | 2173 ---------------------------- sumfiles/gdb.sum.6 | 2168 ---------------------------- sumfiles/gdb.sum.7 | 2166 ---------------------------- sumfiles/gdb.sum.8 | 2152 ---------------------------- sumfiles/gdb.sum.9 | 2224 ----------------------------- 50 files changed, 258 insertions(+), 22173 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 delete mode 100644 sumfiles/gdb.log.10.xz delete mode 100644 sumfiles/gdb.log.11.xz delete mode 100644 sumfiles/gdb.log.4.xz delete mode 100644 sumfiles/gdb.log.5.xz delete mode 100644 sumfiles/gdb.log.6.xz delete mode 100644 sumfiles/gdb.log.7.xz delete mode 100644 sumfiles/gdb.log.8.xz delete mode 100644 sumfiles/gdb.log.9.xz delete mode 100644 sumfiles/gdb.sum.10 delete mode 100644 sumfiles/gdb.sum.11 delete mode 100644 sumfiles/gdb.sum.4 delete mode 100644 sumfiles/gdb.sum.5 delete mode 100644 sumfiles/gdb.sum.6 delete mode 100644 sumfiles/gdb.sum.7 delete mode 100644 sumfiles/gdb.sum.8 delete mode 100644 sumfiles/gdb.sum.9