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 d65ac3746ba 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] discards 98c231f2b48 219: force: #50: 1: Failure after linux: 2520 commits discards 248c866f12a 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] discards 69e7bdf0ef0 217: force: #45: 1: Success after linux: 1 commits discards a52bf3f1dcb 216: force: #43: : Failure after baseline build: no new commits discards 3bff435725f 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] discards d22bd1d264c 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] discards cd0e1fa6bba 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 9b4dbe33be5 212: force: #27: : Failure after baseline build: no new commits discards fff2de94d9c 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards ec36d653274 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 008ec8983e1 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 24606e4242c 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards f89e6af9294 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 19cd8f0a828 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 27707fb16e6 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 81fe2cb5a9f 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 958f57f465a 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 4cf936f25a8 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards dce2b47e4f3 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 95ef6b6e406 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards b5a012092d0 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 2e1f348636c 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards bf5e082b5ba 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards c20bc67fb1c 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 7a7d276ac2a 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards cfaa3206752 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 10e5107e51a 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards fdcaaa2c296 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards a1b672eb209 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 7f0c4817a1c 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards b1169194820 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards dd1b7d51421 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards 832938f6bb7 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 4b266a15c63 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards 66d5f76e754 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards 67e40b90906 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 5290f14b6c5 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 9aeb825ce88 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 9f9c4a34827 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 5aea7afca7f 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards 57f360fe606 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards d695968e0db 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards ca9c64dcb7a 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards af61dbc1284 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 9d083fb1685 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards bac73f4e253 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards cba4654102b 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 7c146f0212b 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 852a2c3599d 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 11ad97917da 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards 31e9d7fd04c 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 5464168b700 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards cc91a49b7d4 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 0e001abaa77 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 6f3e4a833a0 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards d4c8ab7a1b4 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards 5e6c362962f 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards bb0d1110351 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards cdcf3757700 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 27dcbb362ac 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 48ccbe52955 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards a5c325e4405 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards fe84ef34f91 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 7669b4be358 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards cf14f087c0b 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 48c5290360a 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards 9e594f1c2f6 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 3721fec6038 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 38c2c831ccf 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 38b53e05be3 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 7a4c11dddd9 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 31ebda51082 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 8bfd513c9b8 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards b2025bcd162 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards ac1bbbcb13e 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 24d123e64fb 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards c4b3ce0a5c8 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 7cf04e78a97 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 5926c8dea8c 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 21932bbb7dc 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 63b8c79355a 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 8383d048cd7 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards da9fe5232d9 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards 1ed87dfbddc 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 0d8278d64b0 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards e223ee51147 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 7222f721d92 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 246da916bec 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 1db95c6cbf9 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards a5a8bfb62dd 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards f432d2127a8 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 12be377ea71 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards f692fa16148 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 781782c5d66 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 06533b9d4d0 125: onsuccess: #614: 1: Success after linux: 12 commits discards 0d7dff229d9 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 916342237ad 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards a65dbaa51e0 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards fcc577741cf 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards dea1d78e734 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 3ea33422587 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 1f70b42a0cc 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new d38e3f22153 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new c5376006567 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new ae980169a5c 124: onsuccess: #612: 1: Success after binutils: 18 commits new 317b203ded5 125: onsuccess: #614: 1: Success after linux: 12 commits new 1ae32b58e73 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new d53e563a185 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 6d8d35ba520 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 0792db74c61 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new c6328a4bd7b 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new 7f2efa4c5cc 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new a45b75253c7 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new c5a20ea3d93 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new 8cc079ca0b3 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 9164a912c04 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new b5883597a56 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 27dc1560516 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 82168ab00df 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 341ee9b3fcc 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new a50078ec03d 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new eabb81108ed 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new bd3a1e5384d 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 809e6c6e1ad 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new e2228d91095 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new eca09d8f728 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 58859b294d0 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 988055fcbad 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new 9284aab7955 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 59f440cac77 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 54e2a3851c1 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 95f5d4184f0 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new a964c11d9b7 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new 17cdf0acf21 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 243dcbb07fe 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new 604ff50f73e 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 6f8eec63c19 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 4db4bb22e23 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 87606e34ea9 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 4e44936d807 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new e71ab6d40a9 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new eea7dbde5f9 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new a3d2b03f885 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 27c4a76b6c9 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 4449d5e106c 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new a8ec68362d3 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new dc0d3f1f82f 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 2325bbd97f7 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new b6bba74a470 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 2e046ed0b65 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 9df5fb69aae 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new 9531f50b02c 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 4f0f0b5114a 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 49cb0f638be 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new 9aa001b7897 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new ca55176f72a 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new fa61f2be9f7 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 7609246cb3e 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 54df284acab 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new e250fbfbf35 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 86104176ffe 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new fcae719b2e1 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new e8c62c7cf8d 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new b54491dbb1a 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 91c26c3f62c 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new c4cd163b457 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 8a880a43704 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new 8acd5e7a8b7 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new e014e2566c4 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new dbece5b43bd 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 1db7da68194 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 95e31df7a88 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 02010650733 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 3b6273d70d2 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 094753995a0 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 7f859764325 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new debdef72440 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 391776064b0 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new eeaa4478972 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 3c3f36f6d7a 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 84d1d045717 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 64a21722d5a 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 1ffc5e43688 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new ad18fb34cae 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 7bfa5d7880c 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new dac63edf22b 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 6c468f168fd 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 560c295a74f 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 5fb0dbd97a1 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 70d4b6aaa21 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 0a4ed564db3 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 3aeb30670d0 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 43dc469b7a9 212: force: #27: : Failure after baseline build: no new commits new 5f73003f61c 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 8976690ef02 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] new 0deb1dd5e57 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] new 1d8931c005d 216: force: #43: : Failure after baseline build: no new commits new abbc626556b 217: force: #45: 1: Success after linux: 1 commits new 5ae404e006c 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] new b56ef3a8e0b 219: force: #50: 1: Failure after linux: 2520 commits new 23034e963da 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] new f6085b956dc 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...]
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 (d65ac3746ba) \ 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 1988 -> 2072 bytes 02-prepare_abe/console.log.xz | Bin 2532 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 49232 -> 48680 bytes 04-build_abe-gcc/console.log.xz | Bin 237820 -> 236424 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8524 -> 8556 bytes 07-build_abe-glibc/console.log.xz | Bin 234856 -> 233076 bytes 08-build_abe-gdb/console.log.xz | Bin 47748 -> 46984 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3788 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4312 -> 4496 bytes 11-check_regression/console.log.xz | Bin 3316 -> 3216 bytes 11-check_regression/mail-body.txt | 18 - 11-check_regression/results.compare | 9 +- 12-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 20 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- sumfiles/gdb.log.0.xz | Bin 2927064 -> 2930820 bytes sumfiles/gdb.log.1.xz | Bin 134560 -> 185224 bytes sumfiles/gdb.log.2.xz | Bin 12832 -> 16820 bytes sumfiles/gdb.log.3.xz | Bin 6440 -> 14812 bytes sumfiles/gdb.log.4.xz | Bin 0 -> 14976 bytes sumfiles/gdb.log.5.xz | Bin 0 -> 10288 bytes sumfiles/gdb.log.6.xz | Bin 0 -> 10312 bytes sumfiles/gdb.log.7.xz | Bin 0 -> 10160 bytes sumfiles/gdb.log.8.xz | Bin 0 -> 10364 bytes sumfiles/gdb.log.9.xz | Bin 0 -> 10116 bytes sumfiles/gdb.sum | 3884 +----------- sumfiles/gdb.sum.0 | 3895 +----------- sumfiles/gdb.sum.1 | 10522 +++++++++++++++++++++++++++++++- sumfiles/gdb.sum.2 | 2452 +++++++- sumfiles/gdb.sum.3 | 2182 ++++++- sumfiles/gdb.sum.4 | 2352 +++++++ sumfiles/gdb.sum.5 | 2161 +++++++ sumfiles/gdb.sum.6 | 2173 +++++++ sumfiles/gdb.sum.7 | 2113 +++++++ sumfiles/gdb.sum.8 | 2188 +++++++ sumfiles/gdb.sum.9 | 2163 +++++++ 41 files changed, 28177 insertions(+), 8017 deletions(-) create mode 100644 sumfiles/gdb.log.4.xz create mode 100644 sumfiles/gdb.log.5.xz create mode 100644 sumfiles/gdb.log.6.xz create mode 100644 sumfiles/gdb.log.7.xz create mode 100644 sumfiles/gdb.log.8.xz create mode 100644 sumfiles/gdb.log.9.xz create mode 100644 sumfiles/gdb.sum.4 create mode 100644 sumfiles/gdb.sum.5 create mode 100644 sumfiles/gdb.sum.6 create mode 100644 sumfiles/gdb.sum.7 create mode 100644 sumfiles/gdb.sum.8 create mode 100644 sumfiles/gdb.sum.9