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 503a77a6ac 149: onsuccess: #64: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 887c4fc246 148: force: #63: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards 298d809f7c 147: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 4d8926a700 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards ef768646e5 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards d145ae7061 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 15e57ecb97 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 219ef219cb 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 07a008e65e 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards b0a21a5722 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 1067196613 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 21d7e33ef1 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards ea501ee338 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards b966152f47 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards b6fbd43e8a 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 5b13844f12 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 29ee848a0a 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards a53da6fb64 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 2f582b4f2a 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 6e4cf44c5f 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards c254c283ac 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 6ae100c8b7 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards cedd028571 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 140b0599a9 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 18305fec86 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards fc225ecb75 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards db53b20366 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 2f10917a37 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 2e31180ba3 121: force: #26: : Failure after baseline build: no new commits discards 678a41d4db 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 0031291d5c 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards e61f5083b5 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 3f24e4b972 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards 1ae627faa8 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards f3939d02df 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards fa8d3784a0 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards e21aba53c4 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 44cb7a7f77 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards dcd3711583 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards e380614f48 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 3d344dd591 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 006fb12e43 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards e7187dddef 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 3d7c198af0 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards e10c3cbeba 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 76c76bd13e 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards c8a43ef794 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards ab5a0d26ee 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] discards eb773746f3 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] discards a54c027a07 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] discards 026c5be3fd 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] discards bb9b043fd4 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 36304bfaa3 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] discards 834b032a47 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 8a83333cf6 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] discards f64f7bccad 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards 5b46e4ad35 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards c3a80e8bd8 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards 819018574c 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards cc865117e2 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] discards ef3fb09a93 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] discards 3aff44e533 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 5c577bc280 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] discards d8e537ca0c 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] discards 2f7faceaa4 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards 2b2d9e060a 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards bf7620235b 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards e99185d8e8 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards fde6dbceb6 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] discards cee95b6ac8 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 97796e8467 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] discards 5786afe31e 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 5b648269e8 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 72bad4bdbb 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] discards e7f992b8c4 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] discards 02222be65a 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] discards 824c755fdf 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards ace03d4852 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] discards 809f4963ab 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards 9a8c820a2f 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] discards a6a262c6ea 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] discards 1d452f3b8f 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] discards 87ce0440a2 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards 19838bd0b8 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 499047c6f3 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] discards d7f389cd37 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] discards 4a1c349c4b 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] discards 6d204b2293 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] discards d3ea1a178b 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] discards f3485443fd 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards fdb6bb24b6 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] discards ed8befa0e3 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] discards 92b5413c97 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards 4efa8d8fa9 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards b0a0c05f88 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] discards f59e30feb3 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 7d3740c423 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards cd64e16b1c 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] discards 0703e917de 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards f2459dac70 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] discards 5d58d486e2 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] new 6697dbcc22 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] new 4ad276963f 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] new d69ab42da9 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 84fe0c150a 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] new 7592259800 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 95eeab04ba 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new c9fa7dd0b7 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] new 352a86a6f2 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new ca368d48e9 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 499871400f 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] new 634b5c478f 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] new d1e7ce9854 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 6f3e3a3784 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] new dac7ff59a5 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] new 8f3b82c946 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] new 8b5f93d6dc 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] new 51bd58420c 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] new c7afbeec8c 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new a66bb35f3a 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new db3823432b 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] new 53551111ca 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] new 2ec802c142 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] new 0791274d02 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 1628a7d8fb 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] new cbc3cee3fd 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new 7b4c717312 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] new ad01f858a7 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] new 2bab72b9f1 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] new 00e9bb0e73 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new f1007ae99c 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new c7e57c854e 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] new 0c0aedd9dd 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new 2dab10d1bb 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] new b188117220 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 2d14baf6cb 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new d4abfb88ee 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new 831996b0a0 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 3eb20685df 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] new ffb5840998 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] new 300a68de93 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 60a787e112 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] new 0d5d2ea8be 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] new d4f7fd31c6 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new 98c9d372d0 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new e4eca772bb 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new 28cb307f5d 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 87d1b0c41a 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] new e7b5ee3f60 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 7dd8601f4b 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] new 450700337f 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 900310c010 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] new fc0bbc1acb 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] new 0ef5521183 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] new 1188db75d4 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] new fb7f5421ce 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 73d241bbc3 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 5a5dde367a 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 30ae1afa57 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new e5b803d06e 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new b626173e0c 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 7f933d27ef 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 29293d96b9 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 2bc88fb4bc 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 47a5faef60 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 93fec16608 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 14c597de7c 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 1d68412565 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new ba9d925061 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new ae49afec34 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new 6ee4b389b6 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 9399eadbe0 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 4b94129d98 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 4719e24ee6 121: force: #26: : Failure after baseline build: no new commits new c7322210ab 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 3986fe1e51 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 81d245e0f5 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 7428735da7 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new feb91fd7c7 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new a136295ca0 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 166add88d7 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 4b8bfc2408 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new d4bf8de028 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 86b2437bbb 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new fd439eb5c3 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 0461e6f671 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 44ed05c2da 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new a9aaa85457 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 0c839ddfc8 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new e6bf01653d 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 3c56396abc 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 23b44720f8 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new bc7cfa2232 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 370f2eeed9 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 8d25eb89ef 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new a5065b3c4f 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new e26f25f12e 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 693df2ce28 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 138fb5e9d2 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 50e2d19182 147: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 2ce38b79bd 148: force: #63: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 5f275bbc98 149: onsuccess: #64: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new 778b7aedcd 150: onsuccess: #65: 0: [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 (503a77a6ac) \ 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: 01-reset_artifacts/console.log.xz | Bin 2200 -> 2220 bytes 02-prepare_abe/console.log.xz | Bin 2524 -> 2528 bytes 03-build_abe-binutils/console.log.xz | Bin 49220 -> 48904 bytes 04-build_abe-gcc/console.log.xz | Bin 236160 -> 235504 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8452 -> 8452 bytes 07-build_abe-glibc/console.log.xz | Bin 233052 -> 233108 bytes 08-build_abe-gdb/console.log.xz | Bin 46416 -> 46496 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3804 -> 3856 bytes 10-build_abe-check_gdb/console.log.xz | Bin 1732 -> 1716 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 548 -> 548 bytes 12-update_baseline/console.log | 64 +++++++++++++++++----------------- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 2 +- manifest.sh | 30 ++++++++-------- 19 files changed, 53 insertions(+), 53 deletions(-)