run-webkit-tests may exit with zero (interrupted: false) when not all tests are run |
||||
Issue descriptionPast example on Android: https://build.chromium.org/p/chromium.webkit/builders/WebKit%20Android%20%28Nexus4%29/builds/68442 Log includes: 13:48:26.404 32546 0 tests ran as expected (1011 didn't run). 13:48:26.404 32546 => Results: 0/1011 tests passed (0.0%) => Tests to be fixed (1011): 13:48:26.405 32546 13:48:26.405 32546 Testing completed. Exit status: 0 Failing results JSON: https://storage.googleapis.com/chromium-layout-test-archives/WebKit_Android__Nexus4_/68442/layout-test-results/failing_results.json In this case, we might expect interrupted to be set to true (not all tests were run), but it was set to false.
,
Dec 18 2017
qyearsley@, should this still be a P2, or is it a P3?
,
Dec 18 2017
Probably P3, since this has been the behavior for a long time, and it's not "time-critical". But, the problem caused by this bug is that it may occasionally hide test failures; this is probably more important than most other P3 issues related to run-webkit-tests.
,
Dec 19
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
,
Dec 21
|
||||
►
Sign in to add a comment |
||||
Comment 1 by qyears...@chromium.org
, Sep 7 2017