Closed Bug 609040 Opened 15 years ago Closed 15 years ago

remote reftests need to be smarter with the webserver and for jsreftests

Categories

(Testing :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jmaher, Unassigned)

Details

(Whiteboard: [mobile_unittests])

Attachments

(1 file)

ok, this patch makes a lot of assumptions as well as life easier. Here are the two things this patch does: 1) does a symlink to jsreftest so we can access http://ip:port/jsreftest/tests/jstests.list (or whatever subpath). This allows for a non hacking version of jsreftests to be run, but requires a test package 2) fixes the manifest definition in the command line to not require ip:port. This is discovered automtically on linux or by using the --remote-webserver --http-port options on the command line. example of a working command line: python remotereftest.py --deviceIP=192.168.1.101 --xre-path=../../bin --app=org.mozilla.fennec jsreftest/tests/ecma/Types/jstests.list
Attachment #487617 - Flags: review?(ctalbert)
Comment on attachment 487617 [details] [diff] [review] use the ip:port for manifest from cli and symlink jsreftests to webserver (1.0) We should probably file a follow-on for windows support, but we're targeting linux for our remote controllers so this will work for now. Let's get this in so we can use it in buildbotland. r+ with follow up bug.
Attachment #487617 - Flags: review?(ctalbert) → review+
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Component: New Frameworks → General
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: