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 ab995fa736f 228: force: #74: 1: Success after gdb: 53 commits discards dc2e5d2116a 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] discards b98bbcadd53 226: force: #70: 1: Success after baseline build: no new commits discards 9a421a6b1f9 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] discards a999906778a 224: force: #65: 1: Success after gdb: 50 commits discards 3949f3feff9 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] discards d397ea1af78 222: force: #60: 1: Success after gdb: 16 commits discards 49a8d4fde8c 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] discards 3ec9d639ba7 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] discards d18d4ee948b 219: force: #50: 1: Failure after linux: 2520 commits discards 2d06a1aa28d 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] discards 07d0d7f05cc 217: force: #45: 1: Success after linux: 1 commits discards 2b77931d061 216: force: #43: : Failure after baseline build: no new commits discards 58658287009 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 817a70af9a1 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 04e13fdf075 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 6b0b0e33317 212: force: #27: : Failure after baseline build: no new commits discards bc0416be805 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards cf6cd869033 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards d7c03c7cbc9 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards a712fe962a5 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 1b9fe54e157 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 50d3a6b9de7 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 64662c25cb8 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 1e4bbfe66e3 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 0adb8a04779 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards bbf8424f748 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 42357b99380 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards c1fc600ec48 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards e77dfb31dc3 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 5a72d2540f9 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 26c622e4127 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 515328ced7d 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 65856b7500a 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards bd4188ffaeb 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 2b9da48938e 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards da8136e061d 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards d710c5afb87 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 0392de14094 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 5b07c194808 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards 11555a0dbd9 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards d982ca8cc9d 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards c9bc081765d 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards 2a600613b78 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards 66f06bb1a8b 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards c1db7ff880e 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards cc45cdb837a 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 361ac44e058 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards dd760454619 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards f58c87fd7d5 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards b762344fa43 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards da3d3dce135 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 0adfe8d0a3a 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 84bea89c5fe 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 76217b2129c 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 0e888e55d64 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 51b2f9d6fca 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 6797442428d 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards ddb287ff46c 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards 43324f9e2a9 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards e4409dffb28 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards e077a93f2ba 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 0a9077d4d70 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 3ff77c6e97f 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 16053fa00e0 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards d9608dd06be 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 8e544020f1f 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards bfa52a5850a 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards c5a6f565627 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards f2a4affd882 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 6667490aeda 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 0d5cf6fa4d7 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 0e51306e2d2 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards c7d0b5439eb 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 259f3b169f9 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards 5b67c2ec256 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards a24d82d2f1a 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards aaa84dd6d17 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards d1f9b14adbe 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 78d8999e8ad 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 6017d14c308 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 797fb18dc7b 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards b541ebe0214 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards a47d4e9582d 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 734c217af52 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards d02d6017903 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 79af9a39170 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards ecd32743538 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 7a844d20c62 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 5af4089c0c6 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards a5092d5011e 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 2399840e5e4 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards 1d9b6f6f102 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards f6ee60d6da2 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 099ad4843d7 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards d3c9b873ec0 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 0ac3e3fbab4 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 6dc27933124 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards 7af9f51dd29 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards a2796237018 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards eb32e3539c9 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new f7f66451f56 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new f9ec5cfe7ca 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new be3c345491c 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new 8247660e299 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new c18b0f96864 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 22728b60961 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new 6ae4e283819 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 73d69190797 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 99782e90723 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 6a0f08f8f1c 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 8678209b2f7 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 69b501a4e22 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new b1adfd9ff13 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new a03d638229c 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 307322fd444 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new af419546f42 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 5ea0909c7d7 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new 4cad7e10733 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 38324158c0d 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 027d831225e 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new 968843769d8 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new ec541d18870 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new dda44b46ca0 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 700acc1c4c2 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 3ee6c6715ac 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new 768b71c613a 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 20a91c77fc7 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new c9dbb47bce7 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new a5fa3be7f6a 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new a87ae6bd837 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new d1a4c8ec347 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new b6e835b869b 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new ba46021760d 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new a1b9bedabc2 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new bcdea786f6c 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 7f26f6088e3 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 4ff7c143750 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new 9f8b0d9644c 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 165fe23dd7f 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new e8cb1bcf9f0 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new fa1225686ee 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new d520b212b34 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 7850328a6a2 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new a3880810063 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 6c50981249f 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 9a057f56f78 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new dd7253882e9 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 25861ae3454 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 50b660e1991 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 3b7ca1716e2 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 3d990817926 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 21c8ae19b60 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 25ed98ae4b5 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new 060a3585fe4 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new a1a9f8115e2 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new ab137f5830f 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 60b0c546768 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new 57d7689cbeb 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 7cf4a290acd 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new 7f60c14e12b 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new a744fb07a9b 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new 85f45e478e4 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 2183f541b05 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 4555e39022c 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 4398a08257b 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 2949a1c6bd4 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 08b4d54810f 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 5b830a62ad0 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 9737f14fd29 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 5bc0489af66 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 0ce8218ed17 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new a390dace9ee 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 99389e31edf 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new f89c705fe02 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new b6a6dccc290 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new bd60b441477 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new f6299d13e3a 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 4430cb3d21b 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new c503e326273 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new e1380276169 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new dfd22beed80 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 0d89a04706e 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new fcaaa55e06b 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 867cda970a4 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 7e3fb20e0e4 212: force: #27: : Failure after baseline build: no new commits new 929301a510f 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new de615f0f2da 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] new 279c2f53b28 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] new bf833128a3c 216: force: #43: : Failure after baseline build: no new commits new 3cfd9e64f86 217: force: #45: 1: Success after linux: 1 commits new 0a28d1364b4 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] new 10cf5950eec 219: force: #50: 1: Failure after linux: 2520 commits new 8e08e7403d5 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] new 1715025972f 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] new 1cabebf56c2 222: force: #60: 1: Success after gdb: 16 commits new a7b4a0426d0 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] new 5d0277a895b 224: force: #65: 1: Success after gdb: 50 commits new 3abafdb6f0b 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] new ad5b220159a 226: force: #70: 1: Success after baseline build: no new commits new 4308ad7c0f9 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] new 91ea351c2a2 228: force: #74: 1: Success after gdb: 53 commits new fca47daa7bc 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-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 (ab995fa736f) \ 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 2076 -> 1956 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2520 bytes 03-build_abe-binutils/console.log.xz | Bin 49016 -> 49200 bytes 04-build_abe-gcc/console.log.xz | Bin 234700 -> 234456 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8432 -> 8484 bytes 07-build_abe-glibc/console.log.xz | Bin 233160 -> 232396 bytes 08-build_abe-gdb/console.log.xz | Bin 46932 -> 46484 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3768 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4568 -> 4420 bytes 11-check_regression/console.log.xz | Bin 3796 -> 4092 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 6 + 11-check_regression/mail-body.txt | 16 +- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results.compare | 68 +------ 11-check_regression/results.regressions | 14 ++ 11-check_regression/trigger-bisect | 3 + 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 60 +++--- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- jenkins/mail-body.draft | 239 +++++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/mail-body-header.txt | 49 +++++ mail/mail-body.txt | 16 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 14 ++ sumfiles/gdb.log.0.xz | Bin 2879808 -> 2893016 bytes sumfiles/gdb.log.1.xz | Bin 143376 -> 143636 bytes sumfiles/gdb.log.2.xz | Bin 20280 -> 20012 bytes sumfiles/gdb.log.3.xz | Bin 14912 -> 10240 bytes sumfiles/gdb.log.4.xz | Bin 14964 -> 10088 bytes sumfiles/gdb.log.5.xz | Bin 14844 -> 10120 bytes sumfiles/gdb.log.6.xz | Bin 6572 -> 0 bytes sumfiles/gdb.sum | 55 ++++-- sumfiles/gdb.sum.0 | 62 +++--- sumfiles/gdb.sum.1 | 324 +++++++++++++++----------------- sumfiles/gdb.sum.2 | 82 +------- sumfiles/gdb.sum.3 | 204 +------------------- sumfiles/gdb.sum.4 | 208 +++----------------- sumfiles/gdb.sum.5 | 197 ++----------------- sumfiles/gdb.sum.6 | 188 ------------------ 46 files changed, 690 insertions(+), 1147 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.6.xz delete mode 100644 sumfiles/gdb.sum.6