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 1051d31338 162: onsuccess: #75: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards af267a60a3 161: onsuccess: #74: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards adadbdaad1 160: onsuccess: #73: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards b701004ae4 159: onsuccess: #72: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 7aae80c35c 158: onsuccess: #71: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 94a8e0957e 157: onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 9fe0ad6558 156: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 0b2bf588fa 155: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards a3464a2d88 154: onsuccess: #66: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards eeb689c0d0 153: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 6af2a1f97d 152: force: #64: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards b5f7565b39 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 3bdfa27339 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 8d2d2e5671 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 2d089a08ca 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] discards 8864af36fe 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 956fc9df60 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 9bdb748165 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 8e34b322bf 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] discards da9c26bbe3 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 7779359d3d 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards b8b1d06ea0 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 0092aae7fa 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards c528620186 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 424d42d045 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards a6cd82ad8f 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards a364475076 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 091c67c88b 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] discards 1f46aaaa00 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] discards ac7f9fa084 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards b7d4936b75 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 08a7ed095b 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] discards eebc478a20 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 052d23b57a 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards da190eb1ea 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 364f5f97fa 127: force: #27: : Failure after baseline build: no new commits discards d3ed0e27fe 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards e19b0796d9 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 43fa67440d 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 060ed2b0c4 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 5351c53e7e 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 81ca9ec9a0 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 54332aa04f 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 385a0bd979 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards d5cecf7777 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 77695da6f1 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 1095bbf700 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 7a4b8335c0 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards ad269c23ff 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards d022f3b3f3 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards 5d51438345 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards f1448c9317 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 42b51ec3da 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 16987771cf 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 12ca2daa9e 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 366f001b8a 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards c73cdcbf80 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] discards 2104db4532 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 03fef96267 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] discards 17adb4e598 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] discards 36b3040970 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] discards 089de30fab 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] discards 0df320860c 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits discards b94d5fe6e1 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] discards 00cd2634e3 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] discards 45daa8733e 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] discards a3584c2b49 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] discards ca5c5e7ebb 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] discards 26b08ad913 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 5e89808f59 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards d5a613ef11 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] discards 8aca980571 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards b50a5448d3 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards b584868c45 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] discards e89587924a 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards cac186c97b 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 49a809352b 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] discards cafea27de4 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] discards 2a1ac84071 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards caf10efd21 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 70ffe66eb5 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] discards 8aad52a0e4 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards 7ccedeb2e0 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards 547c671696 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards fc72a0f655 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards 25ac865299 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] discards e63cd073de 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] discards fe99b083af 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] discards 126a719c50 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards a44c915c85 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards b1c62a9832 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] discards 86aef6194b 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] discards b4d6f9b270 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] discards 6e71801242 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 3439d6e919 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] discards 19a4d6686c 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards 9f9e4852ae 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] discards e3ba1e1d86 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] discards 20536f4bbd 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] discards ae43155a7f 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards 4d0efefdb9 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] new fb40fa54ed 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] new 509bf9034c 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new bd07c29ca7 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] new 1fccc8df1b 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] new e371f80486 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] new cb574d6f81 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 7294a98015 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] new b3fbeab016 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new d7f3cf9c09 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] new c03b6d2478 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] new 2053b9f847 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] new d6b8f2f1d5 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new d3e49cfd44 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 703bad1eef 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] new e2cc6c2b7b 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] new 99ab07e9c4 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] new 0dcb245f85 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 9b360fef31 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new be554269c3 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new baf3b3be43 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 400a1a1b5b 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] new 36180664aa 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new 250d309986 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 024d2a99ce 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] new 0a8193a2f5 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] new 8541e98318 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new 36f2fbc31e 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new a159d33e49 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] new 626bbf57a8 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new 8448d453c6 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 4ccba44360 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] new 74cfa50521 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new e466a965af 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 7769dce5d8 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] new 953535656d 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] new 74bb235b50 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] new 7b4d7d0032 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] new d382aba775 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] new 73a3d0f2eb 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits new 29f6df6bf3 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] new 9b54964ee9 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] new 90b058e46b 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] new fbeab14dee 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] new 702422c85d 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 3b7a249d9a 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] new 41a99c0ae6 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 8723814c79 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 1d5bda02bd 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new e9e09ae167 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 1dabe5c5be 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 7e2810ecb2 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 2d6d3c898f 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new 090a2e94d7 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 76da420003 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 10c82f48fc 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 478b58536d 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 90643348f7 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 1d474828b3 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new c887282b94 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new ed7a42ea2b 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new e1d2686d7f 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 5a189496ae 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 94d93a7036 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new 10689f80df 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 4c4b5c3bb8 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new ba743d8028 127: force: #27: : Failure after baseline build: no new commits new d33384cede 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new d2145dbaed 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 8c005032ce 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new df09d38c26 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] new b03a707ebd 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 877d86cea3 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new c052414bc7 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] new 6575de646a 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] new 8943e76569 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new f01da868e2 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 3ea469f042 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 8b23bb4158 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 85cb4ea0c2 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 942df6c35e 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 5f77e17906 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new fda46c6aae 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 56c69d932f 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] new ebf2a26d97 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new bd41caa57b 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 71eeeee9c5 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 2d1fe9e7d2 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] new 2207a452e8 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 6ed1852d40 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 2026630923 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new c686c4d135 152: force: #64: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 18476f45e2 153: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new e0ff5881e8 154: onsuccess: #66: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new 77bf24253e 155: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 4c8b0ce166 156: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new bb53dde598 157: onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 524f5f0cb7 158: onsuccess: #71: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 2e89e76b5e 159: onsuccess: #72: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 87cf384fe2 160: onsuccess: #73: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 8f8496564b 161: onsuccess: #74: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new af57d478f2 162: onsuccess: #75: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 0a70b0b5e0 163: onsuccess: #76: 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 (1051d31338) \ 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 14420 -> 14436 bytes 01-reset_artifacts/console.log.xz | Bin 2216 -> 2192 bytes 02-prepare_abe/console.log.xz | Bin 2440 -> 2460 bytes 03-build_abe-binutils/console.log.xz | Bin 35608 -> 35172 bytes 04-build_abe-gcc/console.log.xz | Bin 205732 -> 203540 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9208 -> 9156 bytes 07-build_abe-glibc/console.log.xz | Bin 244168 -> 241260 bytes 08-build_abe-gdb/console.log.xz | Bin 35208 -> 35228 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3860 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3416 -> 3368 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 1196 -> 1204 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(-)