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 4ac76a8a285 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards 4ebff790349 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits discards edc41631d7b 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 2 [...] discards 3868d24c80e 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gc [...] discards 7f56a794703 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 8374419d6cf 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards 96baa039da6 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards ba338986c2c 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits discards 8552a5fa6be 230: onsuccess: #78: 1: Success after gdb: 2 commits discards dba8b56d211 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g [...] discards cd751a48da1 228: force: #74: 1: Success after gdb: 53 commits discards 6c199b07fa3 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] discards e2fa9d1c384 226: force: #70: 1: Success after baseline build: no new commits discards 6e4c66d3496 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] discards ed4212b5ad8 224: force: #65: 1: Success after gdb: 50 commits discards 2634824da52 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] discards 6fe9d68cb11 222: force: #60: 1: Success after gdb: 16 commits discards 402c26c5cfd 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] discards 7087a777aab 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] discards 3f6faa8d123 219: force: #50: 1: Failure after linux: 2520 commits discards f2cc3cf8c0a 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] discards 0f300cbccd8 217: force: #45: 1: Success after linux: 1 commits discards 596c1f4ec50 216: force: #43: : Failure after baseline build: no new commits discards ea118d9d811 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] discards d83c419fbe9 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 57f14a83cb5 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards c072d1a5973 212: force: #27: : Failure after baseline build: no new commits discards 2d37c541336 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 3bd9ee07447 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 755b435b7ff 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 4d7691751de 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 0f81e29622d 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 8b9b0e05cd0 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 3b1ce863827 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 7c8d9741d0f 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 355c02e40ad 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards c5ca8bdffe2 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 000f0908470 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards d192285a323 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards fe882fc3760 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 049226993e9 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards e2a8255d74e 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 85b741e3b1e 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 6358c09f7a9 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 8f47f3fc394 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards a72244cadf2 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 29d355f6ba3 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards b6295f053df 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 20bc8f8ef61 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 95542fd7afe 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards 8f4797fc24e 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards 5b28c22819c 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 46809b4e908 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards fabe02d570f 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards 674270d0a31 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 8f66a2d32ab 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards bd04978bcfb 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 0991fcfb824 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards c21c9dd21f2 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards 73d0d510c70 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards b5daa111093 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 9c8d53388ab 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 23a47dde4ce 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards e58024cfb6a 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards d27cd67f270 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 63e89c251b7 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 3ff08195f38 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards b0bdd6b6dcf 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards c06571c967a 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards ff33acfa40d 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards a34c3c7e1f1 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards fb3699200b8 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 49cc307dd9f 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards f4b17173e70 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards cd4d13507ca 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards a9e43fe6e57 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 3761d0d22f6 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 56ddb5503b5 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 1734ff31a7b 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 004bf4baaca 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 46fb1bd1a7a 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards ae386ef70da 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards ba45d14c7d2 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards a5e08a4a8eb 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 6aa31e632d9 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards a739df0a421 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 1e2cfd1ab20 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 6ecf3078296 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 9cd51d853a4 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 0238120bbc7 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 0f78cabcaf3 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 1c5b63cc087 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards 673e41ac132 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards 952651197d4 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards f4e14d21611 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards de297f60384 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards d8e28740133 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 3609aafdfc4 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 362cd845ca5 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards d92b54805f2 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 816b793d2ef 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 20d0e29afdc 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 9c102dba47c 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 991f70c4cae 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 05e705b0e85 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 340e46a15e2 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new cbe57da4473 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new ceb97f99824 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new 8cd20ee1584 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 3c09f69953a 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 94a6521008a 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new 470b9ec999f 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 0fef25718c1 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new d17cab436e1 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 7a885ffddb1 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 01bc8c4ecc2 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new 5de30ca361e 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 4c20c668219 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new 4b71fe2ba39 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 116b71a1fb5 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 672c36f7030 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new e7746e57d8a 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new cdc72024e82 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 997558a957d 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new a670d6b2738 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new f3c55225023 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new c4d76783bab 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 81741fc34f3 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new d3427174108 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new cddb37622ae 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 54d4b227aff 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new dbed5ebd8cf 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new bd964fa63d1 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 0fdff9decae 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new 503fb180f70 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 5242a978e20 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new eade72232b9 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new 482d5ff020f 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new ab6f3fdf554 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 0c388df119e 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 2bed97b67a8 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 6abc623b512 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 7c18f866b16 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 4555ae3a28f 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new 734d69f1624 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new c42a05c581c 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 8b81ddb9e2e 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 8ec0628eea9 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new bc826aa4af9 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 5697dafc376 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new e88b8579be0 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new 52fb5c72f03 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new 82df5fe862b 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new dc6d4e1e94f 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 90db83998bb 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 6d051733dc3 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new eb666fd30a7 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 19f7def1c5c 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 84e0fd65fa2 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 2306fd7da31 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new b0bf2fe5f3d 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new d5d0025aeaf 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new d6bf9c275f7 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 6f6b20470fa 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 93590810eb8 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new a8d1cce6d35 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 4acb450ffba 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 834f4a0e615 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new d98b644023e 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new a8912191322 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 9bfcfd1bb9b 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 5c65bc8db32 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 53ac8092616 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 1fc7ddedbe2 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new f353086c431 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 100eea69d37 212: force: #27: : Failure after baseline build: no new commits new 3bbca692042 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new e66c191253b 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] new be993ca1b4e 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] new 7572bbfccc5 216: force: #43: : Failure after baseline build: no new commits new c2c0a476f2a 217: force: #45: 1: Success after linux: 1 commits new abbac74f23d 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] new 95ea9bae8af 219: force: #50: 1: Failure after linux: 2520 commits new 172b0740767 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] new 60346fa4dc7 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] new 5768d3ecf94 222: force: #60: 1: Success after gdb: 16 commits new b7cbf7f89df 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] new 4748967759a 224: force: #65: 1: Success after gdb: 50 commits new 25e2073685d 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] new 90a9db0cd72 226: force: #70: 1: Success after baseline build: no new commits new c8496642523 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] new 43d3544f680 228: force: #74: 1: Success after gdb: 53 commits new 41d5826a9bb 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g [...] new 7afcf500751 230: onsuccess: #78: 1: Success after gdb: 2 commits new 32135e15af0 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits new 511b76ef102 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new 6bb4e1f2bd7 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new c22a07fe7a8 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new 83e33a205d0 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gc [...] new 295f860a08d 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 2 [...] new 6c5155b9aca 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits new a91f42a7caa 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branchp [...] new 8c5fcdf3d77 239: force: #106: 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 (4ac76a8a285) \ 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 2072 -> 2268 bytes 02-prepare_abe/console.log.xz | Bin 2532 -> 2512 bytes 03-build_abe-binutils/console.log.xz | Bin 49112 -> 48824 bytes 04-build_abe-gcc/console.log.xz | Bin 236180 -> 234820 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8668 -> 8688 bytes 07-build_abe-glibc/console.log.xz | Bin 232440 -> 234652 bytes 08-build_abe-gdb/console.log.xz | Bin 47156 -> 47836 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3772 -> 3788 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4668 -> 4616 bytes 11-check_regression/console.log.xz | Bin 3936 -> 2808 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 10 - 11-check_regression/results.compare | 24 +- 11-check_regression/results.regressions | 32 - 11-check_regression/trigger-bisect | 3 - 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 68 +- dashboard/dashboard-generate.sh | 2 +- jenkins/notify.sh | 3 - mail/changes-list-long.txt | 5 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 16 +- mail/short-diag.txt | 2 +- manifest.sh | 15 +- results | 32 - sumfiles/gdb.log.0.xz | Bin 2966876 -> 2882236 bytes sumfiles/gdb.log.1.xz | Bin 143404 -> 143620 bytes sumfiles/gdb.log.10.xz | Bin 10292 -> 9928 bytes sumfiles/gdb.log.11.xz | Bin 10436 -> 0 bytes sumfiles/gdb.log.12.xz | Bin 10120 -> 0 bytes sumfiles/gdb.log.2.xz | Bin 21380 -> 15536 bytes sumfiles/gdb.log.3.xz | Bin 14948 -> 10336 bytes sumfiles/gdb.log.4.xz | Bin 14900 -> 10284 bytes sumfiles/gdb.log.5.xz | Bin 10024 -> 10348 bytes sumfiles/gdb.log.6.xz | Bin 10352 -> 10152 bytes sumfiles/gdb.log.7.xz | Bin 10288 -> 10392 bytes sumfiles/gdb.log.8.xz | Bin 10240 -> 10072 bytes sumfiles/gdb.log.9.xz | Bin 10460 -> 10300 bytes sumfiles/gdb.sum | 1694 +++++++++++++---------- sumfiles/gdb.sum.0 | 1708 ++++++++++++++---------- sumfiles/gdb.sum.1 | 786 +++++------ sumfiles/gdb.sum.10 | 30 +- sumfiles/gdb.sum.11 | 2211 ------------------------------- sumfiles/gdb.sum.12 | 2166 ------------------------------ sumfiles/gdb.sum.2 | 662 +++------ sumfiles/gdb.sum.3 | 238 +--- sumfiles/gdb.sum.4 | 204 +-- sumfiles/gdb.sum.5 | 32 +- sumfiles/gdb.sum.6 | 34 +- sumfiles/gdb.sum.7 | 49 +- sumfiles/gdb.sum.8 | 78 +- sumfiles/gdb.sum.9 | 73 +- 53 files changed, 2784 insertions(+), 7396 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.11.xz delete mode 100644 sumfiles/gdb.log.12.xz delete mode 100644 sumfiles/gdb.sum.11 delete mode 100644 sumfiles/gdb.sum.12