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 9b2397a6d6c 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits discards 16db361a45b 230: onsuccess: #78: 1: Success after gdb: 2 commits discards 0e57dad3c95 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g [...] discards 9761e53dd16 228: force: #74: 1: Success after gdb: 53 commits discards e69e6f65cb0 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] discards f8236434d4b 226: force: #70: 1: Success after baseline build: no new commits discards 1154a01eff2 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] discards 82fdd8f79f4 224: force: #65: 1: Success after gdb: 50 commits discards 02526e9073e 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] discards ce3ece35f24 222: force: #60: 1: Success after gdb: 16 commits discards 60e4a7241e1 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] discards be618bd2fe5 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] discards cf023fa6a85 219: force: #50: 1: Failure after linux: 2520 commits discards 904c1e3d338 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] discards a61f753e4eb 217: force: #45: 1: Success after linux: 1 commits discards bd8f5853c26 216: force: #43: : Failure after baseline build: no new commits discards 388f8732d64 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 96f6086fca5 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 74cc5af8298 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards e823cd587a3 212: force: #27: : Failure after baseline build: no new commits discards e4b2322863a 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards c1806d2636c 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 7ae2b412f26 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards a220aa59cae 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 0758fb66e61 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 73a0460632c 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 61d6f7a239f 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 99694e135bc 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 90e855cf4cc 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards d1be582a639 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards c2b3dcf71c5 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 79e66421c9c 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards fb73f935f3e 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 48ac593bd25 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards b268b191408 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards e6ef9e7e656 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 1ac4622912d 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 9dce3e0bcae 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 2e687837379 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 0011c4506aa 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 062843d9248 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 1474590f3e6 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 5cfba8fde42 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards 27240afe69b 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards 59ee3771c62 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 46a54cf6bae 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards 6f19cf404f8 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards ba0575bf7fd 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 76c19a49f8a 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 6d82da5054c 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 23e5b0bf41b 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 4954ab7933f 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards 25f87b31cd5 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards 71df560a079 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 8cceff3798d 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards c3585fd67d9 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards b179ae05a44 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards b8a24010f0c 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards c6020674758 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 310852dca42 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 430bdc73101 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards fc4bfa199fd 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards 259250547cf 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards af42f0f736b 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 81dafb7c2b8 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 4c00846d12e 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 4e03864e5a0 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 394dc782270 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards 2f9816751a4 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 1a313b9ac35 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards adad544cfcb 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 3169b9e0086 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 21708fa791f 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 43d65d4fbc5 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 04466964537 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards beab48b1fcc 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 49b4b9f4273 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards ee0a843d5fd 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards 58e53bd1103 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 3693b4bcecf 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 6a2e3f44e1b 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards b32561f5bb5 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 05568d35dc6 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 978adba5937 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 302d74dafbc 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards 4f58fc99118 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards cc08142dd53 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 06091e8e9f4 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards b031020047b 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 47881f1d8e1 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 432507f5605 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 0c6a791220f 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards c8134c9ff79 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 356298aa850 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 7d8e9835a5a 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards 2bb6e503c32 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards d8fff820090 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards c355c247d96 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 325a4efa125 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards a6e4899e55a 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 21df92ea21d 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 6580d984d76 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 77275994b47 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 3e3abc507b4 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new 42a50708170 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 5c272fa575c 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 901fe343402 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new e3f93ce5393 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 28e8748a351 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 774fe7b4af0 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 55a01a87704 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new c70f13a8109 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 0ff48f9001c 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new fff0194bbd1 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 2f4781a4441 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new bbc831e16bc 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 15b657b7c93 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 938ae107bdf 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new 32f34a5171c 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 5ecbe6b0f83 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 32db60a7997 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 9388cfd43dc 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 77261ec2b69 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new a7f661cef69 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 64b0783c127 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new 41265fabc1e 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 53b86b26578 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new f38ab3941dd 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new a5000431b66 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 15ae8ad124d 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 92700f792cb 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 046b1994e6d 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 8173cb6a242 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 225f437f2df 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 6c5d4f0a874 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new dfa8d876bf9 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new ecc93bb2e82 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 6f852f84b66 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 6557abf9563 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 174597bbd01 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 9b48d43b410 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new d86fb056037 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 1e329ef04b5 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 6700e8a544c 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new 9e6cf6351a5 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 937848ce337 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 4140b1b770d 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 2da7b16a08f 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 17c8f10e4f9 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 13ab67fd95a 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 26313a60086 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new 602dadc8aab 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 76eab9a6cf6 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 778db42c17c 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 1f363c28f32 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new ddc7fe0f6d0 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 4d5dd9a9185 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new febc7a0966f 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new 60caf904e00 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new 5d6c732b7a1 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new a4648ba60b7 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new df9518e8d44 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new bc7d7f1d055 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new a19ff7cfa2c 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 4909a26d0c9 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 539d43fa958 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 4cad0455ff2 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new d9d29fcd8a0 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new a9502971f71 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new cb332d45fd8 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new eb845b39b2e 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 5dbbb89000f 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 358b224898c 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 1beea157dac 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 000cd533bdd 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 36e7e685124 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new efe02801fe9 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 930ba52c92e 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new c5f492054da 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new df01ccd4498 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 2972c792b33 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 64268be1bc0 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 46fc9bddbc1 212: force: #27: : Failure after baseline build: no new commits new 30455faa0b5 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new f2b3da8de13 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] new 5d56917a495 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] new d37e4c7f474 216: force: #43: : Failure after baseline build: no new commits new 2ad782bd95a 217: force: #45: 1: Success after linux: 1 commits new 7e7f65b56c3 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] new ae32327da9f 219: force: #50: 1: Failure after linux: 2520 commits new e32453f94cb 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] new 57e7a34ec00 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] new afcd278ea90 222: force: #60: 1: Success after gdb: 16 commits new 4f8546fad6f 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] new 814d8beeef0 224: force: #65: 1: Success after gdb: 50 commits new b47c522bc55 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] new 738f5dafe31 226: force: #70: 1: Success after baseline build: no new commits new 7f498dd2426 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] new 5a8c417a1ee 228: force: #74: 1: Success after gdb: 53 commits new 7f7c4367fb3 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g [...] new e25eb1d12e2 230: onsuccess: #78: 1: Success after gdb: 2 commits new ca18ce7724d 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits new d48e49aefae 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpo [...]

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 (9b2397a6d6c) \ 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 2008 -> 1968 bytes 02-prepare_abe/console.log.xz | Bin 2528 -> 2528 bytes 03-build_abe-binutils/console.log.xz | Bin 49220 -> 48976 bytes 04-build_abe-gcc/console.log.xz | Bin 234368 -> 234616 bytes 06-build_abe-linux/console.log.xz | Bin 8472 -> 8476 bytes 07-build_abe-glibc/console.log.xz | Bin 234128 -> 234328 bytes 08-build_abe-gdb/console.log.xz | Bin 48848 -> 47548 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3772 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4588 -> 4368 bytes 11-check_regression/console.log.xz | Bin 3636 -> 3920 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 11 +- 11-check_regression/results.compare | 17 + 11-check_regression/results.regressions | 17 + 11-check_regression/trigger-bisect | 4 +- 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 36 +- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- jenkins/notify.sh | 3 + mail/changes-list-long.txt | 11 +- mail/changes-list-short.txt | 2 +- manifest.sh | 12 +- results | 17 + sumfiles/gdb.log.0.xz | Bin 2887436 -> 2881008 bytes sumfiles/gdb.log.1.xz | Bin 187828 -> 143244 bytes sumfiles/gdb.log.10.xz | Bin 10312 -> 0 bytes sumfiles/gdb.log.2.xz | Bin 20256 -> 15568 bytes sumfiles/gdb.log.3.xz | Bin 14916 -> 0 bytes sumfiles/gdb.log.4.xz | Bin 14976 -> 0 bytes sumfiles/gdb.log.5.xz | Bin 14936 -> 0 bytes sumfiles/gdb.log.6.xz | Bin 10360 -> 0 bytes sumfiles/gdb.log.7.xz | Bin 10264 -> 0 bytes sumfiles/gdb.log.8.xz | Bin 10252 -> 0 bytes sumfiles/gdb.log.9.xz | Bin 10364 -> 0 bytes sumfiles/gdb.sum | 1948 ++++++- sumfiles/gdb.sum.0 | 1970 +++++++- sumfiles/gdb.sum.1 | 8408 +------------------------------ sumfiles/gdb.sum.10 | 2167 -------- sumfiles/gdb.sum.2 | 219 +- sumfiles/gdb.sum.3 | 2356 --------- sumfiles/gdb.sum.4 | 2344 --------- sumfiles/gdb.sum.5 | 2414 --------- sumfiles/gdb.sum.6 | 2187 -------- sumfiles/gdb.sum.7 | 2189 -------- sumfiles/gdb.sum.8 | 2166 -------- sumfiles/gdb.sum.9 | 2191 -------- 47 files changed, 3899 insertions(+), 26796 deletions(-) create mode 100644 11-check_regression/trigger-notify create mode 100755 jenkins/notify.sh delete mode 100644 sumfiles/gdb.log.10.xz delete mode 100644 sumfiles/gdb.log.3.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.3 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