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 dd0ee1ca93e 222: force: #60: 1: Success after gdb: 16 commits discards 78c06658fda 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] discards 6ed041e5075 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] discards a78d6cf4023 219: force: #50: 1: Failure after linux: 2520 commits discards c1dfbb1e0a0 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] discards c1a07c20779 217: force: #45: 1: Success after linux: 1 commits discards 787a4103359 216: force: #43: : Failure after baseline build: no new commits discards 1ab0d71c248 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 0927d5ba587 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 5043cccf4db 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards befa33b9700 212: force: #27: : Failure after baseline build: no new commits discards 2a366154225 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 59c8f05f39c 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 47d509d9500 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 553bdfc815d 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards aa66c814098 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 1cb8a86a4d8 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 4b1fdd570b7 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 68fd83baa78 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 6e5651af2d0 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 239b1c98c6f 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 06b040e6e78 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards e3eb58ed316 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 526c3a8e73a 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 844a67e4bef 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 2b8f4508832 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards a93304f19ce 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 7f515203b78 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards e9f03d575e0 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 118752d3fd3 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 73aef8aa430 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 89726698160 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 645c0db4833 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards ed1dc937f8c 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards 706118541be 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards 2523d8612bf 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 910e8f04566 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards 28045495bc8 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards 87435fd29a0 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 3eae43b1961 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 17766137f3c 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 156b06ed48a 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 340c7653e44 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards e45fa26f79a 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards 173d4476008 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 74ec54da26d 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 942fce2a5da 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards ae0fe21e5b9 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 1d7081240c4 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards fdc28085130 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 26eb7b67e64 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 7e6935922c2 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards f6f1b7518fc 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards c5e6c8559a4 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 64fbb3c1ba3 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 03dea317819 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards e92a93ec89d 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards a68391e52f6 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards dbed61e82a1 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards a3b5f93d8a6 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards d792d762ac3 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 261231ebf55 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards eacae59b83c 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards b7f1607a6bb 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 16486c599af 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards f72ec504448 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 8effcc911d8 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 06577a1be3d 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 474772e7c0c 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards 613747f55c2 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards fd0b15a6694 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 4a077d82542 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards ba617340acf 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 7d98ed1ca5f 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 1b259cfbef4 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 17196588f88 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards 256729f3042 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards 4b721e31198 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 06dd4fb2fbb 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards d46a1b0ea97 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 1e37a933538 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 480eab6d795 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards c3e65fb6cbd 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards ac99098f702 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 914eb26f771 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards eaaa3911e8f 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards 57ec07ede44 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards b993c3d303a 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards f5b60fbc060 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 93278a44c37 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 018fea9e3d5 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards b9cfc33ac3d 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards 765a48d1ce0 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards 7a89714b7be 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards e34104f0b49 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 88240a506a1 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 06db7252b7b 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 3d57354fd25 125: onsuccess: #614: 1: Success after linux: 12 commits discards ae5ed12bab8 124: onsuccess: #612: 1: Success after binutils: 18 commits discards b0b3c2911f0 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 28800a97e87 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new ddde3623494 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 968e24eb572 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new d4bea1b71f6 124: onsuccess: #612: 1: Success after binutils: 18 commits new f9d46409131 125: onsuccess: #614: 1: Success after linux: 12 commits new ef1833682d0 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 56d6ecacd5c 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 8286a02742a 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new e0cd19f44ba 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 8cad1ee59ad 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new 0b27ba3794b 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 16add6241e6 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 1149bd3d64b 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new b558b23fe87 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 9ffe0a9ed23 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 585ee0b556e 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 6b476fca3b0 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 4d2df565175 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 2109aaa185b 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new df1ff6cf443 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new f5e62d68e19 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 9b635d4b790 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 220559cb486 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 7d73f9e7c63 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new ce4a6513db1 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 461558dfa93 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 567127904c5 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new 9daa074f90a 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 6306f82df6c 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 000d5c99023 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 4e996a43332 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 57087b3b76f 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new 1c999adc42f 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 73a2290bb44 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new 767ae4939b5 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 661a8fe411e 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new a9b1473fac1 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new a7b36ef7b5b 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 18e18ff28d5 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 53405e50f1a 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 716cb3c9a59 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 4adb0571cb1 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 525136267b3 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 5fd8dbeeea9 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new 2f6d4d85995 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 7fe4e0f13b9 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 4294ddda11c 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 0d7583ffb5f 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 637579edfae 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new c0b938e2108 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new f16d737b5f4 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new b96444751ea 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 80288974e63 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new 7e01ab61b41 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 86ad5e8e8c0 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 6626336cf2b 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 9106fc50bd7 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new e09be13d13c 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 28e8b9ba655 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 5f4f1adff7d 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new f2ddcf4e2d9 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new dd33c1cd15b 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 08438775d13 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 67546a791d4 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new c8099b38897 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 6c411da8691 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new c9605622626 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new 057a9b18d35 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new 8d82d299bcf 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new b1e40df860a 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 33abfb68c88 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new df98b3ad609 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 27ec94f5481 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 996f829ee1b 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new abb2ede7267 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new e10135d7ba3 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new ac74fa60b77 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 28d2cfa1c2a 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 592d7c1c493 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 57186f9ebfe 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 2f7ddeaf469 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 7796499d2d3 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 23f56cbae7c 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new d1c3909bab4 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 322662ce43f 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 1b76ed4a7b1 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 77dbb4efbd9 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new d2137e1cbfb 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new fdb65b13d27 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 77a0d7f43d0 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 1998240b733 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new c5a04ce66a9 212: force: #27: : Failure after baseline build: no new commits new b433203af9d 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 41152e95863 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] new 0a6d7a90fb2 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] new b6c1c9c2bb1 216: force: #43: : Failure after baseline build: no new commits new 91cc950b931 217: force: #45: 1: Success after linux: 1 commits new 8689f8aa97b 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] new 18f9a039bac 219: force: #50: 1: Failure after linux: 2520 commits new 7184c4772de 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] new e075be965de 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] new b5b344afd64 222: force: #60: 1: Success after gdb: 16 commits new 33353c897a3 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-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 (dd0ee1ca93e) \ 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 2052 -> 2328 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2560 bytes 03-build_abe-binutils/console.log.xz | Bin 49000 -> 49216 bytes 04-build_abe-gcc/console.log.xz | Bin 235968 -> 235976 bytes 06-build_abe-linux/console.log.xz | Bin 8588 -> 8596 bytes 07-build_abe-glibc/console.log.xz | Bin 233684 -> 233332 bytes 08-build_abe-gdb/console.log.xz | Bin 47232 -> 47088 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3772 -> 3792 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4700 -> 5048 bytes 11-check_regression/console.log.xz | Bin 3208 -> 4508 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 60 + 11-check_regression/mail-body.txt | 70 +- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results.compare | 63 +- 11-check_regression/results.regressions | 68 + 11-check_regression/trigger-bisect | 3 + 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- jenkins/mail-body.draft | 627 +++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/mail-body-header.txt | 103 ++ mail/mail-body.txt | 70 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 68 + sumfiles/gdb.log.0.xz | Bin 2959316 -> 2937628 bytes sumfiles/gdb.log.1.xz | Bin 138376 -> 146400 bytes sumfiles/gdb.log.10.xz | Bin 10096 -> 0 bytes sumfiles/gdb.log.11.xz | Bin 10364 -> 0 bytes sumfiles/gdb.log.12.xz | Bin 10272 -> 0 bytes sumfiles/gdb.log.13.xz | Bin 10108 -> 0 bytes sumfiles/gdb.log.14.xz | Bin 10132 -> 0 bytes sumfiles/gdb.log.2.xz | Bin 11924 -> 16692 bytes sumfiles/gdb.log.3.xz | Bin 10084 -> 10228 bytes sumfiles/gdb.log.4.xz | Bin 10364 -> 10156 bytes sumfiles/gdb.log.5.xz | Bin 10080 -> 10036 bytes sumfiles/gdb.log.6.xz | Bin 10144 -> 10120 bytes sumfiles/gdb.log.7.xz | Bin 10192 -> 10076 bytes sumfiles/gdb.log.8.xz | Bin 10108 -> 10200 bytes sumfiles/gdb.log.9.xz | Bin 10160 -> 0 bytes sumfiles/gdb.sum | 157 +-- sumfiles/gdb.sum.0 | 169 +-- sumfiles/gdb.sum.1 | 485 ++++++- sumfiles/gdb.sum.10 | 2165 ------------------------------ sumfiles/gdb.sum.11 | 2163 ------------------------------ sumfiles/gdb.sum.12 | 2166 ------------------------------ sumfiles/gdb.sum.13 | 2165 ------------------------------ sumfiles/gdb.sum.14 | 2167 ------------------------------ sumfiles/gdb.sum.2 | 338 ++++- sumfiles/gdb.sum.3 | 47 +- sumfiles/gdb.sum.4 | 35 +- sumfiles/gdb.sum.5 | 13 +- sumfiles/gdb.sum.6 | 49 +- sumfiles/gdb.sum.7 | 12 +- sumfiles/gdb.sum.8 | 39 +- sumfiles/gdb.sum.9 | 2178 ------------------------------- 61 files changed, 2262 insertions(+), 13310 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions create mode 100644 11-check_regression/trigger-bisect create mode 100644 11-check_regression/trigger-notify create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh create mode 100644 mail/mail-body-header.txt 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.14.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.14 delete mode 100644 sumfiles/gdb.sum.9