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 dbc5073212b 217: force: #45: 1: Success after linux: 1 commits discards cea68b942a4 216: force: #43: : Failure after baseline build: no new commits discards dccbaa559f3 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 8813c32db2a 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 302668e1c18 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards f9f8982c2b5 212: force: #27: : Failure after baseline build: no new commits discards 04b556c6fb3 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards a1c90007f20 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards d69a4fb8410 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 1c8b6844941 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards b981d06063a 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 2035d505463 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 6fb4a917ca2 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 730d7183734 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards f195cbdabc4 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 658a050bbcf 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 4b92e48c7d0 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 53073807105 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 6578237e34d 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 99104153d1d 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards f9fdc598522 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards d2672609a02 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards bfc6f34fb37 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards bdddfa7fc04 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 2d1e0b70c6d 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 83d98c2003e 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 7b89455e4cb 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 855269bf32e 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards d7f54d47a60 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards f5fd2dfa67b 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards ff8498e15a1 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 6c6058087fe 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards ee9df97d53c 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards 4674d6415b4 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 4fc2d29a3b3 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards e75fc50fe56 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards b1191216c65 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 380e835759b 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards 2f228c7a769 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards 2faaa2f20c7 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 385cd6e2bb7 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards e6923459dc6 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 450df6c9262 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 95dd4c137cd 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards ce5c7f2dab8 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 857fac578b3 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards cf04f0f8225 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 4e8675123d7 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards 4fde1a9a861 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 4e8308f512b 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards ab7a7b57b8c 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards d8c13e21083 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards a64a02afc0b 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards cab8932a0e9 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards 713160c3b36 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards dbbe76ca3a8 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 9db898fc279 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards a9c739d783e 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 5357cde04d4 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 3ce6f18626b 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards d848e759871 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards ae3c24242f0 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards c016ce70531 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards f9556580f41 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards dd986c21cf1 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 19b689ba175 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards a720be7faf1 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 3f227461658 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 1a2cc29f9c9 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 162406d4fef 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 3c705012138 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards 984b55a4637 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards dd27fec8ba9 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 78ff073c446 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards fad6b0e4d5c 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards dde21164eae 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 42ce2ece36b 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards b932f31eabd 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards cbed528318a 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 7c0bec45fc5 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 55f314e5164 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards 8d9e5c1dce9 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 1da4e441907 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 12d9c15cfc7 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 7802b665f61 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards f2c5ce7d58b 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 6991b5a032b 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards 5d20dabb57c 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards 065d31a96dd 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 82ed24c3244 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 7beafd65c75 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 6b22387cc5b 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards c75049c19d9 125: onsuccess: #614: 1: Success after linux: 12 commits discards c1e1a55e356 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 806494f7699 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards fec1df42e43 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards ac62bd43247 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 7f959ee4577 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards e76e6f38b2c 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards a9683c63728 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 31b4b4475e0 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new 47d7fd1d2a7 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new 56273677dff 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 52da933907f 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new a494311d269 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new fce5f1de1c4 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 99e3ed9471d 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new f06846c43f1 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 3d3d5e4d78d 124: onsuccess: #612: 1: Success after binutils: 18 commits new 03ffe5282f3 125: onsuccess: #614: 1: Success after linux: 12 commits new c085cd8086c 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 2fba6caca25 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 79a8ce55444 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 0e63c9a6858 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 9083f3e0f4e 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new 77bb5ef11fd 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 79c6ed89196 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new a01c9b2dbee 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new 21ecad44f19 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new d8149f5fb54 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 73dd29645ea 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new a14b8ef6456 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new a9500d907d3 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new b7bc9540ae5 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new f4698b96506 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 92ba4e632c5 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 413b9f62e53 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 2e07691f6f5 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 5fc1e4434a5 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new b55569286e0 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 98dcd280626 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 3207ce33ad2 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new 751b3ad64ad 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 755ca60d52a 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 7bc92d8fb16 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new fa1e3845820 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 6edc229b083 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new 5d477027aa9 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 1b32280c654 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new 5d658824bbb 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 398850b30f3 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new b5993977ab6 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 6b0ead88823 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new bdec28b4dfb 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 3a276f5a8fa 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new e41e06728de 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 0ab0913ff57 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new fe87c0cd3aa 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 499019f063b 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new 07876f18cfc 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new f9331250c6b 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new b29d512f85e 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 85566a3e71f 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new a0a7a69afd0 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 3f419ba6e4e 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new aeced05fc0a 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 018523d28a0 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 5413b7fd8dc 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new 1c4ad314abc 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 2967953e14c 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 2cc7edb7c14 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 739e511c99f 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 088a8ff2b4f 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 5897a440eb8 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 6a785fa0de1 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new de0f6357dcf 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 9e8639e8991 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 343536495d0 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new bf26db6d1d3 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new b846d337a88 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 971c14c6aff 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new a502e23b90c 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new fca3cb986a8 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new fb9b14c3116 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new d6fca64daca 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 8aec99d28fb 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new b6b68951c94 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new f659d2647e9 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new d6fd0eb84e2 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 6f747a4b221 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 9d23a72c38a 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 7077345b988 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 4cd9e67d6bd 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 21e5ae73e45 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new f7d18ce4028 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 212086d898d 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new af42457880a 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 0950df0dbd7 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new c10071aaaf3 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 9417e7729aa 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new fe36572d5da 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 8c2da54faaf 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new e699d1d3524 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 14650a91100 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 65e4da196bc 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 44eb6f0c344 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new f8e1dc6ade8 212: force: #27: : Failure after baseline build: no new commits new 5996526e2c7 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 27ce6313635 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] new 942284f256c 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] new 78b211587d0 216: force: #43: : Failure after baseline build: no new commits new d088f8cffb2 217: force: #45: 1: Success after linux: 1 commits new 4f442b10fe1 218: force: #48: 1: Success after gdb-13-branchpoint-1471-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 (dbc5073212b) \ 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 1968 -> 2236 bytes 02-prepare_abe/console.log.xz | Bin 2496 -> 2488 bytes 03-build_abe-binutils/console.log.xz | Bin 49128 -> 49020 bytes 04-build_abe-gcc/console.log.xz | Bin 236016 -> 235568 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8760 -> 8824 bytes 07-build_abe-glibc/console.log.xz | Bin 233460 -> 233700 bytes 08-build_abe-gdb/console.log.xz | Bin 47104 -> 46584 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3776 -> 3768 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4724 -> 4416 bytes 11-check_regression/console.log.xz | Bin 2696 -> 3352 bytes 11-check_regression/mail-body.txt | 15 +- 11-check_regression/results.compare | 30 + 11-check_regression/results.compare2 | 1 + 12-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 17 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/gdb.log.0.xz | Bin 2936808 -> 2961736 bytes sumfiles/gdb.log.1.xz | Bin 143060 -> 139020 bytes sumfiles/gdb.log.10.xz | Bin 10356 -> 0 bytes sumfiles/gdb.log.11.xz | Bin 10340 -> 0 bytes sumfiles/gdb.log.12.xz | Bin 10144 -> 0 bytes sumfiles/gdb.log.13.xz | Bin 10120 -> 0 bytes sumfiles/gdb.log.2.xz | Bin 21016 -> 12340 bytes sumfiles/gdb.log.3.xz | Bin 19484 -> 10256 bytes sumfiles/gdb.log.4.xz | Bin 10264 -> 10240 bytes sumfiles/gdb.log.5.xz | Bin 10280 -> 10312 bytes sumfiles/gdb.log.6.xz | Bin 10204 -> 10184 bytes sumfiles/gdb.log.7.xz | Bin 10072 -> 0 bytes sumfiles/gdb.log.8.xz | Bin 10260 -> 0 bytes sumfiles/gdb.log.9.xz | Bin 10340 -> 0 bytes sumfiles/gdb.sum | 73 +- sumfiles/gdb.sum.0 | 88 +- sumfiles/gdb.sum.1 | 464 +++---- sumfiles/gdb.sum.10 | 2215 --------------------------------- sumfiles/gdb.sum.11 | 2164 -------------------------------- sumfiles/gdb.sum.12 | 2189 -------------------------------- sumfiles/gdb.sum.13 | 2173 -------------------------------- sumfiles/gdb.sum.2 | 490 +------- sumfiles/gdb.sum.3 | 537 ++------ sumfiles/gdb.sum.4 | 32 +- sumfiles/gdb.sum.5 | 27 +- sumfiles/gdb.sum.6 | 47 +- sumfiles/gdb.sum.7 | 2138 ------------------------------- sumfiles/gdb.sum.8 | 2179 -------------------------------- sumfiles/gdb.sum.9 | 2178 -------------------------------- 50 files changed, 456 insertions(+), 16667 deletions(-) create mode 100644 11-check_regression/results.compare create mode 100644 11-check_regression/results.compare2 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.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.7 delete mode 100644 sumfiles/gdb.sum.8 delete mode 100644 sumfiles/gdb.sum.9