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 2275abb080 154: onsuccess: #69: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 1aa74782ab 153: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 954efe8735 152: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards b6a2b2b135 151: onsuccess: #66: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 68657b8966 150: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 82124949d6 149: onsuccess: #64: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards e61d4611fd 148: force: #63: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards d0f4687ea9 147: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards eed8f13f1a 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards dd0618d127 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 664f6e62a7 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards cf1c91c979 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 7ffadc655f 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 3f9a29edfc 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards a5770a6cce 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards ff37c527ed 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards ac82d7b366 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 805aca0355 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 750c6680fe 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards be7a54d1db 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 6bd21b398a 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards a67cd6d2bf 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 05262e4398 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 68dcc750bf 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 0c72b2793a 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards f769326989 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 178c73be83 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards b259fc44b8 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards b09b82aa07 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards caac5497f0 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards bd7e192956 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 9c68ff25b7 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards b74b83741e 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 0f641f0527 121: force: #26: : Failure after baseline build: no new commits discards d5fa210c26 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 43390f3ec7 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards aabe538788 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards f59a47a065 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards 6dd5c6f161 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards 0dddd8e83c 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 15a923f638 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 651ccaf77f 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 2cfbde1406 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards a80eb89e11 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 22ad411d8b 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards af90d417d4 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards af6674ad9d 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 05840707c6 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 3c1558333d 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards d6dffb2549 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards e44ac7dcfd 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards db41ab3d1e 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards ca2bf3e2b3 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] discards 03a965d2e4 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] discards 529a826c21 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] discards e33aefbb1a 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] discards 50a52f6586 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 5d6e9d9b63 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] discards 3776e55dff 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 077e2cd842 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] discards 3b79f4539f 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards add97fb910 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 4fd091e62d 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards a73a097119 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 4265d09bff 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] discards 71625f1751 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] discards 9341616517 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 3337795137 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] discards 0f23ae3671 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] discards cdde0aa8ff 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards 721d141c36 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards dc447ff092 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 05742c7a27 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards ada4d1cd4d 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] discards aa7f66faad 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 73a8b85b7b 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] discards bda30e0422 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 70328c394d 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards c2f719c88a 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] discards d0dff05055 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] discards e0e3dcdb67 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] discards 040225c47a 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 273b239022 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] discards 3a63afab0b 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards 4e1dd2b169 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] discards feac82f1f5 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] discards 5ca4d95707 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] discards d86e81cea3 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards 76d0c23c1a 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 81e6f11011 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] discards 8b234851e5 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] discards fa9620e935 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] discards b599c0faa5 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] discards 83efcd998f 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] discards eada94c503 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 09481e244e 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] discards 077c94b55b 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] discards 55f683ea4e 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards 7d82d65238 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards 9b2923bfc7 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] discards 3202d00c59 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 9c899dcb25 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new caa2ad689b 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] new c21ae25ce8 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new c9c5f879e0 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 76a2cb14b0 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] new ce735566fe 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] new ecf553d2a7 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new ae23a5092a 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] new 1ca0e59fc5 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] new bdb54a0c1a 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] new 25518b4e6d 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] new 6de42e9402 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] new 3c4bfc468e 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 948054d127 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new fcd08beada 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] new f1ba6903f2 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] new 67bf9a846a 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] new 5447569523 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new d42bd0f619 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] new 153c76238b 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new f68208335d 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] new 4972d57450 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] new 10702af929 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] new 315dc9bc8f 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new 95664719bb 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 10acebf218 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] new 404fb396eb 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new 661754c82d 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] new 1b05c96fad 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 0c492e2f4d 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new f1cad2afe5 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new 5dbd6e56ee 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new ac60081d79 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] new fb4a20af2f 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] new a50a59cc59 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 0439ce201c 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] new 720b36903f 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] new 5f6ec5a8e8 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new c022c40f2c 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new e643a3fb96 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new 055837b7b9 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new bc5ff479b7 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] new 5051d98c6c 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new ef8fd57fb5 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] new 3c870909ed 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 432ad19dcb 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] new 332e153a7b 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] new 71c54cb6a5 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] new 3c34fa67b7 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] new 33beedd27e 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new fe4922538d 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new fcad11d6d6 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 5382c980cb 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new c049fcdb9c 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 5b2c8e2322 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 7f35460257 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 2a58321b71 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 33f9db2b22 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new fa8ca9a84c 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 63d7ce1ffd 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new c33fc98545 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new db8b39d03e 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 855dcdc9ff 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new 213e6081f5 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new 92228f5b4c 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new d14fea641b 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new ed35f2cb99 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 5b96291ebe 121: force: #26: : Failure after baseline build: no new commits new 7d7a108eb9 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 4e81ebe921 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new e68a2017c7 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new dca4516abe 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 2033961c67 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new c3b5b1ec38 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 4e18705fde 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 8300f46aa3 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 20c8ca7fc1 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new d69c2f6f74 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 29a4b72b07 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 20ea5b4886 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new fb454e89e6 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 8c095d5cb3 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 4f1c54afe9 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 9c48361363 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 2e9367ba4a 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new e7ec0f278f 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new ef2e36d234 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 32fd9925de 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 98c9a5c5ce 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new d3dcdfd0ca 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new d5ccda0453 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 7a6757eab0 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 77b032fca8 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 259c174cb6 147: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 5e4bbe0dfe 148: force: #63: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new acf193d346 149: onsuccess: #64: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new a60258c760 150: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new b2f3a450ea 151: onsuccess: #66: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 39cbec7e07 152: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new d2d73aec22 153: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 56891ce29c 154: onsuccess: #69: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 68566c5f8c 155: onsuccess: #70: 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 (2275abb080) \ 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 14236 -> 14228 bytes 01-reset_artifacts/console.log.xz | Bin 2224 -> 2208 bytes 02-prepare_abe/console.log.xz | Bin 2488 -> 2452 bytes 03-build_abe-binutils/console.log.xz | Bin 50916 -> 49152 bytes 04-build_abe-gcc/console.log.xz | Bin 240312 -> 236184 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8584 -> 8568 bytes 07-build_abe-glibc/console.log.xz | Bin 235636 -> 232832 bytes 08-build_abe-gdb/console.log.xz | Bin 47456 -> 46788 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3836 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3492 -> 3276 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 1208 -> 1200 bytes 11-check_regression/results.compare | 6 ++--- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 40 +++++++++++++++++----------------- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 6 ++--- manifest.sh | 28 ++++++++++++------------ sumfiles/gdb.sum | 4 ++-- 24 files changed, 51 insertions(+), 51 deletions(-)