Closed Bug 1406663 Opened 3 years ago Closed 3 years ago
test-verify: "REFTEST TEST-UNEXPECTED-FAIL | | EXCEPTION: No tests to run" when running parallel reftests in a directory with few tests
Technically a duplicate of bug 961234, but this will hit test-verify much more because it only runs the modified tests. Push with failures: https://treeherder.mozilla.org/#/jobs?repo=autoland&revision=24cf61e5a04fb68ecc2b41bf3e858199783c5450&filter-resultStatus=testfailed&filter-resultStatus=busted&filter-resultStatus=exception&filter-resultStatus=retry&filter-resultStatus=usercancel&filter-resultStatus=runnable
TV tried to run the reftest layout/reftests/bugs/1404057-noref.html, with manifest entry != 1404057.html 1404057-noref.html TV has a hack to avoid running <test>-ref.html. It looks like -noref, -noref1, -noref2 are also common conventions for reftest reference files.
In the long term, I hope to make this more robust by upgrading our python ReftestManifest class. For now, we can avoid more failures by recognizing more cases: files ending in -noref.html, -noref1.html, etc are likely reference files. https://treeherder.mozilla.org/#/jobs?repo=try&revision=59820bc4db389e7f7d11eaee9c15406f438349c4
Attachment #8917166 - Flags: review?(jmaher)
Attachment #8917166 - Flags: review?(jmaher) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/925b016fb5c0 Further improve test-verify behavior when reftest reference file is modified; r=jmaher
You need to log in before you can comment on or make changes to this bug.