Open Bug 1207980 Opened 4 years ago Updated Last year
"./mach reftest [or crashtest] --filter <foo>" seems to be broken
I'm used to using the --filter option with ./mach reftest to run subsets of tests locally (at times, it's more convenient/specific than naming test directories). However, since bug 1181516 (and a bunch of related bugs) landed recently, attempting to use the --filter option dies with: 0:06.98 REFTEST TEST-UNEXPECTED-FAIL | | EXCEPTION: [Exception... "Component returned failure code: 0x804b000a (NS_ERROR_MALFORMED_URI) [nsIIOService.newURI]" nsresult: "0x804b000a (NS_ERROR_MALFORMED_URI)" location: "JS frame :: chrome://reftest/content/reftest.js :: ReadTopManifest :: line 734" data: no]
Possibly related: using a custom manifest listing a subset of tests also fails. Renaming the custom manifest to crashtests.list *does* work, but that's much to clumsy for everyday use
Summary: "./mach reftest --filter <foo>" seems to be broken → "./mach reftest [or crashtest] --filter <foo>" seems to be broken
Is this still (or again) current? Yesterday I ran into a similar-looking problem (originally reported as bug 1448696), while today (still with the same source checkout, at least initially) reftests did occasionally start running, but as far as I could tell the filter argument didn't have any visible effect judging from the file names scrolling by.
You need to log in before you can comment on or make changes to this bug.