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 68566c5f8c 155: onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 56891ce29c 154: onsuccess: #69: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards d2d73aec22 153: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 39cbec7e07 152: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards b2f3a450ea 151: onsuccess: #66: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards a60258c760 150: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards acf193d346 149: onsuccess: #64: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 5e4bbe0dfe 148: force: #63: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards 259c174cb6 147: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 77b032fca8 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 7a6757eab0 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards d5ccda0453 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards d3dcdfd0ca 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 98c9a5c5ce 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 32fd9925de 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards ef2e36d234 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards e7ec0f278f 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 2e9367ba4a 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 9c48361363 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 4f1c54afe9 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 8c095d5cb3 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards fb454e89e6 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 20ea5b4886 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 29a4b72b07 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards d69c2f6f74 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 20c8ca7fc1 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 8300f46aa3 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 4e18705fde 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards c3b5b1ec38 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 2033961c67 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards dca4516abe 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards e68a2017c7 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 4e81ebe921 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 7d7a108eb9 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 5b96291ebe 121: force: #26: : Failure after baseline build: no new commits discards ed35f2cb99 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards d14fea641b 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 92228f5b4c 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 213e6081f5 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards 855dcdc9ff 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards db8b39d03e 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards c33fc98545 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 63d7ce1ffd 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards fa8ca9a84c 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 33f9db2b22 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 2a58321b71 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 7f35460257 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 5b2c8e2322 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards c049fcdb9c 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 5382c980cb 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards fcad11d6d6 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards fe4922538d 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 33beedd27e 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 3c34fa67b7 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] discards 71c54cb6a5 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] discards 332e153a7b 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] discards 432ad19dcb 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] discards 3c870909ed 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards ef8fd57fb5 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] discards 5051d98c6c 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards bc5ff479b7 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] discards 055837b7b9 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards e643a3fb96 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards c022c40f2c 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards 5f6ec5a8e8 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 720b36903f 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] discards 0439ce201c 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] discards a50a59cc59 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards fb4a20af2f 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] discards ac60081d79 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] discards 5dbd6e56ee 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards f1cad2afe5 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards 0c492e2f4d 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 1b05c96fad 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards 661754c82d 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] discards 404fb396eb 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 10acebf218 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] discards 95664719bb 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 315dc9bc8f 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 10702af929 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] discards 4972d57450 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] discards f68208335d 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] discards 153c76238b 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards d42bd0f619 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] discards 5447569523 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards 67bf9a846a 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] discards f1ba6903f2 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] discards fcd08beada 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] discards 948054d127 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards 3c4bfc468e 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 6de42e9402 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] discards 25518b4e6d 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] discards bdb54a0c1a 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] discards 1ca0e59fc5 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] discards ae23a5092a 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] discards ecf553d2a7 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards ce735566fe 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] discards 76a2cb14b0 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] discards c9c5f879e0 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards c21ae25ce8 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards caa2ad689b 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] new 0805db14ef 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] new aa308836b4 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new e66b99d99a 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 67ae76b119 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] new daee8fe0ed 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] new fe131e9d10 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 159ed01ebc 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] new cd81a5981a 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] new ffd027f00a 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] new 8a81df5123 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] new 504f4dfbc3 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] new 2db69d5c01 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 3eb89c160f 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new 215581a9bf 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] new ca37954a48 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] new e00f91d627 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] new 1cf5387280 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 10c40b87c4 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] new 00c5d1b0dd 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new eca91f8cb3 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] new 03b6ab06fe 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] new bf82c9f3eb 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] new 61920a3f4d 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new faae1069c9 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 547f5e1416 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] new 78b4a52103 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new 3c3e6aeb69 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] new 810a2ab0d2 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new c733ea8582 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new 9c35ebda9d 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new ced8c2a0ad 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 9af1232b16 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] new bd24029d46 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] new 0beb91c62b 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new a6ac119d3f 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] new dfe3dff274 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] new c0c70a5da6 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new ff1a53c589 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 9a9b649a96 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new b0aaf94da2 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 4de5af595d 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] new a054b24d01 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new a6e4443df8 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] new dd7035b7c1 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 32a7af026e 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] new c8d8f840df 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] new 61236dc08a 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] new 0e6d8fc59d 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] new c7280e2d39 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new c78b542b00 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 34173985cf 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new f71641c995 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new 54613dc032 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new a4dfe4548c 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 4b708700d7 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 585ef08da4 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new c7afe894bc 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 7a3db07d26 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 0fca38780b 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 5561b650a4 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 5a27844268 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 1d8f29e9ad 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new e1ad0194be 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new b12df4e209 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 36a28e266b 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 013e7c0207 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new ea22bf49fc 121: force: #26: : Failure after baseline build: no new commits new d11fd0b937 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 1cc7aa3dc5 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 38de1860e0 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 7df4a3f3f4 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 23a3fa8902 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 1fc1ce6fc4 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 92da0d8b3d 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 7a0d2331f3 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 7172f035a6 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 1223db0bd1 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 07dcf3c35d 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 1ae9193d98 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new a59582068b 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 2cea3de220 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new adfe1a0679 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new b609c85ef7 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new c89e6ce2ab 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new ad337e5456 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new f75b576c36 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 415f6fe9ea 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new dfa5ce74f5 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 4e41bccc3f 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new dffc41ab50 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new bac93c11d2 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 1ccd70df6e 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new f142bc7f45 147: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new dd0c6a6796 148: force: #63: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 6fc63d87e9 149: onsuccess: #64: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new 6c7c6454f5 150: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new 5ae2e84727 151: onsuccess: #66: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new a831aa06a3 152: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 9c3fd086aa 153: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 7d7eea402f 154: onsuccess: #69: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 21552021d5 155: onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 0ea50fd036 156: onsuccess: #71: 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 (68566c5f8c) \ 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 2208 -> 2056 bytes 02-prepare_abe/console.log.xz | Bin 2452 -> 2468 bytes 03-build_abe-binutils/console.log.xz | Bin 49152 -> 49688 bytes 04-build_abe-gcc/console.log.xz | Bin 236184 -> 238536 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8568 -> 9236 bytes 07-build_abe-glibc/console.log.xz | Bin 232832 -> 233824 bytes 08-build_abe-gdb/console.log.xz | Bin 46788 -> 47436 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3812 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3276 -> 3276 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 1200 -> 1196 bytes 11-check_regression/results.compare | 6 ++--- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 46 +++++++++++++++++----------------- git/gcc_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 6 ++--- manifest.sh | 20 +++++++-------- sumfiles/gdb.sum | 4 +-- 22 files changed, 48 insertions(+), 48 deletions(-)