Closed
Bug 1030730
Opened 10 years ago
Closed 5 years ago
Fix running jstests from the command line
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: wingo, Assigned: wingo)
References
Details
Attachments
(1 file)
1.36 KB,
patch
|
Details | Diff | Splinter Review |
Since bug 1029059, jstests no longer work from the command line. The attached patch fixes it.
Assignee | ||
Comment 1•10 years ago
|
||
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → wingo
Assignee | ||
Updated•10 years ago
|
Attachment #8446505 -
Flags: review?(jorendorff)
Comment 2•10 years ago
|
||
Does this exhibit the same behavior for all the tests that test XPCOMABI?
Flags: needinfo?(wingo)
Comment 3•10 years ago
|
||
(I backed out bug 1029059 on inbound, but I wouldn't object to being able to check the target in a much cleaner way in jstests, which is what this patch does.)
Assignee | ||
Comment 4•10 years ago
|
||
(In reply to Nathan Froyd (:froydnj) from comment #2) > Does this exhibit the same behavior for all the tests that test XPCOMABI? I believe so. If you grep the tests for ABI you'll find that the only check that's made is match(/x86_64/), which this patch preserves.
Flags: needinfo?(wingo)
Comment 5•10 years ago
|
||
Comment on attachment 8446505 [details] [diff] [review] Fix running jstests from the command line Review of attachment 8446505 [details] [diff] [review]: ----------------------------------------------------------------- Clearing review. The offending patch was apparently backed out. It looks like this would be the right change though, so r=me if it recurs!
Attachment #8446505 -
Flags: review?(jorendorff)
Assignee | ||
Comment 7•5 years ago
|
||
Closing as invalid as no activity in 5 years and of course jstests run just fine from the command line :)
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•