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_fast_check_gdb/master-arm in repository toolchain/ci/base-artifacts.
discards 336d7d274d 158: onsuccess: #73: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 61a998dc5f 157: onsuccess: #72: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards e7374e44b9 156: onsuccess: #71: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 3e3b90a255 155: onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards ebcc885602 154: onsuccess: #69: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 40b6b39b06 153: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 078888c5c1 152: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 1a974fdb58 151: onsuccess: #66: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards ca9616b63c 150: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards aaff874cbe 149: onsuccess: #64: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 834f092284 148: force: #63: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards e080c74473 147: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 35b94446f2 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 2cf0d6152e 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 755483a586 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards a89e7bf6b5 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 201ff26aa0 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards fc26a38f2e 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 8a9d2e34a2 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards b187b55b64 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 2793127af5 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards c46d560c05 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards e5acf5b7a4 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 186404898e 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 5389627f5e 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 839f3ff097 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 53684a2dfe 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 8565e05932 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 303c416ff5 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards ab5f74f2f3 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 1308fd138d 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 75f14f58df 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards fb63aab910 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 3a73475e4e 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 1b59e97279 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 84d07499b1 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 3e72786894 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 9b341c3e37 121: force: #26: : Failure after baseline build: no new commits discards b72b04a9c7 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards d00148e073 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 1738dce788 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 9c10a6db62 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards 344de9b6b8 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards 16bd3f7b7b 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards db0dccb872 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards a511ce4634 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 1775f985c1 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 5668688c22 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 482ae769ca 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 4b0cfb3109 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 96497efd9b 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 364d3811c9 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards f3ff666ca8 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards 5485c84be4 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards b12f84fbab 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards e89928615f 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 240236961f 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] discards 7b8b8ecfe4 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] discards c6d3977c61 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] discards 51dc90618c 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] discards a600606a88 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 9bf886239f 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] discards af659526a2 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards f32d976236 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] discards add0011121 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards 14a91f26f3 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards ee7abffafa 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards 11d1470049 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 5aabc7d200 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] discards b261386ef4 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] discards f87c81a0ee 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards a0deabccab 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] discards 7b4431fdba 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] discards aecfea98e8 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards a0746293ae 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards 6cee9ba198 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 69a78ed169 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards e71e72f948 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] discards 36504a4c63 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards bb4ac7fe41 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] discards a0a7a8a79c 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 1d41ebfb22 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 63fa7fa6de 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] discards fcc9012e72 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] discards a4580ba540 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] discards 4c76759160 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards f1758be529 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] discards bd4a95cad0 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards 2e25920ce7 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] discards 4e1890c52d 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] discards f1cc042847 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] discards fc1568df63 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards 82adcf43a6 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards d2ca5d32cb 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] discards adfbea2aca 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] discards de4efd258f 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] discards a4d96184ae 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] discards ac1b1d7223 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] discards 526545a4f7 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 30fe54384d 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] discards ea913173e0 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] new a84a3174e4 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] new 01d11a8a60 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] new c9527edf72 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 72f929545d 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] new b59d4c1ce3 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] new 6d21b66827 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] new 564dcbb5d5 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] new f5add8e80a 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] new e72a7445c3 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 2a5cfae729 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new 88a032be16 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] new 84c99d8e80 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] new c2b1f8b099 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] new f909605f9a 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new c602880862 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] new 1c5626f37b 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new f20d53e8b4 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] new 7d7c7115b4 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] new b1086e5817 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] new 96fd4f1953 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new af13a23fd8 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new a1a3055d97 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] new e3408fbddd 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new 2e8245ebde 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] new bc74043547 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new b8e8fa005e 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new 550f5b4387 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new 534a7900c4 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new dceb724eae 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] new 44068b1961 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] new 360b2dd0c7 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 64b4466528 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] new 18008a6629 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] new aef3bc5822 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new 5665e468be 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 09c508f496 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new d742ad298b 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 7d8f926639 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] new 4e31f6906b 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 5474aecb46 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] new e21d9f8b2b 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 29b07e7aff 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] new 5f4204f0bf 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] new 8df3114637 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] new 49c89d25a5 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] new 36c72502bf 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new c9dd684e22 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new c5f6b5acc0 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 01252e387e 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new 8a35d57967 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new c31e8486e8 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 31d6b8c7aa 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 8d8bdfb900 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 4f8f2f20b7 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new feeaa19f8d 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 4a4caf9029 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 45e08708f1 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 0e9e0718ae 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 609c18a38f 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new 5abcf54347 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new 5c2216a68c 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 8dacd34373 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 7df9ac5699 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 090b8ff1f8 121: force: #26: : Failure after baseline build: no new commits new e85fc18281 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 76e3848a19 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 372d9e8295 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new bf4ecc8c07 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new e2046bcb43 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 7a5e2a2d9a 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new eaa18cf0c3 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new ac6034c39a 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new caae5eed00 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 43c3be1f9a 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new a415343a23 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 9acb2e7571 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 82189320b4 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new b6caa9162b 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 8f09ef8223 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 20c5e60eea 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 201d96ab99 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 60117bd590 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new c349c388c6 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new c2f84fde6e 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new d56649ee6f 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 2dcef596c3 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new b5800f8104 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 79be512b55 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 4f66ccb28d 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 4ba253b39e 147: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 833272eb6a 148: force: #63: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new f6a04b0b9f 149: onsuccess: #64: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new 8def342759 150: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new a6a4b78564 151: onsuccess: #66: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new df3814eea4 152: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new fa694c6713 153: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new cbf6cfce6a 154: onsuccess: #69: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new d5cf94aef8 155: onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new e5bcc634e0 156: onsuccess: #71: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 18db72d05e 157: onsuccess: #72: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 854dc04f0b 158: onsuccess: #73: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 920426875a 159: onsuccess: #74: 1: [TCWG CI] https://ci.linaro.org/job/ [...]
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 (336d7d274d) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_fast_check_gd [...]
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: 00-sumfiles/gdb.log.xz | Bin 14228 -> 14228 bytes 01-reset_artifacts/console.log.xz | Bin 2248 -> 2204 bytes 02-prepare_abe/console.log.xz | Bin 2476 -> 2448 bytes 03-build_abe-binutils/console.log.xz | Bin 50268 -> 48700 bytes 04-build_abe-gcc/console.log.xz | Bin 238044 -> 236400 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9112 -> 8656 bytes 07-build_abe-glibc/console.log.xz | Bin 233124 -> 233264 bytes 08-build_abe-gdb/console.log.xz | Bin 46988 -> 47208 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3900 -> 3804 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3312 -> 3272 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 1192 -> 1208 bytes 11-check_regression/results.compare | 6 +-- 11-check_regression/results.compare2 | 6 +-- 12-update_baseline/console.log | 70 +++++++++++++++++----------------- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 6 +-- manifest.sh | 32 ++++++++-------- sumfiles/gdb.sum | 4 +- 25 files changed, 69 insertions(+), 69 deletions(-)