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 8d092fb111 160: onsuccess: #73: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 04348cdc5a 159: onsuccess: #72: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 90a350a2cf 158: onsuccess: #71: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 97801e041b 157: onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 976973fe22 156: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards a3fd1eb6ef 155: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 847422639e 154: onsuccess: #66: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards c3eb3cd99b 153: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 1f8de96a0e 152: force: #64: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards cfb2bdd28b 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 8ac987e68d 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 204178ef21 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards a2cc9a5c44 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] discards ad824e9419 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards b62b7e3fdc 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards c66d594d7c 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards f2b26e9817 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] discards 3a7301d600 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 29413a6418 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 7438987995 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards b01a0c047f 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 6eeb4bd3ed 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards abf7ac36ea 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 0b07fff1be 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards c1e5724703 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards ed4c029783 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] discards e47f56fad9 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] discards 16b3c53c32 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 836495465b 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 876cabe731 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] discards c54a7302dc 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 2b54c821ff 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 3014698a94 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 2471968d3e 127: force: #27: : Failure after baseline build: no new commits discards 83978e248d 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 0876680317 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 4ea1c59196 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 8923f7bce9 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 29cf133efb 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards b684fd89db 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 8afee5f007 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 13fb83a550 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 27fe4ef0c5 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 61ed8431b4 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 54054f7d00 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards c828691be2 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 4139e02e87 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards bc406dccce 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards bd3dd4c7e5 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 63bbb38cc7 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 45dec5a849 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 3c463a1610 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 801183aed4 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards de24847af9 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 8bdce95354 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] discards b4d5b134cb 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 36079ba398 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] discards d236d3f05a 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] discards ee73c9b7b3 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] discards 6c3f473b31 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] discards aa0ef2f54e 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits discards 5ab068d625 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] discards 0a07104428 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] discards 9433671b72 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] discards a1e08d02f2 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] discards 60b6368f5b 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] discards 94b3c3a8da 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 05501f0195 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 7c6a8d6408 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] discards a572770b0b 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards 352e6548e4 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards b3fea17ade 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] discards 21e0547224 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards c71cdc7369 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 3c298e1c1f 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] discards 5f449a66f2 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] discards e722109d19 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 5f25d6bee3 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards a410477979 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] discards b5b827f916 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards cf76ddfb4c 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards 42093a842f 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 9b4af0226a 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards b9e05b8276 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] discards b12477c781 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] discards 9f636bc25b 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] discards c801ee0282 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 3594236bd1 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 10e1a378c3 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] discards 3815fdd8eb 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] discards ae6d64c990 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] discards 4356b979f0 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 5af1a534b6 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] discards 075c7e47c3 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards c9b0250d19 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] discards 10dfd744ae 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] discards e69eb7770a 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] discards 60b33d6585 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards c77a7ebf8b 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] discards 53bc7b66bf 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] discards fee876adbe 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] new a8927301b2 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] new a620ed41b3 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] new 4786d983b8 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] new a81b79ee68 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new 53564a6bd3 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] new 72f4bbeede 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] new e873361a18 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] new 4677aba0ef 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 5e0b77db9c 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] new 0bb20076f5 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new 81896a10f5 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] new 5f132361ee 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] new 62323feb44 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] new 153dd863e5 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new 8620875d2a 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new aa1bb0c2df 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] new 5387610995 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] new 57f7b5e916 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] new 9c91dc0bb9 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 666a61aea8 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new f7afee49f0 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new 4a06057493 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 1099c77491 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] new 768870564d 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new cd98e15a0d 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 6a241c52f3 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] new 24d5287852 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] new 44be3df572 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new c5dc6b9a92 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 84ca986529 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] new 04651cfde3 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new ee3d1a64c3 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 5cc164d71c 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] new 80e4d7ac36 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 278f91b998 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 901efe79c8 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] new 8ccec2153c 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] new 1ba0f684a8 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] new bc16a0c4d5 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] new 92dcd61792 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] new 8f876f23e8 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits new 81590fa7c2 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] new acf92ecd49 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] new cc514cb62d 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] new 6cabac36d4 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] new 595e4a8cc1 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new aabdbcaff8 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] new f191fa18b2 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 7ec8470fb4 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 07b17ddaaa 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new c79497880b 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 6a73b98829 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 4050457503 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new ff0420daa3 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new 221d2e045c 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 796dda4f7c 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 2245144bae 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new f96a8d84f4 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 9b7e50c834 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new e668f01683 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new d07b9c5d62 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new c84198f13c 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new ff84c162a9 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 19d6197230 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new eccb9ab564 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new 10fe42d50a 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 04bf9e80c2 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 07a3c33eaf 127: force: #27: : Failure after baseline build: no new commits new 5a333a26da 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new f20f394dac 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new ce75191fa0 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new f848ae9ad5 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] new a9e9ad9960 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 0bd0d3db7e 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new cf42bae858 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] new 578e7700a2 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] new 703982b33e 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 8fb5a88098 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 4e35c075fb 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new d4586d855f 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new f986a8171d 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new f793c4d364 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 61acdc9db3 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 6db7de1a63 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 2bf19dc8bf 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] new bb6a21662e 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 9fed4e0acc 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new bea9981249 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 21ece2f0dc 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] new f3dec746fa 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 61cca0e7d5 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new b166571778 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 354862db26 152: force: #64: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 22311d3b74 153: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new e725df8af6 154: onsuccess: #66: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new 54d8c351fe 155: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 2dbc5a9b7d 156: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 12dc72ad83 157: onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new ef9945231c 158: onsuccess: #71: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new c4d7d5899e 159: onsuccess: #72: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 1f74f97d8f 160: onsuccess: #73: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 48b0321ee0 161: onsuccess: #74: 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 (8d092fb111) \ 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 14460 -> 14436 bytes 01-reset_artifacts/console.log.xz | Bin 2192 -> 2204 bytes 02-prepare_abe/console.log.xz | Bin 2448 -> 2456 bytes 03-build_abe-binutils/console.log.xz | Bin 35004 -> 35148 bytes 04-build_abe-gcc/console.log.xz | Bin 204692 -> 203776 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8524 -> 9176 bytes 07-build_abe-glibc/console.log.xz | Bin 241632 -> 241284 bytes 08-build_abe-gdb/console.log.xz | Bin 35112 -> 35196 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3884 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3344 -> 3272 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 1196 -> 1196 bytes 11-check_regression/results.compare | 6 ++--- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 46 +++++++++++++++++----------------- 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, 54 insertions(+), 54 deletions(-)