Closed
Bug 824163
Opened 12 years ago
Closed 12 years ago
Can't use the jstestbrowser Makefile target with TESTS_PATH
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla20
People
(Reporter: Waldo, Assigned: Waldo)
Details
Attachments
(1 file)
940 bytes,
patch
|
ted
:
review+
|
Details | Diff | Splinter Review |
The current rule:
jstestbrowser: TESTS_PATH?=test-package-stage/jsreftest/tests/
jstestbrowser:
$(MAKE) -C $(DEPTH)/config
$(MAKE) -C $(DEPTH)/js/src/config
$(MAKE) stage-jstests
$(call RUN_REFTEST,$(DIST)/$(TESTS_PATH)/jstests.list --extra-profile-file=$(DIST)/$(TESTS_PATH)/user.js)
$(CHECK_TEST_ERROR)
The --extra-profile-file argument is used to dump a user.js in the profile, with settings such that the browser will allow the JS tests to do privileged stuff like set preferences and the like. That file lives at js/src/tests/user.js. It doesn't live at the location of the test subset being run. So this shouldn't be using $(TESTS_PATH) in that file path.
Attachment #695052 -
Flags: review?(ted)
Updated•12 years ago
|
Attachment #695052 -
Flags: review?(ted) → review+
Assignee | ||
Comment 1•12 years ago
|
||
Target Milestone: --- → mozilla20
Comment 2•12 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•