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 50287b4583 159: onsuccess: #72: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 3dd7868868 158: onsuccess: #71: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 0ea1a1debc 157: onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 435a60b6be 156: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 1a88d6157b 155: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 150a7a7ab8 154: onsuccess: #66: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 59ea0ba2a2 153: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 36cc516bdf 152: force: #64: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards 82ea13a5e3 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 5c00bbb8cd 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 3ce94a3232 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 5eea02e48b 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] discards 82622db527 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 28085706bf 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 083943b2da 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards a72d1c1c94 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] discards 559e5a8055 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 5f6a2bff8d 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards d176cd384c 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 2e90a66d1d 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 6dacee8155 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards cac0dc87be 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards af3ba8a336 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 3be78fd6c8 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards f80cde72b8 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] discards 6930b6a616 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] discards 165eed8d99 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards ad0fde7068 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 3c6038ced2 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] discards 5e11496177 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 5d525a2ae0 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards fc6ff139b0 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards b9907fce73 127: force: #27: : Failure after baseline build: no new commits discards eda025c26a 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards f64715787f 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 429ad6b1cc 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 2b73982b34 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 21603be7ba 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 664f86eb7a 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards aed5056461 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards bb1f3b190d 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 31d383a258 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards b95078894c 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 15f70dc6c0 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards a262b7733d 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards b82f2e7c0c 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards bde0b2dd4f 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards d6eacbef70 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 6774ed8a98 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 135fed6ef7 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards ef5ea102c7 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards da0186b99f 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 9b15850961 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 9867bb56f8 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] discards d653cf35b8 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 7686430884 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] discards 7b3fb2707b 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] discards 69bdfd231b 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] discards 578ba6dfdf 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] discards 26c6bbd5c3 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits discards 7e958b436d 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] discards 918c73b64e 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] discards ae309158a1 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] discards 7196247442 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] discards 3d625a73cd 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] discards 3dfe5d5082 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards ffd2b7706a 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards e54354fdb5 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] discards b93b31ae31 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards 41dc7a653c 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 33ba4f2be2 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] discards 128c76efe2 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards 9993c7a7b5 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 2427b2ae66 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] discards fb679f383e 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] discards 2995524d65 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 8a0c0bf0e8 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 50cf2b7df0 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] discards e22ccd048f 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards e30ee9afad 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards feaf9524fd 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 33fb9ddb79 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards eb3e29187b 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] discards 38ae54d97e 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] discards 02c5c63148 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] discards bbfc64e40a 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards eb24085588 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards b3a9b34ccf 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] discards f5146ccbeb 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] discards 765eebcfc0 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] discards b66f6c537c 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 1a13fb8fa5 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] discards d6fba00d38 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards bd019d1659 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] discards 15d8ebd4ab 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] discards 0eb5ef42d6 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] discards 0b1a4cd3ca 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards b257df70ee 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] discards 6cc817de01 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] discards c72e42dbe2 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] discards b2e351b040 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] new 1933a576a8 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] new fee876adbe 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] new 53bc7b66bf 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] new c77a7ebf8b 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] new 60b33d6585 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new e69eb7770a 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] new 10dfd744ae 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] new c9b0250d19 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] new 075c7e47c3 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 5af1a534b6 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] new 4356b979f0 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new ae6d64c990 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] new 3815fdd8eb 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] new 10e1a378c3 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] new 3594236bd1 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new c801ee0282 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 9f636bc25b 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] new b12477c781 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] new b9e05b8276 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] new 9b4af0226a 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 42093a842f 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new cf76ddfb4c 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new b5b827f916 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new a410477979 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] new 5f25d6bee3 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new e722109d19 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 5f449a66f2 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] new 3c298e1c1f 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] new c71cdc7369 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new 21e0547224 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new b3fea17ade 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] new 352e6548e4 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new a572770b0b 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 7c6a8d6408 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] new 05501f0195 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 94b3c3a8da 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 60b6368f5b 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] new a1e08d02f2 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] new 9433671b72 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] new 0a07104428 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] new 5ab068d625 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] new aa0ef2f54e 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits new 6c3f473b31 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] new ee73c9b7b3 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] new d236d3f05a 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] new 36079ba398 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] new b4d5b134cb 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 8bdce95354 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] new de24847af9 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 801183aed4 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 3c463a1610 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 45dec5a849 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 63bbb38cc7 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new bd3dd4c7e5 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new bc406dccce 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new 4139e02e87 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new c828691be2 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 54054f7d00 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 61ed8431b4 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 27fe4ef0c5 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 13fb83a550 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 8afee5f007 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new b684fd89db 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 29cf133efb 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 8923f7bce9 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 4ea1c59196 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new 0876680317 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 83978e248d 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 2471968d3e 127: force: #27: : Failure after baseline build: no new commits new 3014698a94 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 2b54c821ff 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new c54a7302dc 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 876cabe731 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] new 836495465b 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 16b3c53c32 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new e47f56fad9 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] new ed4c029783 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] new c1e5724703 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 0b07fff1be 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new abf7ac36ea 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 6eeb4bd3ed 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new b01a0c047f 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 7438987995 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 29413a6418 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 3a7301d600 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new f2b26e9817 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] new c66d594d7c 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new b62b7e3fdc 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new ad824e9419 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new a2cc9a5c44 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] new 204178ef21 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 8ac987e68d 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new cfb2bdd28b 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 1f8de96a0e 152: force: #64: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new c3eb3cd99b 153: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new 847422639e 154: onsuccess: #66: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new a3fd1eb6ef 155: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 976973fe22 156: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 97801e041b 157: onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 90a350a2cf 158: onsuccess: #71: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 04348cdc5a 159: onsuccess: #72: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 8d092fb111 160: onsuccess: #73: 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 (50287b4583) \ 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 14452 -> 14460 bytes 01-reset_artifacts/console.log.xz | Bin 2124 -> 2192 bytes 02-prepare_abe/console.log.xz | Bin 2456 -> 2448 bytes 03-build_abe-binutils/console.log.xz | Bin 36484 -> 35004 bytes 04-build_abe-gcc/console.log.xz | Bin 204112 -> 204692 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8460 -> 8524 bytes 07-build_abe-glibc/console.log.xz | Bin 242248 -> 241632 bytes 08-build_abe-gdb/console.log.xz | Bin 35532 -> 35112 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3836 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3492 -> 3344 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(-)