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 1dd4e8ebd9 259: onsuccess: #143: 1: [TCWG CI] https://ci.linaro.org/job [...] discards 4863f237ef 258: onsuccess: #136: 1: [TCWG CI] Success after binutils/gc [...] discards c50a27fd11 257: onsuccess: #135: 1: [TCWG CI] Success after binutils/gc [...] discards cf63a7e60c 256: onsuccess: #134: 1: [TCWG CI] Success after binutils/gc [...] discards 75ce07f32e 255: force: #133: 1: [TCWG CI] Success after baseline build: [...] discards 1a1bac8a7d 254: onsuccess: #132: 1: [TCWG CI] Success after gdb: 2 commits discards 1735b61e7c 253: force: #131: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards 2b8d962cbe 252: force: #130: 1: [TCWG CI] Success after gdb: 15 commits discards 761eced6ad 251: onsuccess: #129: 1: [TCWG CI] Success after linux: 121 commits discards 754b16150a 250: onsuccess: #128: 1: [TCWG CI] Success after glibc: 2 commits discards 8a45094339 249: onsuccess: #127: 1: [TCWG CI] Success after gcc: 98 commits discards 06421c066d 248: onsuccess: #121: 1: [TCWG CI] Success after binutils/gc [...] discards b42258fbb8 247: force: #120: 1: [TCWG CI] Success after baseline build: [...] discards ea6f2a73dd 246: onsuccess: #118: 1: [TCWG CI] Success after glibc: 7 commits discards 1347500c93 245: onsuccess: #117: 1: [TCWG CI] Success after gcc: 16 commits discards 42a73e8433 244: onsuccess: #112: 1: [TCWG CI] Success after binutils/gc [...] discards b875732cd1 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/gc [...] discards 53a246b85f 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits discards 970c22cc83 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/gc [...] discards 794b074636 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/gc [...] discards a53dd7e1fd 239: force: #106: 1: [TCWG CI] Success after baseline build: [...] discards e7c86072c8 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards d139f63626 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits discards 16ca86c3ca 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 22 [...] discards 2742ec6c18 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards 40ee91e1f4 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards e33da646c9 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 4a0aedddcf 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards ec11cc055a 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits discards afdde64c47 230: onsuccess: #78: 1: Success after gdb: 2 commits discards 5c504cd5c5 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g4 [...] discards 228a19bf5f 228: force: #74: 1: Success after gdb: 53 commits discards eed72d5dc8 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 917f591be2 226: force: #70: 1: Success after baseline build: no new commits discards 70696d53b5 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g4 [...] discards 4d34e470a9 224: force: #65: 1: Success after gdb: 50 commits discards bc746d5a03 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g2 [...] discards b91bd4c21f 222: force: #60: 1: Success after gdb: 16 commits discards 9392d767fc 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g6 [...] discards 325a87074e 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02ddb [...] discards 901cd539d8 219: force: #50: 1: Failure after linux: 2520 commits discards 6fa8b0d50e 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g3 [...] discards 075a9b644d 217: force: #45: 1: Success after linux: 1 commits discards 4f76a3d2bf 216: force: #43: : Failure after baseline build: no new commits discards 2efe3dd251 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g1 [...] discards d5faf508e6 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g1 [...] discards 1373db9db5 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 73082c681d 212: force: #27: : Failure after baseline build: no new commits discards e9ac26acd6 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 605f541ead 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards fa9d277bd3 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards fcd206776f 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 87986d53c0 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 72bbc1b1f0 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 68153d5b3a 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 61d111433f 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 03ec2e5264 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 36c164417b 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards d8c30d9ac5 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 9f6feb5273 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards b83a3f15bf 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards a07f6830c8 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards af1f9a629c 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 485e59d4be 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards dcf7da3fee 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 1c26b49f5e 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards b39abd0f40 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 7fcc51c6b2 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards 097caa2cb7 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] discards 2cf950c2d4 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards d8edb66352 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] discards 038ee137e3 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] discards d9960d10de 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] discards 08582b98fa 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] discards b77f9f7c47 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] discards a7a9c0658e 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] discards d553a1f968 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] discards bbf0871a9b 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] discards 2e23c7f2b4 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 18fb57a218 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] discards ed659b1e87 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] discards 750d8d9837 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] discards 2181138c08 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] discards 37d8fe827d 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards 17658a84ed 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards b12590d831 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 819577f5b6 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] discards 9b69b05ff9 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] discards 571bc98c75 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards 36a8188108 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] discards ec5d7093c0 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards 5ba27432f0 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards 668d3f01b5 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards 3eda498a1c 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards 6b02043f06 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 04c2586517 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] discards 34e261a433 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards 11f65600fe 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards 80e1849077 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] discards 5d8887c0d4 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards 4d9da7eefd 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 909fbd557d 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 6d1af5bcb5 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new bf267275fa 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] new b1639026fa 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new 13d6f45cf9 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new f922cf2118 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] new 5c40b86891 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new a5e037772b 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new 79d1e54b1a 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new cdebe68a36 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new 98f470d0b5 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new 5ec3eac41f 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] new e0501471e9 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new 5130834055 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] new 2f3dbc5b8c 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] new a4646b12d1 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new 4a88554fb5 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new 937dbc2dfc 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new 8d934fef2f 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] new 5f7862c9bb 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] new e498c57d89 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] new 323b59eb72 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] new f2c753e042 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 2cedc66e84 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] new dccb091f38 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] new 84f8f528fe 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] new e40f275103 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] new 465d42b99e 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] new cf7d00eb26 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] new 3a0472c0cd 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] new ee9198f1e0 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] new e32f2e927c 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new ea5eed24db 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] new dada30a755 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new ec32f2a1d2 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new d0d09fce64 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 496f19a6fd 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new dc773fbaa1 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 509f1ac02a 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 32c3faf330 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 934fddba39 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new c7c45519da 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new f284717faf 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 6cf239f24f 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new cab2279fcb 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 7c4e6e1f7d 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new ddf60082bd 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new bcb246687d 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new a84b18dc85 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new f7264492f3 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 6bf4407be1 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new f911fefc62 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 81b646d6f3 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 5c522f14ef 212: force: #27: : Failure after baseline build: no new commits new 9b3c6ddbfb 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 8a91563301 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g1 [...] new 1a2400d2c6 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g1 [...] new 428cf8fec7 216: force: #43: : Failure after baseline build: no new commits new 906db34fd8 217: force: #45: 1: Success after linux: 1 commits new b78a5ad95e 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g3 [...] new e06cafc755 219: force: #50: 1: Failure after linux: 2520 commits new f7a85b8395 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02ddb [...] new 58afbe1e0b 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g6 [...] new a17c3c2215 222: force: #60: 1: Success after gdb: 16 commits new 7e2e22349c 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g2 [...] new d8c01b4528 224: force: #65: 1: Success after gdb: 50 commits new 8efb0cb82d 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g4 [...] new 8a7b4761ca 226: force: #70: 1: Success after baseline build: no new commits new 9fcc86c067 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new f65ea2c738 228: force: #74: 1: Success after gdb: 53 commits new 19b009dd35 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g4 [...] new c01f521190 230: onsuccess: #78: 1: Success after gdb: 2 commits new 4800093802 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits new de792bb5bd 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 3d1d639bb5 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 04c4289528 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new 7f2214a41b 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new 9f36dedb81 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 22 [...] new 4a21eb4780 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits new 3397501f46 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new 15c472dc9c 239: force: #106: 1: [TCWG CI] Success after baseline build: [...] new fa8a2a1c1e 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/gc [...] new e12e6a1944 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/gc [...] new 914a11bfea 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits new 2b7f467073 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/gc [...] new 5b864da5b8 244: onsuccess: #112: 1: [TCWG CI] Success after binutils/gc [...] new d2b09c47a5 245: onsuccess: #117: 1: [TCWG CI] Success after gcc: 16 commits new 85abae173e 246: onsuccess: #118: 1: [TCWG CI] Success after glibc: 7 commits new 54ab28835c 247: force: #120: 1: [TCWG CI] Success after baseline build: [...] new c4e506d25a 248: onsuccess: #121: 1: [TCWG CI] Success after binutils/gc [...] new 5d8c2dd355 249: onsuccess: #127: 1: [TCWG CI] Success after gcc: 98 commits new 56f83fec68 250: onsuccess: #128: 1: [TCWG CI] Success after glibc: 2 commits new 5a286afbb5 251: onsuccess: #129: 1: [TCWG CI] Success after linux: 121 commits new 6603168d6b 252: force: #130: 1: [TCWG CI] Success after gdb: 15 commits new 56925d9b4e 253: force: #131: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new 6c2ea7473e 254: onsuccess: #132: 1: [TCWG CI] Success after gdb: 2 commits new 0abaa11dd2 255: force: #133: 1: [TCWG CI] Success after baseline build: [...] new 54e21a2295 256: onsuccess: #134: 1: [TCWG CI] Success after binutils/gc [...] new a3bd3965de 257: onsuccess: #135: 1: [TCWG CI] Success after binutils/gc [...] new 7512997d6f 258: onsuccess: #136: 1: [TCWG CI] Success after binutils/gc [...] new a613ebf924 259: onsuccess: #143: 1: [TCWG CI] https://ci.linaro.org/job [...] new afdd89ffe1 260: force: #144: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...]

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 (1dd4e8ebd9) \ 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 2184 -> 2036 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2540 bytes 03-build_abe-binutils/console.log.xz | Bin 48960 -> 49188 bytes 04-build_abe-gcc/console.log.xz | Bin 237136 -> 236396 bytes 06-build_abe-linux/console.log.xz | Bin 8688 -> 8736 bytes 07-build_abe-glibc/console.log.xz | Bin 232856 -> 233012 bytes 08-build_abe-gdb/console.log.xz | Bin 46564 -> 46860 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3820 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4532 -> 4416 bytes 11-check_regression/console.log.xz | Bin 2692 -> 1580 bytes 11-check_regression/results.compare2 | 130 +- 12-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- jenkins/notify.sh | 2 +- manifest.sh | 13 +- sumfiles/gdb.log.0.xz | Bin 2924116 -> 2965976 bytes sumfiles/gdb.log.1.xz | Bin 137916 -> 138188 bytes sumfiles/gdb.log.10.xz | Bin 9992 -> 0 bytes sumfiles/gdb.log.11.xz | Bin 9880 -> 0 bytes sumfiles/gdb.log.2.xz | Bin 11520 -> 16264 bytes sumfiles/gdb.log.3.xz | Bin 9960 -> 10004 bytes sumfiles/gdb.log.4.xz | Bin 9880 -> 9904 bytes sumfiles/gdb.log.5.xz | Bin 9968 -> 9988 bytes sumfiles/gdb.log.6.xz | Bin 9916 -> 9852 bytes sumfiles/gdb.log.7.xz | Bin 9932 -> 9840 bytes sumfiles/gdb.log.8.xz | Bin 9952 -> 0 bytes sumfiles/gdb.log.9.xz | Bin 9900 -> 0 bytes sumfiles/gdb.sum | 94 +- sumfiles/gdb.sum.0 | 109 +- sumfiles/gdb.sum.1 | 489 +++----- sumfiles/gdb.sum.10 | 2163 -------------------------------- sumfiles/gdb.sum.11 | 2169 -------------------------------- sumfiles/gdb.sum.2 | 198 ++- sumfiles/gdb.sum.3 | 35 +- sumfiles/gdb.sum.4 | 33 +- sumfiles/gdb.sum.5 | 76 +- sumfiles/gdb.sum.6 | 22 +- sumfiles/gdb.sum.7 | 26 +- sumfiles/gdb.sum.8 | 2201 --------------------------------- sumfiles/gdb.sum.9 | 2180 -------------------------------- 40 files changed, 587 insertions(+), 9415 deletions(-) delete mode 100644 sumfiles/gdb.log.10.xz delete mode 100644 sumfiles/gdb.log.11.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.8 delete mode 100644 sumfiles/gdb.sum.9