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-aarch64 in repository toolchain/ci/base-artifacts.

discards 0a70b0b5e0 163: onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards af57d478f2 162: onsuccess: #75: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 8f8496564b 161: onsuccess: #74: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 87cf384fe2 160: onsuccess: #73: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 2e89e76b5e 159: onsuccess: #72: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 524f5f0cb7 158: onsuccess: #71: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards bb53dde598 157: onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 4c8b0ce166 156: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 77bf24253e 155: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards e0ff5881e8 154: onsuccess: #66: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 18476f45e2 153: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards c686c4d135 152: force: #64: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards 2026630923 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 6ed1852d40 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 2207a452e8 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 2d1fe9e7d2 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] discards 71eeeee9c5 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards bd41caa57b 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards ebf2a26d97 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 56c69d932f 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] discards fda46c6aae 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 5f77e17906 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 942df6c35e 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 85cb4ea0c2 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 8b23bb4158 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 3ea469f042 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards f01da868e2 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 8943e76569 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 6575de646a 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] discards c052414bc7 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] discards 877d86cea3 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards b03a707ebd 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards df09d38c26 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] discards 8c005032ce 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards d2145dbaed 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards d33384cede 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards ba743d8028 127: force: #27: : Failure after baseline build: no new commits discards 4c4b5c3bb8 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 10689f80df 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 94d93a7036 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 5a189496ae 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards e1d2686d7f 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards ed7a42ea2b 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards c887282b94 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 1d474828b3 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 90643348f7 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 478b58536d 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 10c82f48fc 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 76da420003 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 090a2e94d7 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 2d6d3c898f 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards 7e2810ecb2 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 1dabe5c5be 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards e9e09ae167 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 1d5bda02bd 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 8723814c79 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 41a99c0ae6 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 3b7a249d9a 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] discards 702422c85d 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards fbeab14dee 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] discards 90b058e46b 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] discards 9b54964ee9 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] discards 29f6df6bf3 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] discards 73a3d0f2eb 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits discards d382aba775 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] discards 7b4d7d0032 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] discards 74bb235b50 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] discards 953535656d 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] discards 7769dce5d8 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] discards e466a965af 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 74cfa50521 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 4ccba44360 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] discards 8448d453c6 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards 626bbf57a8 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards a159d33e49 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] discards 36f2fbc31e 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards 8541e98318 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 0a8193a2f5 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] discards 024d2a99ce 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] discards 250d309986 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 36180664aa 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 400a1a1b5b 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] discards baf3b3be43 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards be554269c3 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards 9b360fef31 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 0dcb245f85 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards 99ab07e9c4 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] discards e2cc6c2b7b 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] discards 703bad1eef 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] discards d3e49cfd44 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards d6b8f2f1d5 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 2053b9f847 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] discards c03b6d2478 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] discards d7f3cf9c09 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] discards b3fbeab016 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 7294a98015 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] discards cb574d6f81 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards e371f80486 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] discards 1fccc8df1b 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] discards bd07c29ca7 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] discards 509bf9034c 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new 8ee04a13b4 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new 5b453d0ac2 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] new f940fe3f04 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] new 8048801f49 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] new 8655f28b23 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 7fa2dcae81 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] new 107ecf90c1 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new 5326fa1841 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] new c454f772e9 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] new 1364aa3c10 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] new e198949fb3 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new dcb0feb8d8 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 5136cb6afa 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] new 1daf0b1e8f 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] new b2ab40ac35 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] new e2813f9c1d 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 9bb4766a54 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new ea96f3f2e3 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new 3247fe330c 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 08ca594c46 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] new 7feb4e2066 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new 2eb403ee99 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new f6f4936ae5 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] new 043b5c8c39 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] new 9e5761b41d 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new 1611121da8 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 6753b058bd 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] new 1f9fa42ddf 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new 909f8e9df4 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 4ad48ec604 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] new 5ae6d7fc5a 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 68472644f9 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new e4c6faffa4 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] new 2c7b37986a 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] new 4d055577d4 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] new c535e4a94b 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] new 0702b2cdd9 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] new 9b26ebfe5d 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits new 2e9dd648d5 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] new 7a86ba7971 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] new 4ff5835e4d 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] new 958f315267 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] new 3fe37aeb3c 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new e22b98c2e6 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] new 2f146aa28b 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 6c558fcee2 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 091de0f43c 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 816181b715 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new c0c7d33774 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 219e9cda34 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 42ad9def01 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new 580869bc60 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 386a96a994 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new c7920dabeb 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 841ff83568 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 029c4102b8 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 520f2385d4 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new d53c517539 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new ef13574ba9 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 1862d766a2 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new d1e96346c9 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new e983d45840 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new 20e6888df8 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 0778be61d3 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new edd9d0d465 127: force: #27: : Failure after baseline build: no new commits new c8474e506c 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 4d1583f5b8 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 2b048861aa 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 7631dc94e7 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] new e6c2db3fa8 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 8329248df1 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 9eb34d03c6 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] new ed2c8bae2f 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] new 5b950c6493 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 5de785fbbf 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new f735e83d8c 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 0caa5a4e8a 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 65ded223c9 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 4577170435 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new d9bcb55e6e 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 8ef608f7d9 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 24b747d4a7 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] new 5374d5e38e 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 807e15dceb 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new b4779c669d 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 0a4b1ccaea 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] new 53679fde79 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 13f82ae2e8 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new fedc3136e2 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 17b935386c 152: force: #64: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new ee72bdc795 153: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new e812506753 154: onsuccess: #66: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new bf4ed92bea 155: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 6f892bfb19 156: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 152b15a55d 157: onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new bfed17df84 158: onsuccess: #71: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 79b3efae21 159: onsuccess: #72: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new d37744ba8d 160: onsuccess: #73: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 40852de1d8 161: onsuccess: #74: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 64c2741bab 162: onsuccess: #75: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 61e8453565 163: onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 5188e2c446 164: onsuccess: #77: 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 (0a70b0b5e0) \ 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 14436 -> 14424 bytes 01-reset_artifacts/console.log.xz | Bin 2192 -> 2240 bytes 02-prepare_abe/console.log.xz | Bin 2460 -> 2468 bytes 03-build_abe-binutils/console.log.xz | Bin 35172 -> 35132 bytes 04-build_abe-gcc/console.log.xz | Bin 203540 -> 205128 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9156 -> 8728 bytes 07-build_abe-glibc/console.log.xz | Bin 241260 -> 241692 bytes 08-build_abe-gdb/console.log.xz | Bin 35228 -> 34824 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3880 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3368 -> 3308 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 1204 -> 1200 bytes 11-check_regression/results.compare | 6 ++--- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 46 +++++++++++++++++----------------- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 6 ++--- manifest.sh | 24 +++++++++--------- sumfiles/gdb.sum | 4 +-- 23 files changed, 51 insertions(+), 51 deletions(-)