Change csspaint/invalidation-* layout tests to use testharness asserts rather than logging. |
||||
Issue descriptionRecently, the definition of what counts as an "all-PASS" testharness test result was changed, so that extra console logging doesn't make the test count as non-passing. Context: https://bugs.chromium.org/p/chromium/issues/detail?id=687492#c12 This means that some testharness -expected.txt files would now be considered all-PASS, and thus removed: https://cs.chromium.org/chromium/src/third_party/WebKit/LayoutTests/csspaint/invalidation-border-image-expected.txt Ideally, logging in https://cs.chromium.org/chromium/src/third_party/WebKit/LayoutTests/csspaint/resources/test-runner-invalidation-logging.js should be replaced with testharness asserts. ikilpatrick@, glebl@, does that sound reasonable?
,
Oct 30 2017
Is there some hotlist or blocking bug for CSS paint?
,
Oct 31
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
,
Nov 2
|
||||
►
Sign in to add a comment |
||||
Comment 1 by dtapu...@chromium.org
, Oct 30 2017