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 c7abaf49baa 216: force: #43: : Failure after baseline build: no new commits discards 5b759cd207d 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 8d4c5d2796b 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] discards def1efcd228 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 6c927869026 212: force: #27: : Failure after baseline build: no new commits discards b102f214bca 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards c0468cc0d01 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 82356721278 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards d48efd0098f 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 0f3a27982f5 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards a93da2a991e 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 7a2cfdf2edf 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 958ad02f5fa 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 9afa76020fd 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards d2edb22c24e 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards ab5caec4479 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards ba39fa4e84a 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards fa2922b5427 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 27ba32fe9a1 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards dc53397d416 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 5ed4895ee02 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 96585149247 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 8345af05985 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards c550fd30149 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 533715e9e71 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards de1ca618519 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards f4bde0d63ef 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards f8649a64468 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards c5fe6954e98 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards c9bf26f828c 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards e15ca5fe0c7 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards 9b9550ab052 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards 9fb7e1421c4 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards cd5f9d25b97 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 1f7e36b672b 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards ee22bc2bba7 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 083a2fb488f 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards d6d37b78fc2 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards bceb7d29cdb 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards ff7656a63de 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards da94ab32d26 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards f9f1274ca5e 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 2aa6efa45b9 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards b5fd6e66ca8 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 5befc09354b 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 6af04736265 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards b874e3b52ef 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards e5f376b90e7 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards af9398f8647 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 09821e244c2 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 313b66f5002 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 84db066327d 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 23a72e75b6f 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards fac6e05c60b 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards bbecd11af73 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards e470c9b5fee 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 47d7bbec53d 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 42d55903a43 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 9132eeff235 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 5979dccc077 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards a0a284463c6 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 34dd5af6cd8 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 668e5d66db9 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards 5e952d3f32f 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards defd07b4b55 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 9bba9f2babd 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards c2a249fa308 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards ebbcb46ca58 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards ae61f78e240 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards f6f5286d556 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards 14c5c601fda 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards 8f9300fb37d 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards ab51a342844 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards b606ee0bbb3 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards ca06e61b37d 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 239f6f34af9 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 2d26818d2b4 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 49f3679f6f8 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 091b661aa15 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 6bc026bac10 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards 4002cdf08a9 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 1c077755ca9 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 7a69f1d345b 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 22340aaedc8 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards aeacd8f3a3a 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 775b6aed7aa 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards c4082c22454 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards c5e66354ebc 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards aea00c3e0fa 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 34dde2bcbe6 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards c67b5b9ddb8 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 9af5ab70c72 125: onsuccess: #614: 1: Success after linux: 12 commits discards 070d8baa636 124: onsuccess: #612: 1: Success after binutils: 18 commits discards a2b1d7c5108 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 20d51e3bbb8 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards b6d49fa56a1 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards f77f55a9e0a 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards bacd929f33a 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards f3cad6324a7 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards c2e760b0d5a 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards f048413e693 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 9b18143bc8e 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 31b4b4475e0 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new a9683c63728 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new e76e6f38b2c 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 7f959ee4577 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new ac62bd43247 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new fec1df42e43 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 806494f7699 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new c1e1a55e356 124: onsuccess: #612: 1: Success after binutils: 18 commits new c75049c19d9 125: onsuccess: #614: 1: Success after linux: 12 commits new 6b22387cc5b 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 7beafd65c75 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 82ed24c3244 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 065d31a96dd 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 5d20dabb57c 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new 6991b5a032b 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new f2c5ce7d58b 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 7802b665f61 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new 12d9c15cfc7 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 1da4e441907 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 8d9e5c1dce9 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 55f314e5164 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 7c0bec45fc5 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new cbed528318a 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new b932f31eabd 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 42ce2ece36b 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new dde21164eae 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new fad6b0e4d5c 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 78ff073c446 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new dd27fec8ba9 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 984b55a4637 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 3c705012138 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new 162406d4fef 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 1a2cc29f9c9 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 3f227461658 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new a720be7faf1 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 19b689ba175 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new dd986c21cf1 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new f9556580f41 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new c016ce70531 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new ae3c24242f0 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new d848e759871 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 3ce6f18626b 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 5357cde04d4 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new a9c739d783e 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 9db898fc279 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new dbbe76ca3a8 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 713160c3b36 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new cab8932a0e9 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new a64a02afc0b 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new d8c13e21083 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new ab7a7b57b8c 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 4e8308f512b 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 4fde1a9a861 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 4e8675123d7 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new cf04f0f8225 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 857fac578b3 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new ce5c7f2dab8 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new 95dd4c137cd 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 450df6c9262 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new e6923459dc6 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 385cd6e2bb7 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 2faaa2f20c7 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 2f228c7a769 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 380e835759b 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new b1191216c65 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new e75fc50fe56 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 4fc2d29a3b3 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 4674d6415b4 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new ee9df97d53c 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 6c6058087fe 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new ff8498e15a1 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new f5fd2dfa67b 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new d7f54d47a60 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 855269bf32e 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 7b89455e4cb 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 83d98c2003e 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 2d1e0b70c6d 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new bdddfa7fc04 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new bfc6f34fb37 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new d2672609a02 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new f9fdc598522 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 99104153d1d 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 6578237e34d 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 53073807105 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 4b92e48c7d0 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 658a050bbcf 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new f195cbdabc4 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 730d7183734 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 6fb4a917ca2 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 2035d505463 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new b981d06063a 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 1c8b6844941 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new d69a4fb8410 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new a1c90007f20 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 04b556c6fb3 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new f9f8982c2b5 212: force: #27: : Failure after baseline build: no new commits new 302668e1c18 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 8813c32db2a 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] new dccbaa559f3 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] new cea68b942a4 216: force: #43: : Failure after baseline build: no new commits new dbc5073212b 217: force: #45: 1: Success after linux: 1 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 (c7abaf49baa) \ 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 2304 -> 1968 bytes 02-prepare_abe/console.log.xz | Bin 2496 -> 2496 bytes 03-build_abe-binutils/console.log.xz | Bin 1004 -> 49128 bytes 04-build_abe-gcc/console.log.xz | Bin 0 -> 236016 bytes 05-clean_sysroot/console.log.xz | Bin 0 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 0 -> 8760 bytes 07-build_abe-glibc/console.log.xz | Bin 0 -> 233460 bytes 08-build_abe-gdb/console.log.xz | Bin 0 -> 47104 bytes 09-build_abe-dejagnu/console.log.xz | Bin 0 -> 3776 bytes 10-build_abe-check_gdb/console.log.xz | Bin 0 -> 4724 bytes 11-check_regression/console.log.xz | Bin 2504 -> 2696 bytes 11-check_regression/jira-body.txt | 2 +- 11-check_regression/mail-body.txt | 55 +- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results.regressions | 2 - 12-update_baseline/console.log | 56 +- dashboard/dashboard-generate.sh | 2 +- .../squad-vs-first/score/results-functional.json | 1 + git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 55 +- mail/mail-subject.txt | 2 +- manifest.sh | 23 +- results | 16 +- sumfiles/gdb.log.0.xz | Bin 0 -> 2936808 bytes sumfiles/gdb.log.1.xz | Bin 0 -> 143060 bytes sumfiles/gdb.log.10.xz | Bin 0 -> 10356 bytes sumfiles/gdb.log.11.xz | Bin 0 -> 10340 bytes sumfiles/gdb.log.12.xz | Bin 0 -> 10144 bytes sumfiles/gdb.log.13.xz | Bin 0 -> 10120 bytes sumfiles/gdb.log.2.xz | Bin 0 -> 21016 bytes sumfiles/gdb.log.3.xz | Bin 0 -> 19484 bytes sumfiles/gdb.log.4.xz | Bin 0 -> 10264 bytes sumfiles/gdb.log.5.xz | Bin 0 -> 10280 bytes sumfiles/gdb.log.6.xz | Bin 0 -> 10204 bytes sumfiles/gdb.log.7.xz | Bin 0 -> 10072 bytes sumfiles/gdb.log.8.xz | Bin 0 -> 10260 bytes sumfiles/gdb.log.9.xz | Bin 0 -> 10340 bytes sumfiles/gdb.sum | 99761 +++++++++++++++++++ sumfiles/gdb.sum.0 | 99757 ++++++++++++++++++ sumfiles/gdb.sum.1 | 8572 ++ sumfiles/gdb.sum.10 | 2215 + sumfiles/gdb.sum.11 | 2164 + sumfiles/gdb.sum.12 | 2189 + sumfiles/gdb.sum.13 | 2173 + sumfiles/gdb.sum.2 | 2661 + sumfiles/gdb.sum.3 | 2609 + sumfiles/gdb.sum.4 | 2160 + sumfiles/gdb.sum.5 | 2161 + sumfiles/gdb.sum.6 | 2198 + sumfiles/gdb.sum.7 | 2138 + sumfiles/gdb.sum.8 | 2179 + sumfiles/gdb.sum.9 | 2178 + 53 files changed, 235196 insertions(+), 139 deletions(-) create mode 100644 04-build_abe-gcc/console.log.xz create mode 100644 05-clean_sysroot/console.log.xz create mode 100644 06-build_abe-linux/console.log.xz create mode 100644 07-build_abe-glibc/console.log.xz create mode 100644 08-build_abe-gdb/console.log.xz create mode 100644 09-build_abe-dejagnu/console.log.xz create mode 100644 10-build_abe-check_gdb/console.log.xz delete mode 100644 11-check_regression/results.regressions create mode 100644 dashboard/squad-vs-first/score/results-functional.json create mode 100644 sumfiles/gdb.log.0.xz create mode 100644 sumfiles/gdb.log.1.xz create mode 100644 sumfiles/gdb.log.10.xz create mode 100644 sumfiles/gdb.log.11.xz create mode 100644 sumfiles/gdb.log.12.xz create mode 100644 sumfiles/gdb.log.13.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.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 create mode 100644 sumfiles/gdb.sum.0 create mode 100644 sumfiles/gdb.sum.1 create mode 100644 sumfiles/gdb.sum.10 create mode 100644 sumfiles/gdb.sum.11 create mode 100644 sumfiles/gdb.sum.12 create mode 100644 sumfiles/gdb.sum.13 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 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