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 4cad7cbd18 262: onsuccess: #146: 1: [TCWG CI] https://ci.linaro.org/job [...] discards 51b6d3b185 261: onsuccess: #145: 1: [TCWG CI] https://ci.linaro.org/job [...] discards 8013bb438d 260: force: #144: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] discards 62c3fdd224 259: onsuccess: #143: 1: [TCWG CI] https://ci.linaro.org/job [...] discards 04faba9a20 258: onsuccess: #136: 1: [TCWG CI] Success after binutils/gc [...] discards e7b268344e 257: onsuccess: #135: 1: [TCWG CI] Success after binutils/gc [...] discards d66d5f19ba 256: onsuccess: #134: 1: [TCWG CI] Success after binutils/gc [...] discards 673d8d10ab 255: force: #133: 1: [TCWG CI] Success after baseline build: [...] discards 3060029853 254: onsuccess: #132: 1: [TCWG CI] Success after gdb: 2 commits discards 13444a85f7 253: force: #131: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards 76715b3994 252: force: #130: 1: [TCWG CI] Success after gdb: 15 commits discards e581edf48a 251: onsuccess: #129: 1: [TCWG CI] Success after linux: 121 commits discards 7bcab078de 250: onsuccess: #128: 1: [TCWG CI] Success after glibc: 2 commits discards c2f9f2ab15 249: onsuccess: #127: 1: [TCWG CI] Success after gcc: 98 commits discards da85863419 248: onsuccess: #121: 1: [TCWG CI] Success after binutils/gc [...] discards e3a09bcb76 247: force: #120: 1: [TCWG CI] Success after baseline build: [...] discards 7a75054eb7 246: onsuccess: #118: 1: [TCWG CI] Success after glibc: 7 commits discards f82732eb98 245: onsuccess: #117: 1: [TCWG CI] Success after gcc: 16 commits discards a533d6d3e8 244: onsuccess: #112: 1: [TCWG CI] Success after binutils/gc [...] discards 58356a0c7f 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/gc [...] discards 7f1c753fde 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits discards a99d686999 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/gc [...] discards a3e96a42a7 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/gc [...] discards d388227a38 239: force: #106: 1: [TCWG CI] Success after baseline build: [...] discards a859efe946 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards 49b51b48f8 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits discards 3bcbff7897 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 22 [...] discards 121698b95b 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards 93dd450bcc 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 2f0fdb5722 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 1a7b397367 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 6b5365541a 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits discards 0401382cfb 230: onsuccess: #78: 1: Success after gdb: 2 commits discards 579b611da4 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g4 [...] discards b54760a82d 228: force: #74: 1: Success after gdb: 53 commits discards 822bc39eaf 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards fe0f4ff61b 226: force: #70: 1: Success after baseline build: no new commits discards bf6feabfe8 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g4 [...] discards 4692fc98c7 224: force: #65: 1: Success after gdb: 50 commits discards a260ce8cdd 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g2 [...] discards e0a41820aa 222: force: #60: 1: Success after gdb: 16 commits discards e4b824a38e 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g6 [...] discards 2ef88fd04f 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02ddb [...] discards 566a757485 219: force: #50: 1: Failure after linux: 2520 commits discards 8aba1bc236 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g3 [...] discards c6052df0f5 217: force: #45: 1: Success after linux: 1 commits discards e93624ee8c 216: force: #43: : Failure after baseline build: no new commits discards ff579b89fc 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g1 [...] discards 03a8fcb880 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g1 [...] discards b0283c3652 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 8790286f05 212: force: #27: : Failure after baseline build: no new commits discards a0c5d9827e 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards e0217bf1c3 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 87fcba9517 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 13a510bfee 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards d9c35036bb 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 2557e03e9b 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards a072d24006 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards e71f09b653 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards e4197181a4 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards f8b4985722 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 7a6e18a926 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 8d11759a4e 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 20aa76be9b 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards a7c1248837 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards ecb41a768e 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 439b7c2e0c 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 9f56f800fd 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards b0a612466a 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 7f9043a18a 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 7733d3c03e 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards 1dda38ccdb 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] discards 550601a974 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards 3cc369ebdf 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] discards fca21a05e2 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] discards 9bf50f8336 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] discards 8b41d16a32 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] discards c59619e85e 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] discards 5ab3b0e76b 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] discards bce220d40f 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] discards 031af1cd23 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] discards aaabde51d5 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards e0414e7435 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] discards 6c3db44a11 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] discards 16110c4dfb 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] discards 180634be04 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] discards 399b79de69 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards cd3eb183b5 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards 419cad3ceb 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards d96be700d2 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] discards 8881cf9f05 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] discards e16cf6face 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards d92c755392 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] discards 62b2e421de 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards 6cd956dc33 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards dccd764cd6 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards 5b97b0c705 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards 8ae5422150 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 088c6d47f8 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] discards b3029a1d60 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards 41d1789fe8 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new a813e04d3b 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new d4104b8e3a 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new 3aeb54fc54 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] new 2f5012d119 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 71cffd7843 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new aa2634de5e 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new 7948f29606 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new 3bb0bb4f00 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new d49f013333 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] new 318be56140 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new f722a6cba2 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] new 4d1f9b9210 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] new b50eebed55 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new e3e707e95c 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new 14e8ce7261 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new dee1321d85 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] new 9b53dc1e2f 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] new 51a96112cf 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] new ced0f88c50 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] new db850d4ca6 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 35d090bac2 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] new 2f9bee385f 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] new ca43071200 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] new 6c59b17b13 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] new 3c7917152d 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] new 8c74c61ae7 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] new a36ceaa6c3 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] new f6745487a4 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] new ce50532f20 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new 4a324ec01a 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] new e3ffd23884 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new edba8bb8b5 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 504d7b6040 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 5d41286f11 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 4a19272668 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 381375dac0 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 564d024bc2 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 7a89e1e39a 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new e03d0016e9 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new ed22dab5a4 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 4290915c61 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 249181bf0f 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 8ae887d8f6 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 77bbbfd043 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 1e88c36885 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new d4545a6f6f 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 928e49a6da 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 83e5cdcfd9 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 2ebd9e0edd 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 37ec7da6b5 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new c61b434a45 212: force: #27: : Failure after baseline build: no new commits new 34ee60a135 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 38c0d7ad78 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g1 [...] new 0bfefbb007 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g1 [...] new 8265f88c98 216: force: #43: : Failure after baseline build: no new commits new ab70d9ae56 217: force: #45: 1: Success after linux: 1 commits new 02f63395f7 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g3 [...] new 23ea8d9e22 219: force: #50: 1: Failure after linux: 2520 commits new d27daed8a6 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02ddb [...] new 6f10c7cf68 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g6 [...] new d11d0e5937 222: force: #60: 1: Success after gdb: 16 commits new f8e37e2e01 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g2 [...] new 464ea28858 224: force: #65: 1: Success after gdb: 50 commits new 48ead27c17 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g4 [...] new 01f740ccac 226: force: #70: 1: Success after baseline build: no new commits new bab634321f 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 531c0aa1ed 228: force: #74: 1: Success after gdb: 53 commits new d4bd456ea4 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g4 [...] new 3b3ee380d7 230: onsuccess: #78: 1: Success after gdb: 2 commits new 932793954a 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits new d80b60d483 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 8c7e03860b 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 2c98fd4c08 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new a82733d2f4 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new 4aba23ef0b 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 22 [...] new d6aa480edb 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits new e06ca4a89c 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new 64c3396f80 239: force: #106: 1: [TCWG CI] Success after baseline build: [...] new 7c3020eef6 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/gc [...] new 0e3d452309 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/gc [...] new fd2c3faa0b 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits new f474e43762 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/gc [...] new 81e76587d7 244: onsuccess: #112: 1: [TCWG CI] Success after binutils/gc [...] new 0a93f86118 245: onsuccess: #117: 1: [TCWG CI] Success after gcc: 16 commits new efdca239aa 246: onsuccess: #118: 1: [TCWG CI] Success after glibc: 7 commits new 14fe3553e2 247: force: #120: 1: [TCWG CI] Success after baseline build: [...] new e60a12555f 248: onsuccess: #121: 1: [TCWG CI] Success after binutils/gc [...] new 3599eaf050 249: onsuccess: #127: 1: [TCWG CI] Success after gcc: 98 commits new de6e220dcf 250: onsuccess: #128: 1: [TCWG CI] Success after glibc: 2 commits new 356f4ec47a 251: onsuccess: #129: 1: [TCWG CI] Success after linux: 121 commits new e6e4514be8 252: force: #130: 1: [TCWG CI] Success after gdb: 15 commits new 2e99270bfe 253: force: #131: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new 9ef72ca3aa 254: onsuccess: #132: 1: [TCWG CI] Success after gdb: 2 commits new d2fbba451d 255: force: #133: 1: [TCWG CI] Success after baseline build: [...] new 4548646df7 256: onsuccess: #134: 1: [TCWG CI] Success after binutils/gc [...] new e32f6dfa89 257: onsuccess: #135: 1: [TCWG CI] Success after binutils/gc [...] new c602d5ff5d 258: onsuccess: #136: 1: [TCWG CI] Success after binutils/gc [...] new 53902f4c07 259: onsuccess: #143: 1: [TCWG CI] https://ci.linaro.org/job [...] new d5fd6d13bf 260: force: #144: 1: [TCWG CI] https://ci.linaro.org/job/tcw [...] new 078afa0222 261: onsuccess: #145: 1: [TCWG CI] https://ci.linaro.org/job [...] new bfb77ea47f 262: onsuccess: #146: 1: [TCWG CI] https://ci.linaro.org/job [...] new 64be7a05a2 263: force: #154: : [TCWG CI] https://ci.linaro.org/job/tcwg [...]
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 (4cad7cbd18) \ 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 2020 -> 2232 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2536 bytes 03-build_abe-binutils/console.log.xz | Bin 48596 -> 48868 bytes 04-build_abe-gcc/console.log.xz | Bin 235188 -> 236452 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8772 -> 8900 bytes 07-build_abe-glibc/console.log.xz | Bin 232524 -> 233044 bytes 08-build_abe-gdb/console.log.xz | Bin 47144 -> 46444 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3848 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4608 -> 1328 bytes 10-build_abe-check_gdb/flaky.xfail | 1 + 11-check_regression/console.log.xz | Bin 3548 -> 952 bytes 11-check_regression/results.compare | 7 - 11-check_regression/results.compare2 | 347 - 11-check_regression/results.regressions | 3 + 12-update_baseline/console.log | 59 +- jenkins/notify.sh | 2 +- mail/check-regression-status.txt | 2 +- mail/results.compare | 7 - manifest.sh | 23 +- results | 5 +- sumfiles/gdb.log.0.xz | Bin 2915808 -> 0 bytes sumfiles/gdb.log.1.xz | Bin 133340 -> 0 bytes sumfiles/gdb.log.10.xz | Bin 9988 -> 0 bytes sumfiles/gdb.log.11.xz | Bin 9972 -> 0 bytes sumfiles/gdb.log.12.xz | Bin 10036 -> 0 bytes sumfiles/gdb.log.13.xz | Bin 10028 -> 0 bytes sumfiles/gdb.log.14.xz | Bin 10072 -> 0 bytes sumfiles/gdb.log.15.xz | Bin 9856 -> 0 bytes sumfiles/gdb.log.2.xz | Bin 11608 -> 0 bytes sumfiles/gdb.log.3.xz | Bin 10072 -> 0 bytes sumfiles/gdb.log.4.xz | Bin 9888 -> 0 bytes sumfiles/gdb.log.5.xz | Bin 9864 -> 0 bytes sumfiles/gdb.log.6.xz | Bin 9924 -> 0 bytes sumfiles/gdb.log.7.xz | Bin 10048 -> 0 bytes sumfiles/gdb.log.8.xz | Bin 10076 -> 0 bytes sumfiles/gdb.log.9.xz | Bin 9984 -> 0 bytes sumfiles/gdb.sum | 99736 ------------------------------ sumfiles/gdb.sum.0 | 99736 ------------------------------ sumfiles/gdb.sum.1 | 8100 --- sumfiles/gdb.sum.10 | 2186 - sumfiles/gdb.sum.11 | 2194 - sumfiles/gdb.sum.12 | 2171 - sumfiles/gdb.sum.13 | 2180 - sumfiles/gdb.sum.14 | 2190 - sumfiles/gdb.sum.15 | 2173 - sumfiles/gdb.sum.2 | 2173 - sumfiles/gdb.sum.3 | 2183 - sumfiles/gdb.sum.4 | 2169 - sumfiles/gdb.sum.5 | 2192 - sumfiles/gdb.sum.6 | 2196 - sumfiles/gdb.sum.7 | 2172 - sumfiles/gdb.sum.8 | 2190 - sumfiles/gdb.sum.9 | 2176 - 54 files changed, 49 insertions(+), 238524 deletions(-) create mode 100644 10-build_abe-check_gdb/flaky.xfail delete mode 100644 11-check_regression/results.compare delete mode 100644 11-check_regression/results.compare2 create mode 100644 11-check_regression/results.regressions delete mode 100644 mail/results.compare 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.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.15.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.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.15 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