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 64378a9c5f 157: onsuccess: #72: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards bcdc7083ac 156: onsuccess: #71: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 6417b87a1f 155: onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 7db3829c38 154: onsuccess: #69: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 5c32bd31be 153: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards e48685ca4c 152: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards c8ae68ab29 151: onsuccess: #66: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 2e3698bc68 150: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards dc2a8d00d8 149: onsuccess: #64: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 82d6dca9cd 148: force: #63: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards f19fd11176 147: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 1c05955d28 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards da6a92313e 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards af9dcda5a1 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards fcded71dcb 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 4d0d9d67da 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 73ecf94375 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards c498b91d59 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards f0e7679526 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards f0ee5ec1e2 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards ca5f4765cd 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards abcb144297 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 02ab3ce58c 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 142ae78fe7 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards f9179d6ff2 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards d2d8b33d4e 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 51eb308c1d 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards efafc82c48 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 89bb05e000 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 03c1a9ddf7 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 01e726114f 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 33cbe9d39a 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 92028a9b25 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 3e326f35fb 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards e609c0724b 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 47ebaf0ea9 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 538cad408a 121: force: #26: : Failure after baseline build: no new commits discards 418594819f 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 824996aaed 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 1c0a74bd4f 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 76016df8fb 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards fd3a1f14c0 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards ac6a175901 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 35c37f614a 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards fd6367af9a 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 3ee8038fef 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards b411e4599b 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 696a08138c 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 0cc061cce4 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards c8aa7333ef 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 004f2627e0 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards ce5219f07c 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards fa60737ffc 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 3124120af2 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 29a14743db 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 12890e3a4f 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] discards 761c739e77 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] discards 30afa8496d 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] discards 60742c7b57 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] discards 0f65ef4191 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 1430f97585 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] discards e31757c07d 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 13f1bb6720 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] discards a7917c58bc 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards 741f4ccd90 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards e6bd341757 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards b8d8610451 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 362b9157c6 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] discards e554483365 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] discards 04e1b9661e 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 1c2714969c 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] discards 029c977a30 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] discards 5b1ac70a9b 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards 34b20e6615 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards 4a97b7f0d5 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards d39f302f0e 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards 443fedd59a 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] discards 76e32ca7d3 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards a8e9edb54f 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] discards 0c0d3eca14 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards aa35282b5c 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 9652b3567d 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] discards 13ca05cd80 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] discards 1e1b178cc2 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] discards 0cba1ec190 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards e8e21a67c5 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] discards 7d2eba8377 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards 7e3bcc9c0d 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] discards 6d08e1a8e8 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] discards 3b043622fc 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] discards 7da244b900 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards 80f43ef2be 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards b092a1c8c6 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] discards 29505d9e79 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] discards f7d4801335 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] discards 9595bf4868 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] discards 02aaee65f5 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] discards f51e78bba9 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 093ca419d4 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] discards 2a2c98b815 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] discards 102791b733 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 7a05abb4ad 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new ea913173e0 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] new 30fe54384d 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] new 526545a4f7 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new ac1b1d7223 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] new a4d96184ae 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] new de4efd258f 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] new adfbea2aca 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] new d2ca5d32cb 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] new 82adcf43a6 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new fc1568df63 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new f1cc042847 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] new 4e1890c52d 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] new 2e25920ce7 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] new bd4a95cad0 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new f1758be529 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] new 4c76759160 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new a4580ba540 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] new fcc9012e72 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] new 63fa7fa6de 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] new 1d41ebfb22 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new a0a7a8a79c 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new bb4ac7fe41 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] new 36504a4c63 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new e71e72f948 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] new 69a78ed169 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 6cee9ba198 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new a0746293ae 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new aecfea98e8 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 7b4431fdba 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] new a0deabccab 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] new f87c81a0ee 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new b261386ef4 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] new 5aabc7d200 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] new 11d1470049 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new ee7abffafa 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 14a91f26f3 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new add0011121 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new f32d976236 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] new af659526a2 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 9bf886239f 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] new a600606a88 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 51dc90618c 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] new c6d3977c61 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] new 7b8b8ecfe4 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] new 240236961f 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] new e89928615f 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new b12f84fbab 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 5485c84be4 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new f3ff666ca8 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new 364d3811c9 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 96497efd9b 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 4b0cfb3109 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 482ae769ca 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 5668688c22 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 1775f985c1 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new a511ce4634 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new db0dccb872 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 16bd3f7b7b 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 344de9b6b8 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new 9c10a6db62 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new 1738dce788 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new d00148e073 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new b72b04a9c7 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 9b341c3e37 121: force: #26: : Failure after baseline build: no new commits new 3e72786894 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 84d07499b1 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 1b59e97279 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 3a73475e4e 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new fb63aab910 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 75f14f58df 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 1308fd138d 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new ab5f74f2f3 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 303c416ff5 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 8565e05932 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 53684a2dfe 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 839f3ff097 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 5389627f5e 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 186404898e 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new e5acf5b7a4 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new c46d560c05 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 2793127af5 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new b187b55b64 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 8a9d2e34a2 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new fc26a38f2e 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 201ff26aa0 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new a89e7bf6b5 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 755483a586 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 2cf0d6152e 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 35b94446f2 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new e080c74473 147: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 834f092284 148: force: #63: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new aaff874cbe 149: onsuccess: #64: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new ca9616b63c 150: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new 1a974fdb58 151: onsuccess: #66: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 078888c5c1 152: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 40b6b39b06 153: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new ebcc885602 154: onsuccess: #69: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 3e3b90a255 155: onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new e7374e44b9 156: onsuccess: #71: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 61a998dc5f 157: onsuccess: #72: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 336d7d274d 158: onsuccess: #73: 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 (64378a9c5f) \ 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 14256 -> 14228 bytes 01-reset_artifacts/console.log.xz | Bin 2252 -> 2248 bytes 02-prepare_abe/console.log.xz | Bin 2444 -> 2476 bytes 03-build_abe-binutils/console.log.xz | Bin 49392 -> 50268 bytes 04-build_abe-gcc/console.log.xz | Bin 239464 -> 238044 bytes 05-clean_sysroot/console.log.xz | Bin 320 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9312 -> 9112 bytes 07-build_abe-glibc/console.log.xz | Bin 235344 -> 233124 bytes 08-build_abe-gdb/console.log.xz | Bin 47356 -> 46988 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3900 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3448 -> 3312 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 1208 -> 1192 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 +- jenkins/notify.sh | 2 +- mail/results.compare | 6 +-- manifest.sh | 28 +++++++------- sumfiles/gdb.sum | 4 +- 24 files changed, 66 insertions(+), 66 deletions(-)