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 45727ffcebf 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 8cbe83380c6 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 5b9c0d9c960 212: force: #27: : Failure after baseline build: no new commits discards 9e5600e9fc5 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards a2690632cc2 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 5e493d860bd 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 48eff13626e 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 829e82c2cb2 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 781c4d3ac08 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 50b3e8465be 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 16d35b753d6 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards e6632f330ca 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards d89eadc44a0 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards c6a6f5c783a 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 19a2ad84848 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards d7dedbf4575 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 8d0331431f2 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards ad67fab3356 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards ed8c0a27494 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards fa2cf194c53 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards daaddba1d89 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 3297dc81b03 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 7759901b099 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 88c2b9aad99 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 59877a584ed 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 5dceab0d3ca 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards 8ca20f7788f 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards f57a96a9a0b 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 114bc8bda89 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards 4d2d33a9af0 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards 97e4e0f3646 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 420aba9c8d4 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 334593c4a89 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 8dd64944ab7 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 8b994d33784 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards 715d3a5f63b 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards 227fbe1f453 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 8dce8e34b23 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 7269354c677 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards a48260e0843 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 7863a8c7fa5 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 118a27b875d 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards e23d7f8762c 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards fcb316ac5d3 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards b614d5f9c25 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards 40c75315e30 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 345abae9523 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards f4148710c21 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 8287172bd27 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 9eec578adf9 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 0c90325d0ec 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards 5b954218a11 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards d2c67c9a72a 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 69f9ef63991 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards fdc8f874d94 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 63bfe1be284 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 2495137c9e1 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 096e449abe5 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards a17f1b7174b 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 85b5467555b 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 34661ea0d39 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards facde2cf4cd 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 4ac005be718 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 0bf96192d4e 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 5ab5bf2d2f0 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 9d554ab7a57 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards bf8a493aaf4 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards d02b8a0b8a3 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards e484f6ccf79 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards c9569d9860f 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 5b95fe31b3a 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards d5b690fb3cd 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards b2244cb7ece 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards fd5dc163941 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 1dc48009a5c 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards cbfbe511d5c 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards a16112f8193 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 64351355b22 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards 07fb3acc66c 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 6e9be0c1123 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards e8f75af1c09 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 879088841ab 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 46770088f2b 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 134a122417c 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards 116a06fb1aa 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards a26d87cd55c 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 5b51ab6e589 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 702748885ea 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 5a5820d3054 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 7a19bb1a737 125: onsuccess: #614: 1: Success after linux: 12 commits discards 268291889aa 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 4cc00bd0cbb 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards efdc5bcb13a 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards bdc67e1a5cd 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards fa28484c5b0 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 55d19e681d3 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 06601bd4324 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 51d267f64e4 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards 9ebf8f063cc 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards b55e11d75c7 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 3e01d58d919 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new a92707f2d15 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 02a06683ed9 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new d64999d5bf4 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 0041327816f 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new 4bd69a6efc2 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 8d14662ff63 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 9535f7b5d00 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new b488b746bad 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 1a3bf00b224 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 4434866a020 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new eff34c37e89 124: onsuccess: #612: 1: Success after binutils: 18 commits new 6216b935bdf 125: onsuccess: #614: 1: Success after linux: 12 commits new 1ecfdb2f43c 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new f83b48b17d9 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new db7ef450eda 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new c9bf2ca354f 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 096b69cb1b2 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new 7657f8d171f 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 450e52959ce 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new f4a843ded62 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new 17745b5c2ae 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 22848d4dbec 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new b824089da42 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 1a9636028e0 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 9e75fd1f546 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 7e528734414 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 458f1f8de32 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new cea4187c9ab 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new acf4c2f2e18 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 237ebd1f843 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 4a4adbb06a7 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new b515a8b5d0e 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new a7a81396f4e 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 89481e6e8aa 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new c5311fed3a7 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new ef98c227dcf 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 33415e61c72 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new d35deb21e66 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new f51b0e41df1 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new 3914b5ba861 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 733196e97b5 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new 52816f29693 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 3a7f28b7950 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 536f412b1b3 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 4f2446dfa25 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 7396f172cd6 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new aa4e7546416 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 8c19a7ba8d0 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 539ac98d776 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new fa7e5b6355d 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 60314f12fa0 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new 448df9aa54e 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new c72e655ba96 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new b8617b672f2 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new c04843de1fe 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new abb5a803317 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new c96298603b5 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new 3532fb5052b 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new f84b1de5b4d 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 93e253da40a 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new b5dab1eac4b 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new fe689566a3f 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 4faa2275c56 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new ddf2a633661 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new efd5d7a7edd 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 5e23d305f45 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 56f93bda7c7 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new d6ce07956d0 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 273b1a03225 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new d58c996e711 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 9f413271c8c 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new 46266d10abf 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new ca7d21ba569 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new 498a01db58c 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new 24249afcc3d 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new e0b707e6cc3 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 81e0b245d0b 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new d6166673763 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new a9e98eade72 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new eef1f9981d0 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 34106660cac 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 510ea180a20 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new d3fa66a85e9 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new d62dfe7b4b7 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 409eaac3fa4 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 2af06e2af3c 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 12b9ea052df 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new d897b056a02 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 184f019e6f8 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 904e35c3bac 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 93cbc797fab 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 1176cd78011 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 7361c638c14 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 53711780cda 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 2e69edaa8a4 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 5f151ee0daf 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 0a2d2ba1427 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 5b4df69c2de 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 6a59dea581c 212: force: #27: : Failure after baseline build: no new commits new 3f3af572547 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new e0fd1abe2d9 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] new be6ffff94a6 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-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 (45727ffcebf) \ 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 2072 -> 2264 bytes 02-prepare_abe/console.log.xz | Bin 2516 -> 2524 bytes 03-build_abe-binutils/console.log.xz | Bin 48596 -> 49036 bytes 04-build_abe-gcc/console.log.xz | Bin 235220 -> 235172 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8668 -> 8668 bytes 07-build_abe-glibc/console.log.xz | Bin 233692 -> 233964 bytes 08-build_abe-gdb/console.log.xz | Bin 46984 -> 46660 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3772 -> 3772 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4436 -> 4592 bytes 11-check_regression/console.log.xz | Bin 4500 -> 4456 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 10 +- 11-check_regression/mail-body.txt | 75 +- 11-check_regression/results.compare | 31 +- 11-check_regression/results.regressions | 31 +- 11-check_regression/trigger-bisect | 4 +- 12-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- jenkins/jira-status.draft | 2 +- jenkins/mail-body.draft | 87 +- jenkins/notify.sh | 2 +- mail/mail-body.txt | 75 +- manifest.sh | 14 +- results | 31 +- sumfiles/gdb.log.0.xz | Bin 2937136 -> 2809052 bytes sumfiles/gdb.log.1.xz | Bin 143240 -> 138604 bytes sumfiles/gdb.log.10.xz | Bin 0 -> 10132 bytes sumfiles/gdb.log.2.xz | Bin 21432 -> 16808 bytes sumfiles/gdb.log.3.xz | Bin 19932 -> 11344 bytes sumfiles/gdb.log.4.xz | Bin 14860 -> 10316 bytes sumfiles/gdb.log.5.xz | Bin 6480 -> 10136 bytes sumfiles/gdb.log.6.xz | Bin 0 -> 10312 bytes sumfiles/gdb.log.7.xz | Bin 0 -> 10360 bytes sumfiles/gdb.log.8.xz | Bin 0 -> 10396 bytes sumfiles/gdb.log.9.xz | Bin 0 -> 10132 bytes sumfiles/gdb.sum | 1729 +++++++++++++--------- sumfiles/gdb.sum.0 | 1727 +++++++++++++--------- sumfiles/gdb.sum.1 | 1099 +++++--------- sumfiles/{gdb.sum.4 => gdb.sum.10} | 316 +--- sumfiles/gdb.sum.2 | 720 +++------ sumfiles/gdb.sum.3 | 484 +----- sumfiles/gdb.sum.4 | 311 +--- sumfiles/gdb.sum.5 | 2453 +++++++++++++++++++++++++++---- sumfiles/{gdb.sum.4 => gdb.sum.6} | 321 +--- sumfiles/{gdb.sum.4 => gdb.sum.7} | 330 +---- sumfiles/{gdb.sum.4 => gdb.sum.8} | 339 +---- sumfiles/{gdb.sum.4 => gdb.sum.9} | 317 +--- 49 files changed, 5269 insertions(+), 5309 deletions(-) create mode 100644 sumfiles/gdb.log.10.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 copy sumfiles/{gdb.sum.4 => gdb.sum.10} (86%) copy sumfiles/{gdb.sum.4 => gdb.sum.6} (85%) copy sumfiles/{gdb.sum.4 => gdb.sum.7} (86%) copy sumfiles/{gdb.sum.4 => gdb.sum.8} (86%) copy sumfiles/{gdb.sum.4 => gdb.sum.9} (86%)