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 c405221c08c 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits discards bb7d1262e6d 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 2 [...] discards e81971938e3 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gc [...] discards 9b2dee0ec15 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards d436c9bb0c3 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards a105e3ac71c 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards 7528cd8e8f7 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits discards df96406026a 230: onsuccess: #78: 1: Success after gdb: 2 commits discards 16cacda252a 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g [...] discards 4a7b6149def 228: force: #74: 1: Success after gdb: 53 commits discards 88b0d071226 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] discards c38a0ce5134 226: force: #70: 1: Success after baseline build: no new commits discards 5a078a95184 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] discards e8699aec85c 224: force: #65: 1: Success after gdb: 50 commits discards 4589c09f106 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] discards fe9ab198947 222: force: #60: 1: Success after gdb: 16 commits discards 3d3c3354b4e 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] discards 9487913cdbb 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] discards b058c9d161a 219: force: #50: 1: Failure after linux: 2520 commits discards 9f555ebc43a 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] discards 4134be77242 217: force: #45: 1: Success after linux: 1 commits discards 0c3ee99dd17 216: force: #43: : Failure after baseline build: no new commits discards b9b80b1497c 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] discards d8dfbad183c 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 506a919e7f7 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards b1839445489 212: force: #27: : Failure after baseline build: no new commits discards 9f4bef9f716 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards edf408e83c3 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards a87b969bed3 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards d55b86afe81 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 68f6b70b776 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 69de0fedd6f 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 5c7892262a3 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 3bd698e5ad7 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 8daa112b3a7 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards e7c276aaa97 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards a3c87d9a02f 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards b99baa9051d 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 4b16b16684e 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 57c405493e6 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 81e974c6d09 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards e5047ac5bb8 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards eba02527206 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 050ddd30a34 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 3bbd1960990 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 2c7592fbe84 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards aa0b8d95dec 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards db33d6882cc 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards b8a9dfd6188 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards 47e23eb95c8 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards 4a2fb3a7137 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards d4bcbe8c01e 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards 351bb3d2eae 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards 34968f50d23 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 2cd9fc691c5 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards ca25cfc5efc 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 82cc0148248 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards af1ab342ce0 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards a7c6a1027b0 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards 887a60295d4 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 89a7f80e0da 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards cfb39a1f446 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 7a6e7f4c080 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 6760c192444 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards f3c1984c771 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards ff5862d9fbc 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 0e308b0cc58 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 96c6d578a1a 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards c3797b557cd 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 91cffeda350 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards bc8a83948cd 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards ae6de604708 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 38a2db45b85 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards cacffe9fe10 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards 9a9ec3400ec 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards e107c32548f 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 4229fb78928 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards a94222542ef 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 6810254810a 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards f0a5d4186cd 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 5610af7d92e 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 74b621c75ff 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards b3c6942f56e 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards db30820bf2d 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards 846e839045f 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards ef2569a1a99 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 5a4dbd33a57 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 521b5311ab8 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards ad75aac1ca6 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 35f04532903 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 2b7217c3ec2 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards de699975b36 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards 75d4bab1fc4 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 1a583cf47fe 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards 74b3c2bac81 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards a5c245db21d 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards b9c9103045d 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards bb5c995212f 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards ab4e4356ae6 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 591afbf896a 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards f39864b813a 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 818152c5e91 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 816b793d2ef 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new d92b54805f2 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 362cd845ca5 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 3609aafdfc4 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new d8e28740133 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new de297f60384 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new f4e14d21611 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new 952651197d4 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 673e41ac132 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 1c5b63cc087 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new 0f78cabcaf3 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 0238120bbc7 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 9cd51d853a4 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 6ecf3078296 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 1e2cfd1ab20 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new a739df0a421 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 6aa31e632d9 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new a5e08a4a8eb 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new ba45d14c7d2 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new ae386ef70da 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 46fb1bd1a7a 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 004bf4baaca 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 1734ff31a7b 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 56ddb5503b5 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 3761d0d22f6 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new a9e43fe6e57 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new cd4d13507ca 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new f4b17173e70 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 49cc307dd9f 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new fb3699200b8 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new a34c3c7e1f1 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new ff33acfa40d 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new c06571c967a 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new b0bdd6b6dcf 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 3ff08195f38 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 63e89c251b7 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new d27cd67f270 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new e58024cfb6a 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 23a47dde4ce 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 9c8d53388ab 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new b5daa111093 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 73d0d510c70 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new c21c9dd21f2 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new 0991fcfb824 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new bd04978bcfb 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 8f66a2d32ab 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 674270d0a31 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new fabe02d570f 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 46809b4e908 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new 5b28c22819c 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new 8f4797fc24e 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new 95542fd7afe 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 20bc8f8ef61 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new b6295f053df 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 29d355f6ba3 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new a72244cadf2 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 8f47f3fc394 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 6358c09f7a9 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 85b741e3b1e 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new e2a8255d74e 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 049226993e9 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new fe882fc3760 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new d192285a323 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 000f0908470 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new c5ca8bdffe2 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 355c02e40ad 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 7c8d9741d0f 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 3b1ce863827 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 8b9b0e05cd0 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 0f81e29622d 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 4d7691751de 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 755b435b7ff 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 3bd9ee07447 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 2d37c541336 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new c072d1a5973 212: force: #27: : Failure after baseline build: no new commits new 57f14a83cb5 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new d83c419fbe9 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] new ea118d9d811 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] new 596c1f4ec50 216: force: #43: : Failure after baseline build: no new commits new 0f300cbccd8 217: force: #45: 1: Success after linux: 1 commits new f2cc3cf8c0a 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] new 3f6faa8d123 219: force: #50: 1: Failure after linux: 2520 commits new 7087a777aab 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] new 402c26c5cfd 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] new 6fe9d68cb11 222: force: #60: 1: Success after gdb: 16 commits new 2634824da52 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] new ed4212b5ad8 224: force: #65: 1: Success after gdb: 50 commits new 6e4c66d3496 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] new e2fa9d1c384 226: force: #70: 1: Success after baseline build: no new commits new 6c199b07fa3 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] new cd751a48da1 228: force: #74: 1: Success after gdb: 53 commits new dba8b56d211 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g [...] new 8552a5fa6be 230: onsuccess: #78: 1: Success after gdb: 2 commits new ba338986c2c 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits new 96baa039da6 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new 8374419d6cf 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new 7f56a794703 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new 3868d24c80e 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gc [...] new edc41631d7b 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 2 [...] new 4ebff790349 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits new 4ac76a8a285 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branchp [...]
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 (c405221c08c) \ 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 2220 -> 2072 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2532 bytes 03-build_abe-binutils/console.log.xz | Bin 48924 -> 49112 bytes 04-build_abe-gcc/console.log.xz | Bin 236144 -> 236180 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8660 -> 8668 bytes 07-build_abe-glibc/console.log.xz | Bin 232040 -> 232440 bytes 08-build_abe-gdb/console.log.xz | Bin 46892 -> 47156 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3772 -> 3772 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4692 -> 4668 bytes 11-check_regression/console.log.xz | Bin 3932 -> 3936 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 8 +- 11-check_regression/results.compare | 16 +- 11-check_regression/results.regressions | 16 +- 11-check_regression/trigger-bisect | 4 +- 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 68 +- 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 | 20 +- manifest.sh | 16 +- results | 16 +- sumfiles/gdb.log.0.xz | Bin 2884104 -> 2966876 bytes sumfiles/gdb.log.1.xz | Bin 143256 -> 143404 bytes sumfiles/gdb.log.10.xz | Bin 10236 -> 10292 bytes sumfiles/gdb.log.11.xz | Bin 10256 -> 10436 bytes sumfiles/gdb.log.12.xz | Bin 10128 -> 10120 bytes sumfiles/gdb.log.13.xz | Bin 10320 -> 0 bytes sumfiles/gdb.log.2.xz | Bin 15512 -> 21380 bytes sumfiles/gdb.log.3.xz | Bin 10308 -> 14948 bytes sumfiles/gdb.log.4.xz | Bin 10168 -> 14900 bytes sumfiles/gdb.log.5.xz | Bin 10028 -> 10024 bytes sumfiles/gdb.log.6.xz | Bin 10356 -> 10352 bytes sumfiles/gdb.log.7.xz | Bin 10344 -> 10288 bytes sumfiles/gdb.log.8.xz | Bin 10160 -> 10240 bytes sumfiles/gdb.log.9.xz | Bin 10308 -> 10460 bytes sumfiles/gdb.sum | 1714 ++++++++++-------------- sumfiles/gdb.sum.0 | 1724 ++++++++++-------------- sumfiles/gdb.sum.1 | 808 ++++++------ sumfiles/gdb.sum.10 | 23 +- sumfiles/gdb.sum.11 | 75 +- sumfiles/gdb.sum.12 | 27 +- sumfiles/gdb.sum.13 | 2172 ------------------------------- sumfiles/gdb.sum.2 | 680 +++++++--- sumfiles/gdb.sum.3 | 240 +++- sumfiles/gdb.sum.4 | 206 ++- sumfiles/gdb.sum.5 | 15 +- sumfiles/gdb.sum.6 | 22 +- sumfiles/gdb.sum.7 | 28 +- sumfiles/gdb.sum.8 | 50 +- sumfiles/gdb.sum.9 | 55 +- 55 files changed, 2972 insertions(+), 5053 deletions(-) create mode 100644 11-check_regression/trigger-notify create mode 100755 jenkins/notify.sh delete mode 100644 sumfiles/gdb.log.13.xz delete mode 100644 sumfiles/gdb.sum.13