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 1280dad8b0f5 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits discards 1f21e82ec164 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/ [...] discards c0b6a3c5db92 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/ [...] discards 15ad98b97e5d 239: force: #106: 1: [TCWG CI] Success after baseline buil [...] discards d9a3a1613eb5 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branch [...] discards 32dc3ce5e9aa 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits discards 8b472643ce96 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: [...] discards 891e26e1eb68 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/g [...] discards eb475f03ec03 234: force: #94: 1: [TCWG CI] Success after baseline build [...] discards 6eb992959f48 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards 399bfcc9639f 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards bb75227f40e7 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits discards bb734003ea02 230: onsuccess: #78: 1: Success after gdb: 2 commits discards 2fc4f364a248 229: force: #77: 1: Failure after gdb-13-branchpoint-1594- [...] discards b47c1525b2b6 228: force: #74: 1: Success after gdb: 53 commits discards b1e4d68c22d2 227: onsuccess: #72: 1: Success after binutils/gcc/linux/g [...] discards 3ab7f6009f98 226: force: #70: 1: Success after baseline build: no new commits discards 347c05a160de 225: force: #68: 1: Failure after gdb-13-branchpoint-1540- [...] discards 8481dc218b07 224: force: #65: 1: Success after gdb: 50 commits discards f0ee0afbfb6a 223: force: #63: 1: Failure after gdb-13-branchpoint-1489- [...] discards a6a890df7546 222: force: #60: 1: Success after gdb: 16 commits discards 68deca96dcf6 221: force: #53: 1: Success after gdb-13-branchpoint-1472- [...] discards bda358b9c267 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02d [...] discards 2df93864cdeb 219: force: #50: 1: Failure after linux: 2520 commits discards 79450f423f80 218: force: #48: 1: Success after gdb-13-branchpoint-1471- [...] discards 296407dbb7c7 217: force: #45: 1: Success after linux: 1 commits discards 3549cc53f5d0 216: force: #43: : Failure after baseline build: no new commits discards afd894fbc026 215: force: #41: 1: Failure after gdb-13-branchpoint-1470- [...] discards 78b75526eb3a 214: force: #39: 1: Failure after gdb-13-branchpoint-1470- [...] discards 42eb435ad131 213: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards 4e41956df92a 212: force: #27: : Failure after baseline build: no new commits discards b51510cb9120 211: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards 081705736b6f 210: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 33c6083022b0 209: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 65b52c2075fc 208: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 7981b76d5abf 207: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards c625022c47c9 206: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards bfa26872f9d0 205: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards a66734b5c7f3 204: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards 5419419fff2b 203: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards 474eab177371 202: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 68a882c19b77 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 1c070d34c8f7 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 4959762fbc4a 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards d3bf6b9dde6e 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards 4d998bba4e5f 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 6a02496c692a 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards e4dccbb18bcd 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards ff97de47d642 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards 3366c3580327 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 0693265ef463 192: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] discards 3e598cf0e6de 191: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] discards 23ce7b956b8b 190: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] discards 52368f580a8c 189: onsuccess: #683: 1: Success after binutils/gcc/linux/ [...] discards 6629bc86a068 188: onsuccess: #682: 1: Success after binutils/gcc/linux/ [...] discards 03225de8e35c 187: onsuccess: #681: 1: Success after binutils/gcc/linux/ [...] discards 94d6bff4c36f 186: onsuccess: #680: 1: Success after binutils/gcc/linux/ [...] discards 59f51417ec1b 185: onsuccess: #679: 1: Success after binutils/gcc/linux/ [...] discards 6e5c5ced3ccd 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/ [...] discards c81ab7b2bfb4 183: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] discards f17e6fbcb22a 182: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] discards 73fe50a22d52 181: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] discards e9df17e45040 180: onsuccess: #674: 1: Success after binutils/gcc/linux/ [...] discards decc90f652f4 179: onsuccess: #673: 1: Success after binutils/gcc/linux/ [...] discards d2c579eb9478 178: onsuccess: #672: 1: Success after binutils/gcc/linux/ [...] discards 6af8eb12434d 177: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] discards 22fc13cbcd9b 176: onsuccess: #670: 1: Success after binutils/gcc/linux/ [...] discards fd93f404413c 175: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] discards 02d7733836be 174: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] discards 2e79bd935211 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 1 [...] discards 6633c7b2f3cb 172: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] discards 8a03b30a91d3 171: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] discards 2033a2c22071 170: onsuccess: #664: 1: Success after binutils/gcc/linux/ [...] discards cde3356298ac 169: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] discards 6e0d12498903 168: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] discards fddd08269c8a 167: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] discards 2bcf767f34e0 166: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] discards 6ab68ea966dc 165: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] discards f4e66f5a1c5f 164: onsuccess: #658: 1: Success after binutils/gcc/linux/ [...] discards 0cbbad04c3ec 163: onsuccess: #657: 1: Success after binutils/gcc/linux/ [...] discards be3e33879036 162: onsuccess: #656: 1: Success after binutils/gcc/linux/ [...] discards 5a28328d2ce3 161: onsuccess: #655: 1: Success after binutils/gcc/linux/ [...] discards 23789f793eef 160: onsuccess: #654: 1: Success after binutils/gcc/linux/ [...] discards 9ce0744ece69 159: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] discards 0cff5be1088a 158: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] discards 966077bd9fc4 157: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] discards 27eb61fbb81f 156: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] discards ac10d04e73c1 155: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] discards 034373e80212 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/ [...] discards 2683d254c76a 153: onsuccess: #647: 1: Success after binutils/gcc/linux/ [...] discards 7e781695e32d 152: onsuccess: #645: 1: Success after binutils/gcc/linux/ [...] discards c34780c10be8 151: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] discards c2dddb7a09ca 150: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] discards dd823e63328c 149: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] discards 035fd196566a 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 [...] discards 7209c32b8ce5 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 1 [...] discards ceb0f499e142 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 3 [...] discards b214b58dc613 145: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] discards 03ee6cadccd0 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 4 [...] discards 6101b8892181 143: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] discards f9dc01e562ed 142: onsuccess: #634: 1: Success after binutils/gcc/linux/ [...] new 68673f5f66c0 142: onsuccess: #634: 1: Success after binutils/gcc/linux/ [...] new 1a1a763979ca 143: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] new 1c7ae3c65ca6 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 4 [...] new e944abbcaa94 145: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] new c9413e4c1ad1 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 3 [...] new 54c5bc4ce803 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 1 [...] new 0a3a53164307 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 [...] new 5c7d8aeba162 149: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] new 1354f980f69e 150: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] new d6de9d536b1f 151: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] new 883109912c32 152: onsuccess: #645: 1: Success after binutils/gcc/linux/ [...] new d7138f146639 153: onsuccess: #647: 1: Success after binutils/gcc/linux/ [...] new 75174a8f5778 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/ [...] new ed9f9431ff9b 155: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] new 0c0d6151473c 156: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] new 21a41b9f7d4d 157: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] new c99c50523e16 158: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] new d52411e6b202 159: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] new b4c6ee128c60 160: onsuccess: #654: 1: Success after binutils/gcc/linux/ [...] new 2dfd4035d252 161: onsuccess: #655: 1: Success after binutils/gcc/linux/ [...] new 88ee0cd76724 162: onsuccess: #656: 1: Success after binutils/gcc/linux/ [...] new 4a4ac52745c8 163: onsuccess: #657: 1: Success after binutils/gcc/linux/ [...] new 6cd269ea950f 164: onsuccess: #658: 1: Success after binutils/gcc/linux/ [...] new 76db1a0584df 165: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] new 13f1ec7fcca4 166: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] new 2ecacd9beaba 167: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] new 9541a2a6df5d 168: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] new ee01939eb40a 169: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] new 05eff82d96b0 170: onsuccess: #664: 1: Success after binutils/gcc/linux/ [...] new e3f7de7551e5 171: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] new 984685fa6ea8 172: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] new e274e5aad057 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 1 [...] new e31b6c1ccb0f 174: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] new 26c092270b89 175: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] new 78dc5bdf80ac 176: onsuccess: #670: 1: Success after binutils/gcc/linux/ [...] new 8a0753e72dad 177: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] new 9d2ea7567bc4 178: onsuccess: #672: 1: Success after binutils/gcc/linux/ [...] new 222efcae78c8 179: onsuccess: #673: 1: Success after binutils/gcc/linux/ [...] new 4ee9b625065f 180: onsuccess: #674: 1: Success after binutils/gcc/linux/ [...] new da80978fd126 181: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] new fe7945ca1d1b 182: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] new 281230787283 183: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] new 21c01828f2e8 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/ [...] new a46d354c2c8d 185: onsuccess: #679: 1: Success after binutils/gcc/linux/ [...] new 2d1ffd769322 186: onsuccess: #680: 1: Success after binutils/gcc/linux/ [...] new bfd9a604a192 187: onsuccess: #681: 1: Success after binutils/gcc/linux/ [...] new 7443df49793f 188: onsuccess: #682: 1: Success after binutils/gcc/linux/ [...] new 6954e11857fe 189: onsuccess: #683: 1: Success after binutils/gcc/linux/ [...] new 952ed9b61986 190: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] new e53d24e12720 191: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] new 00657b41f59a 192: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] new 8497efeb35e3 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new 121254983239 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new be7cb960e624 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new c93e09c78722 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new a7f5f360b980 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 55843e279c0d 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new a52b1f83a8b6 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new 2a8382567de6 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new f26cc9c136e4 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 4ca2699c7264 202: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new db6d2a820956 203: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new 47f7c474794a 204: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new 8a687712876f 205: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new bba4cca6678e 206: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new 6aa4dc6134b7 207: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 222c55d485ef 208: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 954f6b069f69 209: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 9b2f3e3fa9e6 210: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new becb70efee1a 211: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new 063369527227 212: force: #27: : Failure after baseline build: no new commits new cb3bae422627 213: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new fcae2a9ae015 214: force: #39: 1: Failure after gdb-13-branchpoint-1470- [...] new fbc4bd4f4d47 215: force: #41: 1: Failure after gdb-13-branchpoint-1470- [...] new 3006a12c3ad2 216: force: #43: : Failure after baseline build: no new commits new a52caa7c3241 217: force: #45: 1: Success after linux: 1 commits new 6d70b2da0e58 218: force: #48: 1: Success after gdb-13-branchpoint-1471- [...] new 3981fe51cdf9 219: force: #50: 1: Failure after linux: 2520 commits new abd558397f72 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02d [...] new 2b2c8dd88237 221: force: #53: 1: Success after gdb-13-branchpoint-1472- [...] new daf6b8713d89 222: force: #60: 1: Success after gdb: 16 commits new 2d476e14701f 223: force: #63: 1: Failure after gdb-13-branchpoint-1489- [...] new 45a22d017d9d 224: force: #65: 1: Success after gdb: 50 commits new b510e12a88a2 225: force: #68: 1: Failure after gdb-13-branchpoint-1540- [...] new e75152999016 226: force: #70: 1: Success after baseline build: no new commits new 01508c3ee686 227: onsuccess: #72: 1: Success after binutils/gcc/linux/g [...] new cc275cb43f2b 228: force: #74: 1: Success after gdb: 53 commits new a45a30aaaeeb 229: force: #77: 1: Failure after gdb-13-branchpoint-1594- [...] new ee4d46dbcc0c 230: onsuccess: #78: 1: Success after gdb: 2 commits new 136f2e8464f1 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits new 61fcbdf6aa7b 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchp [...] new eea33ee66d72 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchp [...] new e971bec7af40 234: force: #94: 1: [TCWG CI] Success after baseline build [...] new de500de892c0 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/g [...] new 76abcc47ee9f 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: [...] new da431698c4f5 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits new 9518d8a23819 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branch [...] new 03b589d41044 239: force: #106: 1: [TCWG CI] Success after baseline buil [...] new 2c3a538fcfab 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/ [...] new 9ed005b92190 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/ [...] new 38755fa998e4 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits new 350d5ed36b94 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/ [...]
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 (1280dad8b0f5) \ 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 -> 2044 bytes 02-prepare_abe/console.log.xz | Bin 2492 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 49180 -> 49332 bytes 04-build_abe-gcc/console.log.xz | Bin 238512 -> 234752 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8712 -> 8188 bytes 07-build_abe-glibc/console.log.xz | Bin 233620 -> 232424 bytes 08-build_abe-gdb/console.log.xz | Bin 46396 -> 47016 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3760 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4356 -> 4156 bytes 11-check_regression/console.log.xz | Bin 4420 -> 6168 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 180 ++- 12-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 34 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 22 +- manifest.sh | 34 +- sumfiles/gdb.log.0.xz | Bin 2946564 -> 2929368 bytes sumfiles/gdb.log.1.xz | Bin 138656 -> 138736 bytes sumfiles/gdb.log.2.xz | Bin 11832 -> 16476 bytes sumfiles/gdb.log.3.xz | Bin 10088 -> 0 bytes sumfiles/gdb.log.4.xz | Bin 10136 -> 0 bytes sumfiles/gdb.log.5.xz | Bin 10240 -> 0 bytes sumfiles/gdb.log.6.xz | Bin 10300 -> 0 bytes sumfiles/gdb.log.7.xz | Bin 9996 -> 0 bytes sumfiles/gdb.log.8.xz | Bin 10076 -> 0 bytes sumfiles/gdb.sum | 116 +- sumfiles/gdb.sum.0 | 133 +- sumfiles/gdb.sum.1 | 229 ++-- sumfiles/gdb.sum.2 | 211 +++- sumfiles/gdb.sum.3 | 2178 -------------------------------- sumfiles/gdb.sum.4 | 2176 -------------------------------- sumfiles/gdb.sum.5 | 2215 --------------------------------- sumfiles/gdb.sum.6 | 2185 -------------------------------- sumfiles/gdb.sum.7 | 2153 -------------------------------- sumfiles/gdb.sum.8 | 2159 -------------------------------- 43 files changed, 627 insertions(+), 13456 deletions(-) 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.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