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 3f3e618421f 212: force: #27: : Failure after baseline build: no new commits discards c0e6bc41486 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 0d0957742da 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 621bc209147 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 108b33b93d9 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 3fd27b061dc 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards ca7f695c5cc 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 9b3a6924392 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 1e1d6b1259b 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards cdaa087258b 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards fa735011e21 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards a03187fa5f1 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards ba0cd1577a3 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 5fb219eca55 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 88c2b1dd704 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 52d529c6bb3 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards d1b8bd70805 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 6521d1cbd35 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 4be37f278e6 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 5224a4a8ed1 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards a68d53bb77e 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 3c8cff479bf 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards f4688a1c0ce 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 0ecae54e53d 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards beabba48ea7 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards e4a5dbc7ff4 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 3dcdfa77a50 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards 2db0aa2f90c 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards 27b1cdb8dee 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 2425c1d3949 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 9f3275a0951 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 8ae7e1bd613 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards f8cf8f8bdde 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards 105edc34498 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards a6d2e7da3f1 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards a469757b724 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 591cf91d670 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards f5fad975d7d 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 6caab166679 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 2748d9befba 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards d3d566c70d9 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 206d1d1f0c7 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards fb3857e859f 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards c51b332f020 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 7920d61bd72 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 4c115ffc0e7 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards f786d33352b 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 9acb487c76f 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 2fbcf8ce413 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards 50e9c4fae57 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 049bdebaea8 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 025f9d5c8a2 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 3a89da45f25 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards b515fa0ef23 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards aa50b389acb 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 002e5f6da7b 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards afbf343bf88 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards b15baf0f1d8 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards b4050b1cff0 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards 39e0837eb4c 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards d3d114d5370 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 9fe19be7d72 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 2b9ad1e6c64 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 4c653d9b665 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 5d066f9b194 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards b008e2acdf3 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards 7bf955523d6 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards ae3500a9799 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 9d00eec9dc2 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards 7d9388ccda9 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 323cf72d116 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 4b3a9d6a78d 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards bb8d211a465 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards e049ed6f2de 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 28c8507f050 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards edc5ea91c0f 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards f6af779a06e 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 30052c5e450 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards c13aa8c4850 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards b5d673e9283 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 60b80417284 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 0a86091fe36 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards a66cb6f5f17 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards dd6f401e943 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 39fb1ba27de 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 76d602248d3 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards e4276f24cbe 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 11f664acf87 125: onsuccess: #614: 1: Success after linux: 12 commits discards bc7241e12a5 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 2ec9e63e0cb 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 04b4eb34bc1 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 50520d08ed4 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 362095951f9 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 4c345492d37 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 36989457128 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards b775f7bebe5 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards cb9012d3ce3 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 6e5628faf95 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 2b69c8a4ff1 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards d6a1c8c2eb0 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 3de94cbbe73 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] new 7605120b1a0 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] new a5c6ace0201 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 3764eabb360 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new a8bf816de35 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new b9e79a01ae6 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new b47c4eb8804 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new 2a3e518e546 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new ad7dcfa9562 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 687f74aecf9 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new b952d75cf48 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 547e0bcb7a6 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 82ab3569b48 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new c5d30ba3ba0 124: onsuccess: #612: 1: Success after binutils: 18 commits new 247f3226efd 125: onsuccess: #614: 1: Success after linux: 12 commits new ce3ab4c50e5 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new b6bc0c87a5f 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new e00d79ffb37 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 482c3fda64d 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new f17ba0c4bfc 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new 5fdc56251f3 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new db3658805fb 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 6adc19b5c68 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new ed919065905 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 03dcc80a50a 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new b6d5ca7cb1a 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new d3c1ac52cfd 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new b87f406018d 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new f45cffb766f 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new c3caa69c4a5 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new de26541bfd5 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new c58fc1fa257 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 09b2e47f935 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 7b0297a51a1 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new 59ac70b1158 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 7962867e53f 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 0985375defe 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new d5fbed22ae6 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 4f1db502acb 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 61b8403248d 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new daf14d5c8b7 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 4825837ebd1 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new 4dc1e22d43b 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 1836b0f0026 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new 5267e68ba6c 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 41ec8d1abff 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 732af35775b 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 48a5ccaeca9 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 459e4b590c7 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new bc29733c75d 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 85f81b66d62 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 77ea73703b6 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new dc88531c7db 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new e0d5a6fa056 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new 8616588729a 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 5936d098563 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 1cf277552a5 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new f6bbe07cab2 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 1f8a6c5f3b7 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 853f732d924 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new fd574bd8c58 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 9698fa494e0 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 5d9b5e2abc8 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new 8aa0e25fd40 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 603fe4d38f8 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 42bd1a77ae0 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new ae49b4023af 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 493e1f0c6a6 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 8216d13d994 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new a90d3c6f5e7 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new 64956667714 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 6c3cd268238 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new e41c1044aea 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new a2df8bec62b 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new abf5cbe5766 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 1ec26b89439 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new f99b2971a4f 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new 8471b105b65 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new 680f602e556 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 4493354ec97 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new adc40b51e6a 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new ba04da506a5 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 9548071fdb2 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new a8610336b33 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new ecf18b6c16c 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 1b8247508eb 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new e855a2db69a 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new d399fcafed1 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 84c8f909092 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 99b9f0667ac 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 01d24c12448 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 0795d7971b9 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 80b6dd1520f 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new c540f53224e 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new cdaec2e3782 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 5de8d3bb7ad 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new ac6f74b0b58 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 0be96fcce1c 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 6b8c7ea305d 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 1f6156a8c5f 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 5a3f8f1daaa 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new aaec93ffbb9 212: force: #27: : Failure after baseline build: no new commits new c7a9a1e93df 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...]
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 (3f3e618421f) \ 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 1724 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 3444 -> 2452 bytes 03-build_abe-binutils/console.log.xz | Bin 52668 -> 48356 bytes 04-build_abe-gcc/console.log.xz | Bin 236000 -> 236520 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9236 -> 8556 bytes 07-build_abe-glibc/console.log.xz | Bin 235808 -> 233108 bytes 08-build_abe-gdb/console.log.xz | Bin 50308 -> 47420 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3764 -> 3780 bytes 10-build_abe-check_gdb/console.log.xz | Bin 1052 -> 4248 bytes 11-check_regression/console.log.xz | Bin 2504 -> 4072 bytes 11-check_regression/jira-body.txt | 2 +- 11-check_regression/mail-body.txt | 66 +- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results.regressions | 2 - 12-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 66 +- mail/mail-subject.txt | 2 +- manifest.sh | 33 +- results | 4 +- sumfiles/gdb.log.0.xz | Bin 0 -> 2932132 bytes sumfiles/gdb.log.1.xz | Bin 0 -> 143088 bytes sumfiles/gdb.log.2.xz | Bin 0 -> 16976 bytes sumfiles/gdb.log.3.xz | Bin 0 -> 14948 bytes sumfiles/gdb.log.4.xz | Bin 0 -> 10396 bytes sumfiles/gdb.log.5.xz | Bin 0 -> 10256 bytes sumfiles/gdb.sum | 99688 ++++++++++++++++++++++++++++++ sumfiles/gdb.sum.0 | 99684 +++++++++++++++++++++++++++++ sumfiles/gdb.sum.1 | 8554 +++ sumfiles/gdb.sum.2 | 2349 + sumfiles/gdb.sum.3 | 2361 + sumfiles/gdb.sum.4 | 2197 + sumfiles/gdb.sum.5 | 2174 + 39 files changed, 217065 insertions(+), 169 deletions(-) delete mode 100644 11-check_regression/results.regressions create mode 100644 sumfiles/gdb.log.0.xz create mode 100644 sumfiles/gdb.log.1.xz create mode 100644 sumfiles/gdb.log.2.xz create mode 100644 sumfiles/gdb.log.3.xz create mode 100644 sumfiles/gdb.log.4.xz create mode 100644 sumfiles/gdb.log.5.xz create mode 100644 sumfiles/gdb.sum create mode 100644 sumfiles/gdb.sum.0 create mode 100644 sumfiles/gdb.sum.1 create mode 100644 sumfiles/gdb.sum.2 create mode 100644 sumfiles/gdb.sum.3 create mode 100644 sumfiles/gdb.sum.4 create mode 100644 sumfiles/gdb.sum.5