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 93c1b87ef2 252: force: #130: 1: [TCWG CI] Success after gdb: 15 commits discards c6912d68bc 251: onsuccess: #129: 1: [TCWG CI] Success after linux: 121 commits discards 328e3daeaf 250: onsuccess: #128: 1: [TCWG CI] Success after glibc: 2 commits discards 9b4e6e1e66 249: onsuccess: #127: 1: [TCWG CI] Success after gcc: 98 commits discards 84a8c7a602 248: onsuccess: #121: 1: [TCWG CI] Success after binutils/gc [...] discards 92c7af6b5a 247: force: #120: 1: [TCWG CI] Success after baseline build: [...] discards 3a60238834 246: onsuccess: #118: 1: [TCWG CI] Success after glibc: 7 commits discards 90af29d0c8 245: onsuccess: #117: 1: [TCWG CI] Success after gcc: 16 commits discards 4f2d078527 244: onsuccess: #112: 1: [TCWG CI] Success after binutils/gc [...] discards 2b0627d95e 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/gc [...] discards c2f082f0e6 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits discards e01fb37282 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/gc [...] discards 2734e73a99 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/gc [...] discards 645acb4be8 239: force: #106: 1: [TCWG CI] Success after baseline build: [...] discards 79faba3bce 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards 05da3939e8 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits discards 4a335a978d 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 22 [...] discards 625b9d4c94 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards f7524e4273 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 8e13a065b8 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 8ad79230a4 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 11cb849c45 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits discards a26702d7e0 230: onsuccess: #78: 1: Success after gdb: 2 commits discards 9b6ddfec74 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g4 [...] discards c51ff4d87e 228: force: #74: 1: Success after gdb: 53 commits discards b681692920 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 31efce909f 226: force: #70: 1: Success after baseline build: no new commits discards 58a5eca170 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g4 [...] discards a980c1a88b 224: force: #65: 1: Success after gdb: 50 commits discards 2843e4aa38 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g2 [...] discards f57a853d7e 222: force: #60: 1: Success after gdb: 16 commits discards 2c8ba275dd 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g6 [...] discards 57b354a6ef 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02ddb [...] discards 3d143af50c 219: force: #50: 1: Failure after linux: 2520 commits discards a0b48aa1b3 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g3 [...] discards c56cbe9023 217: force: #45: 1: Success after linux: 1 commits discards 06aacf94dc 216: force: #43: : Failure after baseline build: no new commits discards 329e216363 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g1 [...] discards ccb7b9d04e 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g1 [...] discards 89f94eaaa1 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards b3cafc8d65 212: force: #27: : Failure after baseline build: no new commits discards 9c3749f395 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 86652947ab 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 76e5112785 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 8517ddb373 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards f591152094 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards c8a3438782 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards e7ca8adb28 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 3f8c64732e 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 905824eb42 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards cc105f6f8d 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 3baa0ef706 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 881e5b18ad 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 51337745f2 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards a512b57da2 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards cd3ea524ad 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 2ae77a1265 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 13b8056a71 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 0244f5e508 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 87abb122f1 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards aa4c3fc99b 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards bac18f4396 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] discards b12075915d 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards be96af7632 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] discards cc87de26de 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] discards 45ef681026 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] discards 77cf98305d 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] discards 881e9d7ebf 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] discards 72f53394be 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] discards 5d1c987cc7 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] discards 1c14e6a3db 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] discards a56373579a 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards abfc56aeea 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] discards 18f9159893 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] discards 58a746735f 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] discards 816acb48ff 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] discards 45f5f5cd9d 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards 02f70994f0 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards fcbf2b03bc 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 3a601003f9 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] discards d07d4b25ab 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] discards 54e150e58f 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards 689cb5d0fa 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] discards d32231c061 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards deeb3cee61 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards 8033b634c8 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards 2d92dde7a2 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards e8c1e423a2 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards fe6be31f9a 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] discards c670987a7d 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards f8b4a62fdb 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards e22e0f3582 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] discards e851666065 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards 27bcc54a16 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards 664906f877 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards 79cd15fa64 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 2c6519f3aa 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards e995b9fb78 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards eb1ff739fe 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] discards ae3ebd666d 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] discards 43b490971b 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new 765c4d1cd8 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new c199916e09 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new f12413cd19 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] new 3ad2d884d1 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 12ac42bd49 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 99c3b893db 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 58c87585b2 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new 573af6c529 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 92cec42a24 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new e8055ce355 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] new 638d2fdd2c 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new d574fde7be 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new 2816bfbfb5 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] new 279e1fd86e 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 089afc7314 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new 756472befa 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new 2bfd0f132d 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new 470c175582 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new 54f705bb98 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] new 17b6138486 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new 6baf38673a 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] new 552316cd54 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] new 5d65cb444a 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new 4474393fea 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new de5170bfab 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new 9c0fc92e11 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] new c747e8d676 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] new 78743bd49a 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] new 7b110092f9 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] new 1d1d3a2896 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 24034ee08e 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] new 673fd1e1ee 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] new 48e100272a 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] new c120af586d 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] new dd73cbec14 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] new 90fd8f9b69 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] new 012e47a97e 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] new 9798793bef 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] new 04a271ffb1 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new 4059a1665f 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] new 476cbc5c71 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new a49977a494 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 26eff09f18 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new d3a602b4a0 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new feb02a56ee 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 1572b2b69a 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 42c1e37299 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 388c86984f 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new fe1d8ddae7 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 0f9221acaa 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new c278664e23 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 59164c0d1e 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 76bdc54233 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 49fbc2e2d2 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 3b78213f5f 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new afbc256190 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 31379d3281 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 45883090a4 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new dabf018996 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 48c33c7e15 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new a16be7fc59 212: force: #27: : Failure after baseline build: no new commits new 674fa80ba5 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new d5cd1ca36f 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g1 [...] new a3df11cfae 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g1 [...] new 0d917b2259 216: force: #43: : Failure after baseline build: no new commits new 4bec5f30ad 217: force: #45: 1: Success after linux: 1 commits new b084900c6d 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g3 [...] new c530cc48f4 219: force: #50: 1: Failure after linux: 2520 commits new b8d9185fa3 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02ddb [...] new 6153179389 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g6 [...] new 0ca793d191 222: force: #60: 1: Success after gdb: 16 commits new b29811e330 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g2 [...] new 0a9a1b20e7 224: force: #65: 1: Success after gdb: 50 commits new 78d5a7fe47 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g4 [...] new 7eb0fd24cc 226: force: #70: 1: Success after baseline build: no new commits new cc61624d1e 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 461ab6c6af 228: force: #74: 1: Success after gdb: 53 commits new fa7af0c1cd 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g4 [...] new 4b4f1bbad0 230: onsuccess: #78: 1: Success after gdb: 2 commits new 1078a97ee4 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits new e5e2f8c26a 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new fbee4a6df0 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new fa9672b5df 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new 718f3adc3c 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new 6065af79b7 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 22 [...] new 3111b822b3 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits new 838cef2bc7 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new 4166f368c6 239: force: #106: 1: [TCWG CI] Success after baseline build: [...] new 396739d674 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/gc [...] new b302436e59 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/gc [...] new ebbe9ce2a5 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits new d41aa24508 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/gc [...] new f3aa839f4d 244: onsuccess: #112: 1: [TCWG CI] Success after binutils/gc [...] new c7b12b40f9 245: onsuccess: #117: 1: [TCWG CI] Success after gcc: 16 commits new a3aa54120b 246: onsuccess: #118: 1: [TCWG CI] Success after glibc: 7 commits new 47ae1d7b0b 247: force: #120: 1: [TCWG CI] Success after baseline build: [...] new e4b85ca3fe 248: onsuccess: #121: 1: [TCWG CI] Success after binutils/gc [...] new 8a4272c790 249: onsuccess: #127: 1: [TCWG CI] Success after gcc: 98 commits new 90d403dccb 250: onsuccess: #128: 1: [TCWG CI] Success after glibc: 2 commits new 0585bca8af 251: onsuccess: #129: 1: [TCWG CI] Success after linux: 121 commits new 98d02b0635 252: force: #130: 1: [TCWG CI] Success after gdb: 15 commits new 0bb077feff 253: force: #131: 1: [TCWG CI] Failure after gdb-13-branchpo [...]
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 (93c1b87ef2) \ 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 2024 -> 2044 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2532 bytes 03-build_abe-binutils/console.log.xz | Bin 49304 -> 49428 bytes 04-build_abe-gcc/console.log.xz | Bin 234416 -> 235124 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8636 -> 8652 bytes 07-build_abe-glibc/console.log.xz | Bin 233472 -> 232872 bytes 08-build_abe-gdb/console.log.xz | Bin 47492 -> 46792 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3804 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4628 -> 4476 bytes 11-check_regression/console.log.xz | Bin 3148 -> 3768 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 10 + 11-check_regression/results.compare | 17 +- 11-check_regression/results.regressions | 18 + 11-check_regression/trigger-bisect | 3 + 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- jenkins/notify.sh | 3 + mail/changes-list-long.txt | 11 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 18 +- mail/short-diag.txt | 2 +- manifest.sh | 16 +- results | 18 + sumfiles/gdb.log.0.xz | Bin 2840672 -> 2888792 bytes sumfiles/gdb.log.1.xz | Bin 142796 -> 143280 bytes sumfiles/gdb.log.10.xz | Bin 10196 -> 0 bytes sumfiles/gdb.log.11.xz | Bin 9776 -> 0 bytes sumfiles/gdb.log.2.xz | Bin 19528 -> 19600 bytes sumfiles/gdb.log.3.xz | Bin 9900 -> 9920 bytes sumfiles/gdb.log.4.xz | Bin 9968 -> 10076 bytes sumfiles/gdb.log.5.xz | Bin 9888 -> 9972 bytes sumfiles/gdb.log.6.xz | Bin 10184 -> 0 bytes sumfiles/gdb.log.7.xz | Bin 9976 -> 0 bytes sumfiles/gdb.log.8.xz | Bin 9928 -> 0 bytes sumfiles/gdb.log.9.xz | Bin 9868 -> 0 bytes sumfiles/gdb.sum | 47 +- sumfiles/gdb.sum.0 | 57 +- sumfiles/gdb.sum.1 | 298 +++-- sumfiles/gdb.sum.10 | 2207 ------------------------------- sumfiles/gdb.sum.11 | 2162 ------------------------------ sumfiles/gdb.sum.2 | 49 +- sumfiles/gdb.sum.3 | 53 +- sumfiles/gdb.sum.4 | 23 +- sumfiles/gdb.sum.5 | 45 +- sumfiles/gdb.sum.6 | 2203 ------------------------------ sumfiles/gdb.sum.7 | 2169 ------------------------------ sumfiles/gdb.sum.8 | 2185 ------------------------------ sumfiles/gdb.sum.9 | 2174 ------------------------------ 52 files changed, 439 insertions(+), 13396 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 100755 jenkins/notify.sh delete mode 100644 sumfiles/gdb.log.10.xz delete mode 100644 sumfiles/gdb.log.11.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.10 delete mode 100644 sumfiles/gdb.sum.11 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