Push new version of SoM to pick up experimental test suite handling fix |
||||||
Issue descriptionSheriff-o-matic says this has been failing for 8 builds, but I don’t see any failures in the ci page. Turns out the bot is green because it correctly identifies this test suite as experimental and ignores the failure. Obviously sheriff-o-matic should do the same. Sheriff-o-matic failure text: Builder interactive_ui_tests (experimental) on Windows-10-15063 failing on chromium.win/Win10 Tests x64 (dbg) Link: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Win10%20Tests%20x64%20%28dbg%29
,
Sep 11
FWIW, this is making sheriffing *much* harder with a ton of noise. If there's any way to fix this soon, I think it would be much appreciated.
,
Sep 14
Yeah this is weird, it's now showing as 41 out of the last 41 builds have failed for me. But when I go to the bot, it's definitely not a 100% failure.
,
Sep 14
Is this related to https://bugs.chromium.org/p/chromium/issues/detail?id=815006 ? jbudorick@ added some support to the gatekeeper config parser so it *should* ignore "experimental_tests" categories.
,
Sep 21
it is, and I landed https://chromium.googlesource.com/infra/infra/+/4d90c8b790a3ea712967e5462d7b85793b1fdb95 to fix it on august 27. SoM was last deployed on august 10, though.
,
Sep 21
Updating bug title to reflect what's left.
,
Sep 21
just did a push to staging: https://sheriff-o-matic-staging.appspot.com/chromium if that looks ok we can push to prod tomorrow.
,
Oct 2
This happened on 2018-09-28. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ojan@chromium.org
, Sep 10