Summary: | Tests reporting FailureNotTested after r217130 | ||
---|---|---|---|
Product: | WebKit | Reporter: | Ryan Haddad <ryanhaddad> |
Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW --- | ||
Severity: | Normal | CC: | ap, dbates, jbedard, jlewis3 |
Priority: | P2 | ||
Version: | WebKit Nightly Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
See Also: |
https://bugs.webkit.org/show_bug.cgi?id=172322 https://bugs.webkit.org/show_bug.cgi?id=172609 https://bugs.webkit.org/show_bug.cgi?id=172610 https://bugs.webkit.org/show_bug.cgi?id=172616 https://bugs.webkit.org/show_bug.cgi?id=172672 https://bugs.webkit.org/show_bug.cgi?id=172772 https://bugs.webkit.org/show_bug.cgi?id=173380 |
Description
Ryan Haddad
2017-05-19 12:44:16 PDT
This means that the test had no output when it was run. We have tests that legitimately have no output, so I'm not sure if r217130 was right. (In reply to Alexey Proskuryakov from comment #2) > We have tests that legitimately have no output, so I'm not sure if r217130 > was right. If the expected file is empty, this logic will not be triggered. I skipped the tests in https://webkit.org/b/172378 so that they would not affect EWS. Of note, there were expectations in place for a few of the tests. I removed them so that the 'Skip' wouldn't be overridden, but we may end up having to restore the original expectations at some point. fetch/closing-while-fetching-blob.html is another (flakily) affected test, could you please skip it and file a new bug? |