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 be6ffff94a6 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] discards e0fd1abe2d9 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 3f3af572547 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 6a59dea581c 212: force: #27: : Failure after baseline build: no new commits discards 5b4df69c2de 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 0a2d2ba1427 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 5f151ee0daf 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 2e69edaa8a4 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 53711780cda 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 7361c638c14 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 1176cd78011 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 93cbc797fab 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 904e35c3bac 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 184f019e6f8 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards d897b056a02 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 12b9ea052df 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 2af06e2af3c 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 409eaac3fa4 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards d62dfe7b4b7 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards d3fa66a85e9 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 510ea180a20 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 34106660cac 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards eef1f9981d0 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards a9e98eade72 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards d6166673763 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 81e0b245d0b 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards e0b707e6cc3 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards 24249afcc3d 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards 498a01db58c 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards ca7d21ba569 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards 46266d10abf 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards 9f413271c8c 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards d58c996e711 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 273b1a03225 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards d6ce07956d0 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 56f93bda7c7 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards 5e23d305f45 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards efd5d7a7edd 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards ddf2a633661 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 4faa2275c56 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards fe689566a3f 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards b5dab1eac4b 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 93e253da40a 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards f84b1de5b4d 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 3532fb5052b 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards c96298603b5 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards abb5a803317 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards c04843de1fe 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards b8617b672f2 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards c72e655ba96 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 448df9aa54e 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 60314f12fa0 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards fa7e5b6355d 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 539ac98d776 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 8c19a7ba8d0 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards aa4e7546416 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 7396f172cd6 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 4f2446dfa25 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 536f412b1b3 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 3a7f28b7950 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 52816f29693 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 733196e97b5 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards 3914b5ba861 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards f51b0e41df1 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards d35deb21e66 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 33415e61c72 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards ef98c227dcf 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards c5311fed3a7 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 89481e6e8aa 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards a7a81396f4e 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards b515a8b5d0e 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 4a4adbb06a7 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards 237ebd1f843 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards acf4c2f2e18 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards cea4187c9ab 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 458f1f8de32 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 7e528734414 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 9e75fd1f546 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 1a9636028e0 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards b824089da42 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 22848d4dbec 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 17745b5c2ae 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards f4a843ded62 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 450e52959ce 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 7657f8d171f 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards 096b69cb1b2 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards c9bf2ca354f 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards db7ef450eda 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards f83b48b17d9 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 1ecfdb2f43c 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 6216b935bdf 125: onsuccess: #614: 1: Success after linux: 12 commits discards eff34c37e89 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 4434866a020 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 1a3bf00b224 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards b488b746bad 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 9535f7b5d00 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 8d14662ff63 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 4bd69a6efc2 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 0041327816f 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards d64999d5bf4 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 02a06683ed9 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 2e05c0d9608 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new f048413e693 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new c2e760b0d5a 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new f3cad6324a7 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new bacd929f33a 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new f77f55a9e0a 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new b6d49fa56a1 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 20d51e3bbb8 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new a2b1d7c5108 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 070d8baa636 124: onsuccess: #612: 1: Success after binutils: 18 commits new 9af5ab70c72 125: onsuccess: #614: 1: Success after linux: 12 commits new c67b5b9ddb8 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 34dde2bcbe6 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new aea00c3e0fa 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new c5e66354ebc 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new c4082c22454 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new 775b6aed7aa 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new aeacd8f3a3a 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 22340aaedc8 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new 7a69f1d345b 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 1c077755ca9 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 4002cdf08a9 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 6bc026bac10 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 091b661aa15 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 49f3679f6f8 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 2d26818d2b4 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 239f6f34af9 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new ca06e61b37d 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new b606ee0bbb3 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new ab51a342844 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new 8f9300fb37d 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 14c5c601fda 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new f6f5286d556 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new ae61f78e240 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new ebbcb46ca58 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new c2a249fa308 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 9bba9f2babd 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new defd07b4b55 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new 5e952d3f32f 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 668e5d66db9 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new 34dd5af6cd8 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new a0a284463c6 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 5979dccc077 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 9132eeff235 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 42d55903a43 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 47d7bbec53d 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new e470c9b5fee 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new bbecd11af73 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new fac6e05c60b 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 23a72e75b6f 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new 84db066327d 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 313b66f5002 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 09821e244c2 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new af9398f8647 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new e5f376b90e7 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new b874e3b52ef 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new 6af04736265 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 5befc09354b 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new b5fd6e66ca8 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new 2aa6efa45b9 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new f9f1274ca5e 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new da94ab32d26 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new ff7656a63de 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new bceb7d29cdb 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new d6d37b78fc2 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 083a2fb488f 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new ee22bc2bba7 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 1f7e36b672b 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new cd5f9d25b97 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 9fb7e1421c4 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new 9b9550ab052 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new e15ca5fe0c7 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new c9bf26f828c 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new c5fe6954e98 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new f8649a64468 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new f4bde0d63ef 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new de1ca618519 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 533715e9e71 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new c550fd30149 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 8345af05985 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 96585149247 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 5ed4895ee02 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new dc53397d416 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 27ba32fe9a1 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new fa2922b5427 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new ba39fa4e84a 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new ab5caec4479 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new d2edb22c24e 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 9afa76020fd 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 958ad02f5fa 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 7a2cfdf2edf 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new a93da2a991e 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 0f3a27982f5 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new d48efd0098f 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 82356721278 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new c0468cc0d01 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new b102f214bca 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 6c927869026 212: force: #27: : Failure after baseline build: no new commits new def1efcd228 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 8d4c5d2796b 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] new 5b759cd207d 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] new c7abaf49baa 216: force: #43: : Failure after baseline build: no new 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 (be6ffff94a6) \ 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 2264 -> 2304 bytes 02-prepare_abe/console.log.xz | Bin 2524 -> 2496 bytes 03-build_abe-binutils/console.log.xz | Bin 49036 -> 1004 bytes 04-build_abe-gcc/console.log.xz | Bin 235172 -> 0 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 0 bytes 06-build_abe-linux/console.log.xz | Bin 8668 -> 0 bytes 07-build_abe-glibc/console.log.xz | Bin 233964 -> 0 bytes 08-build_abe-gdb/console.log.xz | Bin 46660 -> 0 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3772 -> 0 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4592 -> 0 bytes 11-check_regression/console.log.xz | Bin 4456 -> 2504 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 8 - 11-check_regression/mail-body.txt | 69 +- 11-check_regression/results.compare | 41 - 11-check_regression/results.compare2 | 1 - 11-check_regression/results.regressions | 43 +- 11-check_regression/trigger-bisect | 3 - 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 58 +- dashboard/dashboard-generate.sh | 2 +- .../squad-vs-first/score/results-functional.json | 1 - jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 189 - jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 2 +- mail/mail-body.txt | 71 +- mail/mail-subject.txt | 2 +- manifest.sh | 23 +- results | 57 +- sumfiles/gdb.log.0.xz | Bin 2809052 -> 0 bytes sumfiles/gdb.log.1.xz | Bin 138604 -> 0 bytes sumfiles/gdb.log.10.xz | Bin 10132 -> 0 bytes sumfiles/gdb.log.2.xz | Bin 16808 -> 0 bytes sumfiles/gdb.log.3.xz | Bin 11344 -> 0 bytes sumfiles/gdb.log.4.xz | Bin 10316 -> 0 bytes sumfiles/gdb.log.5.xz | Bin 10136 -> 0 bytes sumfiles/gdb.log.6.xz | Bin 10312 -> 0 bytes sumfiles/gdb.log.7.xz | Bin 10360 -> 0 bytes sumfiles/gdb.log.8.xz | Bin 10396 -> 0 bytes sumfiles/gdb.log.9.xz | Bin 10132 -> 0 bytes sumfiles/gdb.sum | 100026 ------------------ sumfiles/gdb.sum.0 | 100022 ----------------- sumfiles/gdb.sum.1 | 8249 -- sumfiles/gdb.sum.10 | 2169 - sumfiles/gdb.sum.2 | 2401 - sumfiles/gdb.sum.3 | 2162 - sumfiles/gdb.sum.4 | 2172 - sumfiles/gdb.sum.5 | 2173 - sumfiles/gdb.sum.6 | 2162 - sumfiles/gdb.sum.7 | 2187 - sumfiles/gdb.sum.8 | 2194 - sumfiles/gdb.sum.9 | 2174 - 55 files changed, 54 insertions(+), 228617 deletions(-) delete mode 100644 04-build_abe-gcc/console.log.xz delete mode 100644 05-clean_sysroot/console.log.xz delete mode 100644 06-build_abe-linux/console.log.xz delete mode 100644 07-build_abe-glibc/console.log.xz delete mode 100644 08-build_abe-gdb/console.log.xz delete mode 100644 09-build_abe-dejagnu/console.log.xz delete mode 100644 10-build_abe-check_gdb/console.log.xz delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.compare delete mode 100644 11-check_regression/results.compare2 delete mode 100644 11-check_regression/trigger-bisect delete mode 100644 11-check_regression/trigger-notify delete mode 100644 dashboard/squad-vs-first/score/results-functional.json delete mode 100644 jenkins/jira-status.draft delete mode 100644 jenkins/mail-body.draft delete mode 100644 jenkins/mail-recipients.draft delete mode 100644 jenkins/mail-subject.draft delete mode 100755 jenkins/notify.sh delete mode 100644 sumfiles/gdb.log.0.xz delete mode 100644 sumfiles/gdb.log.1.xz delete mode 100644 sumfiles/gdb.log.10.xz delete mode 100644 sumfiles/gdb.log.2.xz delete mode 100644 sumfiles/gdb.log.3.xz delete mode 100644 sumfiles/gdb.log.4.xz delete mode 100644 sumfiles/gdb.log.5.xz delete mode 100644 sumfiles/gdb.log.6.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 delete mode 100644 sumfiles/gdb.sum.0 delete mode 100644 sumfiles/gdb.sum.1 delete mode 100644 sumfiles/gdb.sum.10 delete mode 100644 sumfiles/gdb.sum.2 delete mode 100644 sumfiles/gdb.sum.3 delete mode 100644 sumfiles/gdb.sum.4 delete mode 100644 sumfiles/gdb.sum.5 delete mode 100644 sumfiles/gdb.sum.6 delete mode 100644 sumfiles/gdb.sum.7 delete mode 100644 sumfiles/gdb.sum.8 delete mode 100644 sumfiles/gdb.sum.9