Closed Bug 541436 Opened 15 years ago Closed 11 years ago

browser-chrome autorun runs tests too soon?

Categories

(Testing :: Mochitest, defect)

Product:
Testing
Component:
Mochitest
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: ted, Unassigned)

Details

If I run: make mochitest-browser-chrome TEST_PATH=toolkit/crashreporter/test/browser/browser_aboutCrashesResubmit.js the test fails. If I run: python _tests/testing/mochitest/runtests.py --browser-chrome --test-path=toolkit/crashreporter/test/browser/browser_aboutCrashesResubmit.js wait a second, and click "run tests", the test passes. If I bump the timeout here: http://mxr.mozilla.org/mozilla-central/source/testing/mochitest/browser-harness.xul#133 to 2000, the test passes, so it seems clear that something's not initialized by the time the tests start, but I don't know what. When the test fails, I get two error console entries of the form: TEST-INFO | chrome://mochikit/content/browser/toolkit/crashreporter/test/browser/browser_aboutCrashesResubmit.js | Console message: [JavaScript Error: "uncaught exception: 2147500037"]
Running the equivalent mach command from comment 0 works for me. This was probably fixed by bug 851516 (which was reworked a little in bug 896711).
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Component: BrowserTest → Mochitest
You need to log in before you can comment on or make changes to this bug.