css3/filters/effect-contrast-hw.html flakily failing |
||||||
Issue descriptioncss3/filters/effect-contrast-hw.html started failing frequently on "WebKit Linux Trusty (dbg)" bot today. https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Linux%20Trusty%20%28dbg%29 Looking at the flakiness dashboard for this test, it has been flaky for a while it seems. +cc wangxianzhu,fmalita since it looks like you were the last ones to rebaseline this test, so you might know who best to route this bug to.
,
Dec 13 2016
Perhaps we can just add [ Debug ] css3/filters/effect-contrast-hw.html [ WontFix ] in NeverFixTests. fmalita@ wdyt?
,
Dec 13 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/2a395c271ee5709e7132693561402d03dd3a7c1f commit 2a395c271ee5709e7132693561402d03dd3a7c1f Author: Antony Sargent <asargent@chromium.org> Date: Tue Dec 13 00:11:08 2016 Change expectations for css3/filters/effect-contrast-hw.html on linux The test has been flakily failing on linux today TBR=wangxianzhu@chromium.org BUG=673539 Review-Url: https://codereview.chromium.org/2571553004 . Cr-Commit-Position: refs/heads/master@{#437965} [modify] https://crrev.com/2a395c271ee5709e7132693561402d03dd3a7c1f/third_party/WebKit/LayoutTests/TestExpectations
,
Dec 13 2016
The random order bots are producing similar results as on linux dbg bot: https://storage.googleapis.com/chromium-layout-test-archives/WebKit_Linux_-_RandomOrder/1471/layout-test-results/results.html ( bug 663581 ).
,
Dec 13 2016
[Sheriff update] Assigning to asargent@ due to the update in comment #3. No failure since that landed, but I think it needs to bake some more before closing.
,
Dec 13 2016
My sheriff stint ended yesterday
,
Dec 19 2016
This was also failing on Windows in random order: https://build.chromium.org/p/chromium.fyi/builders/WebKit%20Win%20-%20RandomOrder/builds/573 I added it to TestExpectations in this CL: https://codereview.chromium.org/2592473002
,
Apr 5 2017
,
Apr 6 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 9 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by asargent@chromium.org
, Dec 13 2016