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 0474816d86 245: onsuccess: #117: 1: [TCWG CI] Success after gcc: 16 commits discards 88aa6c27d3 244: onsuccess: #112: 1: [TCWG CI] Success after binutils/gc [...] discards b404159108 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/gc [...] discards 6ec307fdec 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits discards dee0a2546f 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/gc [...] discards 7fe63844e7 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/gc [...] discards bd2d0879e6 239: force: #106: 1: [TCWG CI] Success after baseline build: [...] discards 0f392bef74 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards 388ae1ceba 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits discards a6f05447eb 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 22 [...] discards 2fe853faff 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards 28e422f60f 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 1d98d923ba 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards d392f8ec6b 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 8e8c4c3468 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits discards 7e217887ed 230: onsuccess: #78: 1: Success after gdb: 2 commits discards 8170942eb6 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g4 [...] discards e32a0d1123 228: force: #74: 1: Success after gdb: 53 commits discards 32f5d6f6cf 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 37273661d1 226: force: #70: 1: Success after baseline build: no new commits discards 44ec99a40a 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g4 [...] discards 2e54ca8860 224: force: #65: 1: Success after gdb: 50 commits discards 6b76df0daa 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g2 [...] discards 6d2a2969f4 222: force: #60: 1: Success after gdb: 16 commits discards 16895a550d 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g6 [...] discards 680c808bd0 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02ddb [...] discards 5b5e7a4e3a 219: force: #50: 1: Failure after linux: 2520 commits discards 35ffb3b842 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g3 [...] discards ea06382dec 217: force: #45: 1: Success after linux: 1 commits discards 4468a30f7a 216: force: #43: : Failure after baseline build: no new commits discards de62228c2d 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g1 [...] discards 8e3fe46aa2 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g1 [...] discards 3abec40cff 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 214f7f0435 212: force: #27: : Failure after baseline build: no new commits discards 122de1926e 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 2d20eaab18 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 7ace09eb47 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards e6b1d92b64 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 4185c74ab2 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 24d0f739c4 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 68b828ea44 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 71052f9da7 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 64eafdb08e 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards ff345a83a3 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 7f8cd2eb2b 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 9a52d19154 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 9fd709cc73 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards db5ac75a1a 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards e8a60ba0b0 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 4b908ca037 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 9626d02fc1 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards edaee2c6bb 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards c1bd3cc429 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 79d35feccd 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards 45c8750dad 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] discards 9f82b6cd82 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards 318f610a74 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] discards 27862313b3 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] discards 5782a6cf6b 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] discards e180c47c31 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] discards 4f8be2537c 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] discards fb057406f5 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] discards 05c70d9c12 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] discards 85aaff83c4 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] discards 49d8fab516 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 496c4c3cc2 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] discards 44146dfa4d 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] discards 7a22d2edd3 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] discards d8301da591 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] discards 068c84c4dc 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards 82e99f1529 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards bee4faac55 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 73bdfac4d5 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] discards ba55c6a72f 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] discards ac7bd2cbc1 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards 79789fb290 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] discards b28ea11811 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards 2bda50012c 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards 7caee715a2 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards 1d95ac46a7 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards c9864dbd84 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards d2fdf0ea95 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] discards 5ee9a56375 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards 26af63a239 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards 46af2fcbe4 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] discards 8be3cfe064 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards 54dd152ae4 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards 1ffbcbabda 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards 55b4c5734d 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 09791e2a76 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards d58c62b5d1 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 68f9990400 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] discards ab5eb7dea1 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] discards 03b1118f8b 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] discards 0e5c8c3d86 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards a82cd619d9 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards 31ed4bf87e 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 01b31a7cb5 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 9010505e19 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits discards 9b4b953025 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards 14fd312448 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new 630fe20257 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new d8025f131e 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new 384eb54b5b 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits new e004d1f245 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new a94a2e674c 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 64f5326300 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 37e7b66045 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 2b2481c93c 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new 7adfe77c30 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new c680745fb7 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] new 9ba838d8af 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 3f163cacec 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new d3124f48ee 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new dc5deb9ed2 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new ca59b94dda 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 79c8143158 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new 00b8510ece 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] new f8b716aa4b 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new b0daf4ef33 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new cc76afff03 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] new aa9e772210 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 080a93cb9c 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new 950b2b50d5 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new 5b7365b9b6 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new fa45654fb3 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new b503b59819 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] new 825c89c4f5 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new 78fd2f0902 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] new fe36c9789e 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] new 54852d018b 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new f6212c88ee 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new 0511c9f8dc 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new e3589a99da 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] new 12d8c2c391 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] new 3a6c677ff1 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] new 1a2cb63ee7 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] new cfb37900f1 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new d17d2628c4 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] new 225570d950 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] new f49c6a76c1 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] new f4d141ab4c 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] new d1844c512d 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] new af45814383 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] new 1f16f221ac 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] new 73dccb559a 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] new 1cd64a3338 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new 00cecfd7fa 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] new d9e29d1c01 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new eae9aafd36 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 2d7ae3c97d 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 7541364b44 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 8b86607cc3 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 4fb84879ae 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 0626805fdf 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new dc141f721d 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new d6ccff1444 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new b48403cbff 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new bc367ce964 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 3cd2350465 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 3e7a79b00c 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 7f3ad6a671 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 7019b825c8 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 626808db16 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new b39141b8c7 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 0c03a4a97b 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new f5b3bc1903 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new a538b5a530 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 5f2b2a21cb 212: force: #27: : Failure after baseline build: no new commits new c32b78bc0f 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 3dcf710d94 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g1 [...] new 687417d133 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g1 [...] new 77b5e0d92f 216: force: #43: : Failure after baseline build: no new commits new d7fe40565d 217: force: #45: 1: Success after linux: 1 commits new 47e92d1b96 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g3 [...] new 2457df53af 219: force: #50: 1: Failure after linux: 2520 commits new d429c82828 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02ddb [...] new 6eb7c6d2a9 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g6 [...] new 6700265de5 222: force: #60: 1: Success after gdb: 16 commits new a747c8dbfd 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g2 [...] new d44905421b 224: force: #65: 1: Success after gdb: 50 commits new e731bfb41c 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g4 [...] new 4fc97fb686 226: force: #70: 1: Success after baseline build: no new commits new 35a3273d30 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 64eba622bd 228: force: #74: 1: Success after gdb: 53 commits new 21e259024b 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g4 [...] new 9fa4ec57d1 230: onsuccess: #78: 1: Success after gdb: 2 commits new aefd1281ae 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits new 6ed6ba6c95 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 382fc6794e 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 7ed5235ca9 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new 47bc8c6ca6 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new 848c66489a 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 22 [...] new 18771e5aee 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits new 23773c835d 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new 9db2c82c8b 239: force: #106: 1: [TCWG CI] Success after baseline build: [...] new 03aa5c14f3 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/gc [...] new 37c3e3e36c 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/gc [...] new c35d0d1a2c 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits new 8d323868f9 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/gc [...] new 97907c47ab 244: onsuccess: #112: 1: [TCWG CI] Success after binutils/gc [...] new 0988c98976 245: onsuccess: #117: 1: [TCWG CI] Success after gcc: 16 commits new e3f8c9676c 246: onsuccess: #118: 1: [TCWG CI] Success after glibc: 7 commits

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 (0474816d86) \ 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 2032 -> 1968 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2532 bytes 03-build_abe-binutils/console.log.xz | Bin 50492 -> 50164 bytes 04-build_abe-gcc/console.log.xz | Bin 235640 -> 235800 bytes 06-build_abe-linux/console.log.xz | Bin 8844 -> 8836 bytes 07-build_abe-glibc/console.log.xz | Bin 232788 -> 232152 bytes 08-build_abe-gdb/console.log.xz | Bin 48104 -> 47700 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3760 bytes 10-build_abe-check_gdb/console.log.xz | Bin 6080 -> 5516 bytes 11-check_regression/console.log.xz | Bin 4596 -> 4456 bytes 11-check_regression/results.compare2 | 151 +-- 12-update_baseline/console.log | 56 +- dashboard/dashboard-generate.sh | 2 +- git/glibc_rev | 2 +- mail/changes-list-long.txt | 14 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 28 +- manifest.sh | 14 +- sumfiles/gdb.log.0.xz | Bin 2962660 -> 2951612 bytes sumfiles/gdb.log.1.xz | Bin 138536 -> 143224 bytes sumfiles/gdb.log.10.xz | Bin 10044 -> 0 bytes sumfiles/gdb.log.11.xz | Bin 10308 -> 0 bytes sumfiles/gdb.log.12.xz | Bin 10268 -> 0 bytes sumfiles/gdb.log.13.xz | Bin 10304 -> 0 bytes sumfiles/gdb.log.14.xz | Bin 10116 -> 0 bytes sumfiles/gdb.log.15.xz | Bin 10072 -> 0 bytes sumfiles/gdb.log.16.xz | Bin 10132 -> 0 bytes sumfiles/gdb.log.17.xz | Bin 10032 -> 0 bytes sumfiles/gdb.log.18.xz | Bin 10456 -> 0 bytes sumfiles/gdb.log.19.xz | Bin 10200 -> 0 bytes sumfiles/gdb.log.2.xz | Bin 11988 -> 8420 bytes sumfiles/gdb.log.20.xz | Bin 10328 -> 0 bytes sumfiles/gdb.log.21.xz | Bin 10176 -> 0 bytes sumfiles/gdb.log.22.xz | Bin 10428 -> 0 bytes sumfiles/gdb.log.23.xz | Bin 9836 -> 0 bytes sumfiles/gdb.log.24.xz | Bin 10096 -> 0 bytes sumfiles/gdb.log.3.xz | Bin 10056 -> 6544 bytes sumfiles/gdb.log.4.xz | Bin 10140 -> 0 bytes sumfiles/gdb.log.5.xz | Bin 10128 -> 0 bytes sumfiles/gdb.log.6.xz | Bin 10124 -> 0 bytes sumfiles/gdb.log.7.xz | Bin 10012 -> 0 bytes sumfiles/gdb.log.8.xz | Bin 9812 -> 0 bytes sumfiles/gdb.log.9.xz | Bin 10016 -> 0 bytes sumfiles/gdb.sum | 112 +- sumfiles/gdb.sum.0 | 131 +- sumfiles/gdb.sum.1 | 201 ++- sumfiles/gdb.sum.10 | 2152 ------------------------------ sumfiles/gdb.sum.11 | 2188 ------------------------------ sumfiles/gdb.sum.12 | 2221 ------------------------------- sumfiles/gdb.sum.13 | 2164 ------------------------------ sumfiles/gdb.sum.14 | 2167 ------------------------------ sumfiles/gdb.sum.15 | 2182 ------------------------------ sumfiles/gdb.sum.16 | 2161 ------------------------------ sumfiles/gdb.sum.17 | 2160 ------------------------------ sumfiles/gdb.sum.18 | 2218 ------------------------------- sumfiles/gdb.sum.19 | 2157 ------------------------------ sumfiles/gdb.sum.2 | 2327 +++----------------------------- sumfiles/gdb.sum.20 | 2193 ------------------------------ sumfiles/gdb.sum.21 | 2191 ------------------------------ sumfiles/gdb.sum.22 | 2219 ------------------------------- sumfiles/gdb.sum.23 | 2171 ------------------------------ sumfiles/gdb.sum.24 | 2180 ------------------------------ sumfiles/gdb.sum.3 | 2340 +++------------------------------ sumfiles/gdb.sum.4 | 2167 ------------------------------ sumfiles/gdb.sum.5 | 2186 ------------------------------ sumfiles/gdb.sum.6 | 2174 ------------------------------ sumfiles/gdb.sum.7 | 2157 ------------------------------ sumfiles/gdb.sum.8 | 2049 ----------------------------- sumfiles/gdb.sum.9 | 2144 ------------------------------ 69 files changed, 778 insertions(+), 50203 deletions(-) delete mode 100644 sumfiles/gdb.log.10.xz delete mode 100644 sumfiles/gdb.log.11.xz delete mode 100644 sumfiles/gdb.log.12.xz delete mode 100644 sumfiles/gdb.log.13.xz delete mode 100644 sumfiles/gdb.log.14.xz delete mode 100644 sumfiles/gdb.log.15.xz delete mode 100644 sumfiles/gdb.log.16.xz delete mode 100644 sumfiles/gdb.log.17.xz delete mode 100644 sumfiles/gdb.log.18.xz delete mode 100644 sumfiles/gdb.log.19.xz delete mode 100644 sumfiles/gdb.log.20.xz delete mode 100644 sumfiles/gdb.log.21.xz delete mode 100644 sumfiles/gdb.log.22.xz delete mode 100644 sumfiles/gdb.log.23.xz delete mode 100644 sumfiles/gdb.log.24.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.12 delete mode 100644 sumfiles/gdb.sum.13 delete mode 100644 sumfiles/gdb.sum.14 delete mode 100644 sumfiles/gdb.sum.15 delete mode 100644 sumfiles/gdb.sum.16 delete mode 100644 sumfiles/gdb.sum.17 delete mode 100644 sumfiles/gdb.sum.18 delete mode 100644 sumfiles/gdb.sum.19 delete mode 100644 sumfiles/gdb.sum.20 delete mode 100644 sumfiles/gdb.sum.21 delete mode 100644 sumfiles/gdb.sum.22 delete mode 100644 sumfiles/gdb.sum.23 delete mode 100644 sumfiles/gdb.sum.24 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