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 f6085b956dc 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] discards 23034e963da 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] discards b56ef3a8e0b 219: force: #50: 1: Failure after linux: 2520 commits discards 5ae404e006c 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] discards abbc626556b 217: force: #45: 1: Success after linux: 1 commits discards 1d8931c005d 216: force: #43: : Failure after baseline build: no new commits discards 0deb1dd5e57 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 8976690ef02 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 5f73003f61c 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 43dc469b7a9 212: force: #27: : Failure after baseline build: no new commits discards 3aeb30670d0 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 0a4ed564db3 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 70d4b6aaa21 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 5fb0dbd97a1 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 560c295a74f 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 6c468f168fd 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards dac63edf22b 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 7bfa5d7880c 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards ad18fb34cae 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 1ffc5e43688 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 64a21722d5a 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 84d1d045717 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 3c3f36f6d7a 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards eeaa4478972 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 391776064b0 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards debdef72440 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 7f859764325 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 094753995a0 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 3b6273d70d2 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 02010650733 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 95e31df7a88 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 1db7da68194 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards dbece5b43bd 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards e014e2566c4 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards 8acd5e7a8b7 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 8a880a43704 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards c4cd163b457 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards 91c26c3f62c 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards b54491dbb1a 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards e8c62c7cf8d 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards fcae719b2e1 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 86104176ffe 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards e250fbfbf35 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards 54df284acab 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 7609246cb3e 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards fa61f2be9f7 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards ca55176f72a 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 9aa001b7897 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 49cb0f638be 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 4f0f0b5114a 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 9531f50b02c 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 9df5fb69aae 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards 2e046ed0b65 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards b6bba74a470 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 2325bbd97f7 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards dc0d3f1f82f 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards a8ec68362d3 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 4449d5e106c 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards 27c4a76b6c9 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards a3d2b03f885 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards eea7dbde5f9 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards e71ab6d40a9 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 4e44936d807 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 87606e34ea9 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 4db4bb22e23 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 6f8eec63c19 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 604ff50f73e 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 243dcbb07fe 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards 17cdf0acf21 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards a964c11d9b7 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 95f5d4184f0 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 54e2a3851c1 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 59f440cac77 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 9284aab7955 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 988055fcbad 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards 58859b294d0 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards eca09d8f728 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards e2228d91095 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards 809e6c6e1ad 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards bd3a1e5384d 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards eabb81108ed 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards a50078ec03d 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 341ee9b3fcc 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 82168ab00df 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 27dc1560516 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards b5883597a56 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 9164a912c04 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 8cc079ca0b3 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards c5a20ea3d93 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards a45b75253c7 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 7f2efa4c5cc 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards c6328a4bd7b 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards 0792db74c61 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 6d8d35ba520 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards d53e563a185 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 1ae32b58e73 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 317b203ded5 125: onsuccess: #614: 1: Success after linux: 12 commits discards ae980169a5c 124: onsuccess: #612: 1: Success after binutils: 18 commits discards c5376006567 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards d38e3f22153 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 1f70b42a0cc 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new de116694245 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 28800a97e87 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new b0b3c2911f0 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new ae5ed12bab8 124: onsuccess: #612: 1: Success after binutils: 18 commits new 3d57354fd25 125: onsuccess: #614: 1: Success after linux: 12 commits new 06db7252b7b 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 88240a506a1 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new e34104f0b49 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 7a89714b7be 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 765a48d1ce0 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new b9cfc33ac3d 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 018fea9e3d5 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 93278a44c37 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new f5b60fbc060 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new b993c3d303a 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 57ec07ede44 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new eaaa3911e8f 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 914eb26f771 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new ac99098f702 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new c3e65fb6cbd 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 480eab6d795 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 1e37a933538 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new d46a1b0ea97 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 06dd4fb2fbb 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new 4b721e31198 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 256729f3042 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 17196588f88 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new 1b259cfbef4 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 7d98ed1ca5f 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new ba617340acf 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 4a077d82542 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new fd0b15a6694 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new 613747f55c2 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 474772e7c0c 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new 06577a1be3d 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 8effcc911d8 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new f72ec504448 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 16486c599af 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new b7f1607a6bb 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new eacae59b83c 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 261231ebf55 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new d792d762ac3 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new a3b5f93d8a6 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new dbed61e82a1 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new a68391e52f6 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new e92a93ec89d 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 03dea317819 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 64fbb3c1ba3 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new c5e6c8559a4 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new f6f1b7518fc 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new 7e6935922c2 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 26eb7b67e64 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new fdc28085130 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new 1d7081240c4 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new ae0fe21e5b9 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 942fce2a5da 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 74ec54da26d 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 173d4476008 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new e45fa26f79a 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 340c7653e44 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new 156b06ed48a 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 17766137f3c 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 3eae43b1961 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 87435fd29a0 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new 28045495bc8 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 910e8f04566 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new 2523d8612bf 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new 706118541be 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new ed1dc937f8c 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 645c0db4833 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 89726698160 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 73aef8aa430 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 118752d3fd3 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new e9f03d575e0 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 7f515203b78 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new a93304f19ce 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 2b8f4508832 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 844a67e4bef 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 526c3a8e73a 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new e3eb58ed316 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 06b040e6e78 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 239b1c98c6f 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 6e5651af2d0 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 68fd83baa78 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 4b1fdd570b7 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 1cb8a86a4d8 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new aa66c814098 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 553bdfc815d 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 47d509d9500 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 59c8f05f39c 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 2a366154225 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new befa33b9700 212: force: #27: : Failure after baseline build: no new commits new 5043cccf4db 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 0927d5ba587 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] new 1ab0d71c248 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] new 787a4103359 216: force: #43: : Failure after baseline build: no new commits new c1a07c20779 217: force: #45: 1: Success after linux: 1 commits new c1dfbb1e0a0 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] new a78d6cf4023 219: force: #50: 1: Failure after linux: 2520 commits new 6ed041e5075 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] new 78c06658fda 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] new dd0ee1ca93e 222: force: #60: 1: Success after gdb: 16 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 (f6085b956dc) \ 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 2072 -> 2052 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 48680 -> 49000 bytes 04-build_abe-gcc/console.log.xz | Bin 236424 -> 235968 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8556 -> 8588 bytes 07-build_abe-glibc/console.log.xz | Bin 233076 -> 233684 bytes 08-build_abe-gdb/console.log.xz | Bin 46984 -> 47232 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3788 -> 3772 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4496 -> 4700 bytes 11-check_regression/console.log.xz | Bin 3216 -> 3208 bytes 11-check_regression/jira-body.txt | 1 - 11-check_regression/mail-body.txt | 2 +- 11-check_regression/results.compare | 19 +- 12-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 1 - mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/gdb.log.0.xz | Bin 2930820 -> 2959316 bytes sumfiles/gdb.log.1.xz | Bin 185224 -> 138376 bytes sumfiles/gdb.log.10.xz | Bin 0 -> 10096 bytes sumfiles/gdb.log.11.xz | Bin 0 -> 10364 bytes sumfiles/gdb.log.12.xz | Bin 0 -> 10272 bytes sumfiles/gdb.log.13.xz | Bin 0 -> 10108 bytes sumfiles/gdb.log.14.xz | Bin 0 -> 10132 bytes sumfiles/gdb.log.2.xz | Bin 16820 -> 11924 bytes sumfiles/gdb.log.3.xz | Bin 14812 -> 10084 bytes sumfiles/gdb.log.4.xz | Bin 14976 -> 10364 bytes sumfiles/gdb.log.5.xz | Bin 10288 -> 10080 bytes sumfiles/gdb.log.6.xz | Bin 10312 -> 10144 bytes sumfiles/gdb.log.7.xz | Bin 10160 -> 10192 bytes sumfiles/gdb.log.8.xz | Bin 10364 -> 10108 bytes sumfiles/gdb.log.9.xz | Bin 10116 -> 10160 bytes sumfiles/gdb.sum | 3699 +++++++++++++- sumfiles/gdb.sum.0 | 3715 +++++++++++++- sumfiles/gdb.sum.1 | 8652 +-------------------------------- sumfiles/{gdb.sum.9 => gdb.sum.10} | 28 +- sumfiles/{gdb.sum.9 => gdb.sum.11} | 56 +- sumfiles/{gdb.sum.9 => gdb.sum.12} | 21 +- sumfiles/{gdb.sum.9 => gdb.sum.13} | 24 +- sumfiles/{gdb.sum.9 => gdb.sum.14} | 20 +- sumfiles/gdb.sum.2 | 198 +- sumfiles/gdb.sum.3 | 207 +- sumfiles/gdb.sum.4 | 206 +- sumfiles/gdb.sum.5 | 18 +- sumfiles/gdb.sum.6 | 45 +- sumfiles/gdb.sum.7 | 84 +- sumfiles/gdb.sum.8 | 32 +- sumfiles/gdb.sum.9 | 25 +- 52 files changed, 7808 insertions(+), 9337 deletions(-) delete mode 100644 11-check_regression/jira-body.txt delete mode 100644 mail/jira-body.txt create mode 100644 sumfiles/gdb.log.10.xz create mode 100644 sumfiles/gdb.log.11.xz create mode 100644 sumfiles/gdb.log.12.xz create mode 100644 sumfiles/gdb.log.13.xz create mode 100644 sumfiles/gdb.log.14.xz copy sumfiles/{gdb.sum.9 => gdb.sum.10} (99%) copy sumfiles/{gdb.sum.9 => gdb.sum.11} (98%) copy sumfiles/{gdb.sum.9 => gdb.sum.12} (99%) copy sumfiles/{gdb.sum.9 => gdb.sum.13} (99%) copy sumfiles/{gdb.sum.9 => gdb.sum.14} (99%)