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 73b50b2cb85 230: onsuccess: #78: 1: Success after gdb: 2 commits discards 7cb6833f922 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g [...] discards 1f56396f620 228: force: #74: 1: Success after gdb: 53 commits discards 5101877455b 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] discards 0fa6d38785d 226: force: #70: 1: Success after baseline build: no new commits discards 8ccaaf315f0 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] discards 892da422ffa 224: force: #65: 1: Success after gdb: 50 commits discards f96743f6f57 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] discards a35094b7e4f 222: force: #60: 1: Success after gdb: 16 commits discards f185c6b7368 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] discards 4dee74cc6b6 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] discards 62a6745f1f1 219: force: #50: 1: Failure after linux: 2520 commits discards b6f78fab9a7 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] discards 90252a5c9d6 217: force: #45: 1: Success after linux: 1 commits discards f2d3e9a154d 216: force: #43: : Failure after baseline build: no new commits discards c95c2e0d21e 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 6b6cca93328 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 8787a00621e 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards d3dc3f889bb 212: force: #27: : Failure after baseline build: no new commits discards 992b3c137ea 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards fbac7c0b44f 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 144b293af74 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 237be255142 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards a8ed2f51e69 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 557e3b70a4c 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 7f825e4c152 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 3022aa96bce 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards cbe318a26c1 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 41fce251548 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards b06efa0ecf8 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards e747d481107 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 4799b8abc0f 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 837b805a3b5 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards d3a5d50a75d 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 8efb835b206 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 997f86df36f 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards a461fe1a7fe 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 638d0b23b71 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards c3bb6781464 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 33a590e474c 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 09440d44783 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards a02d6a4c586 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards d5ec857da98 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards f3013aab3a2 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 1bd511feba3 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards 344f0370818 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards d18251dc393 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards ab8079fdd2c 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 0da7666a235 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards d865065c7ed 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 262a2a5d57e 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards 3ffb806cf94 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards 46dfc7b6989 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 3d77550f50c 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards e0a8c2b0b3c 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 29ee549f47c 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards b830a83978a 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards aa205daa26a 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards be5bd0441ee 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 01eb26e3eb2 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards d2ba2c5fb6d 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards 2fe6f1be44d 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 88fa5900b15 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards cfdea43ef81 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards f5947f9d85c 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 9ee49ffcc7e 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards c9e20393df0 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards 57bf3d77874 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 68d904a383f 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 4b5d7e53e67 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 42cfd3857c7 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards e2f6410b940 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards f155fc513a7 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards f524582ae60 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards d099974afc5 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards c010943b0c1 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 711c849e9a9 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards f1ba4c8f42e 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 9b455770bf8 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 69cfc214f46 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 1d58a740227 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards e05e5c5d1bb 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards f265ccd6174 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 169dfeee396 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards 48dfbfc5452 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards 21d94433507 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 29ad9a8e14b 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards bca52960e27 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards d36b88721da 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards f3809aff780 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 620b899fc60 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards b21c0652085 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 8c3410e3f85 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 2b97408e9e8 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards 8ddfa9988fa 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards abf65ee89f7 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 7b8b4080f11 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 856c6e5422a 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 49144a02b4c 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards fbbb4ba903b 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards 6d63f5e6d5b 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new f235c3cc5a5 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new 21df92ea21d 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new a6e4899e55a 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 325a4efa125 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new c355c247d96 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new d8fff820090 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 2bb6e503c32 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 7d8e9835a5a 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 356298aa850 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new c8134c9ff79 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 0c6a791220f 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 432507f5605 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 47881f1d8e1 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new b031020047b 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 06091e8e9f4 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new cc08142dd53 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 4f58fc99118 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 302d74dafbc 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new 978adba5937 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 05568d35dc6 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new b32561f5bb5 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 6a2e3f44e1b 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 3693b4bcecf 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new 58e53bd1103 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new ee0a843d5fd 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new 49b4b9f4273 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new beab48b1fcc 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 04466964537 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 43d65d4fbc5 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 21708fa791f 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 3169b9e0086 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new adad544cfcb 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 1a313b9ac35 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 2f9816751a4 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 394dc782270 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new 4e03864e5a0 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 4c00846d12e 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 81dafb7c2b8 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new af42f0f736b 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 259250547cf 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new fc4bfa199fd 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new 430bdc73101 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 310852dca42 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new c6020674758 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new b8a24010f0c 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new b179ae05a44 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new c3585fd67d9 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 8cceff3798d 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 71df560a079 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 25f87b31cd5 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 4954ab7933f 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new 23e5b0bf41b 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 6d82da5054c 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 76c19a49f8a 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new ba0575bf7fd 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new 6f19cf404f8 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 46a54cf6bae 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new 59ee3771c62 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new 27240afe69b 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new 5cfba8fde42 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 1474590f3e6 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 062843d9248 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 0011c4506aa 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 2e687837379 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 9dce3e0bcae 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 1ac4622912d 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new e6ef9e7e656 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new b268b191408 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 48ac593bd25 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new fb73f935f3e 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 79e66421c9c 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new c2b3dcf71c5 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new d1be582a639 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 90e855cf4cc 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 99694e135bc 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 61d6f7a239f 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 73a0460632c 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 0758fb66e61 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new a220aa59cae 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 7ae2b412f26 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new c1806d2636c 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new e4b2322863a 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new e823cd587a3 212: force: #27: : Failure after baseline build: no new commits new 74cc5af8298 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 96f6086fca5 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] new 388f8732d64 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] new bd8f5853c26 216: force: #43: : Failure after baseline build: no new commits new a61f753e4eb 217: force: #45: 1: Success after linux: 1 commits new 904c1e3d338 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] new cf023fa6a85 219: force: #50: 1: Failure after linux: 2520 commits new be618bd2fe5 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] new 60e4a7241e1 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] new ce3ece35f24 222: force: #60: 1: Success after gdb: 16 commits new 02526e9073e 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] new 82fdd8f79f4 224: force: #65: 1: Success after gdb: 50 commits new 1154a01eff2 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] new f8236434d4b 226: force: #70: 1: Success after baseline build: no new commits new e69e6f65cb0 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] new 9761e53dd16 228: force: #74: 1: Success after gdb: 53 commits new 0e57dad3c95 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g [...] new 16db361a45b 230: onsuccess: #78: 1: Success after gdb: 2 commits new 9b2397a6d6c 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 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 (73b50b2cb85) \ 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 1996 -> 2008 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2528 bytes 03-build_abe-binutils/console.log.xz | Bin 49112 -> 49220 bytes 04-build_abe-gcc/console.log.xz | Bin 234700 -> 234368 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8544 -> 8472 bytes 07-build_abe-glibc/console.log.xz | Bin 232968 -> 234128 bytes 08-build_abe-gdb/console.log.xz | Bin 46368 -> 48848 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3768 -> 3820 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4448 -> 4588 bytes 11-check_regression/console.log.xz | Bin 4212 -> 3636 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 10 + 11-check_regression/mail-body.txt | 49 - 11-check_regression/mail-subject.txt | 1 - 11-check_regression/results.compare | 17 +- 11-check_regression/results.compare2 | 113 +- 11-check_regression/results.regressions | 18 + 11-check_regression/trigger-bisect | 3 + 12-update_baseline/console.log | 68 +- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- mail/changes-list-long.txt | 8 + mail/changes-list-short.txt | 1 + mail/mail-body.txt | 49 - mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 24 +- results | 18 + sumfiles/gdb.log.0.xz | Bin 2895788 -> 2887436 bytes sumfiles/gdb.log.1.xz | Bin 143188 -> 187828 bytes sumfiles/gdb.log.10.xz | Bin 10108 -> 10312 bytes sumfiles/gdb.log.2.xz | Bin 20312 -> 20256 bytes sumfiles/gdb.log.3.xz | Bin 10088 -> 14916 bytes sumfiles/gdb.log.4.xz | Bin 10240 -> 14976 bytes sumfiles/gdb.log.5.xz | Bin 10236 -> 14936 bytes sumfiles/gdb.log.6.xz | Bin 10172 -> 10360 bytes sumfiles/gdb.log.7.xz | Bin 10320 -> 10264 bytes sumfiles/gdb.log.8.xz | Bin 10240 -> 10252 bytes sumfiles/gdb.log.9.xz | Bin 9900 -> 10364 bytes sumfiles/gdb.sum | 1916 +------ sumfiles/gdb.sum.0 | 1935 +------ sumfiles/gdb.sum.1 | 8603 ++++++++++++++++++++++++++++++- sumfiles/gdb.sum.10 | 26 +- sumfiles/gdb.sum.2 | 76 +- sumfiles/gdb.sum.3 | 203 +- sumfiles/gdb.sum.4 | 197 +- sumfiles/gdb.sum.5 | 273 +- sumfiles/gdb.sum.6 | 43 +- sumfiles/gdb.sum.7 | 37 +- sumfiles/gdb.sum.8 | 33 +- sumfiles/gdb.sum.9 | 101 +- 52 files changed, 9635 insertions(+), 4194 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/mail-body.txt delete mode 100644 11-check_regression/mail-subject.txt create mode 100644 11-check_regression/results.regressions create mode 100644 11-check_regression/trigger-bisect create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt