Open Bug 556730 Opened 10 years ago Updated 10 years ago

reftest should provide its own browser.chromeURL

Categories

(Testing :: Reftest, defect)

x86
Linux
defect
Not set

Tracking

(Not tracked)

REOPENED

People

(Reporter: glandium, Unassigned)

Details

As I'm running reftests on xulrunner, I'm actually not running them in firefox, but in a sample application. I haven't taken a deep look at what really happens and why, but would appreciate any help as to what to look at specifically. Anyways, the sample application I use to run the reftests has no specific chrome, and only a few preferences. Everything else is provided by XRE.

This is the error I get:
REFTEST TEST-UNEXPECTED-FAIL | file:///tmp/buildd/xulrunner-1.9.2.2/js/src/tests/jsreftest.html?test=js1_5/Regress/regress-351116.js | Unknown :0: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIDOMJSWindow.open]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: file:///tmp/buildd/xulrunner-1.9.2.2/js/src/tests/js1_5/Regress/regress-351116.js :: test :: line 59"  data: no] item 1
I found what is missing: a browser.chromeURL setting and corresponding chrome ; even a simple chrome.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
Or maybe this bug should be kept to have reftest have its own browser.chromeURL ?
Assignee: general → nobody
Status: RESOLVED → REOPENED
Component: JavaScript Engine → Reftest
Product: Core → Testing
QA Contact: general → reftest
Resolution: INVALID → ---
Summary: js1_5/Regress/regress-351116.js fails when run in a sample application that is not firefox → reftest should provide its own browser.chromeURL
You need to log in before you can comment on or make changes to this bug.