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

Categories

(Testing :: General, defect)

Version 3
defect
Not set
normal

Tracking

(firefox58 fixed)

RESOLVED FIXED
mozilla58
Tracking Status
firefox58 --- fixed

People

(Reporter: aryx, Assigned: gbrown)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Assignee: nobody → gbrown
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.
I think bug 961234 is not relevant in this case...though it might be in another.
See Also: → 1403565
See Also: → 1406407
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 gbrown@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/925b016fb5c0
Further improve test-verify behavior when reftest reference file is modified; r=jmaher
https://hg.mozilla.org/mozilla-central/rev/925b016fb5c0
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla58
You need to log in before you can comment on or make changes to this bug.