Closed
Bug 811296
Opened 13 years ago
Closed 13 years ago
Test RestartChangeArchitecture.js causes a hang in testruns
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect, P1)
Tracking
(firefox18 affected)
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| firefox18 | --- | affected |
People
(Reporter: AndreeaMatei, Unassigned)
References
()
Details
(Whiteboard: [mozmill-test-failure])
Another aborted testrun, also on Aurora with Linux, which failed at the skipped testRestartChangeArchitecture:
http://10.250.73.243:8080/job/mozilla-aurora_functional/1638/console
TEST-START | /tmp/tmpzeU2v8.mozmill-tests/tests/functional/restartTests/testRestartChangeArchitecture/test1.js | setupModule
WARNING | test1.js::setupModule | (SKIP) Architecture changes only supported on OSX 10.6
TEST-START | /tmp/tmpzeU2v8.mozmill-tests/tests/functional/restartTests/testRestartChangeArchitecture/test1.js | testArchitecture64bit
WARNING | test1.js::testArchitecture64bit | (SKIP) setupModule failed.
TEST-START | /tmp/tmpzeU2v8.mozmill-tests/tests/functional/restartTests/testRestartChangeArchitecture/test2.js | setupModule
WARNING | test2.js::setupModule | (SKIP) Architecture changes only supported on OSX 10.6
TEST-START | /tmp/tmpzeU2v8.mozmill-tests/tests/functional/restartTests/testRestartChangeArchitecture/test2.js | testRestartedNormally
WARNING | test2.js::testRestartedNormally | (SKIP) setupModule failed.
TEST-START | /tmp/tmpzeU2v8.mozmill-tests/tests/functional/restartTests/testRestartChangeArchitecture/test3.js | setupModule
WARNING | test3.js::setupModule | (SKIP) Architecture changes only supported on OSX 10.6
TEST-START | /tmp/tmpzeU2v8.mozmill-tests/tests/functional/restartBuild timed out (after 60 minutes). Marking the build as aborted.
Build was aborted
Recording test results
Email was triggered for: Aborted
Sending email for trigger: Aborted
Sending email to: mozmill-ci@mozilla.org
Finished: ABORTED
| Reporter | ||
Updated•13 years ago
|
Updated•13 years ago
|
Priority: -- → P1
Comment 1•13 years ago
|
||
This should have been fixed now with the final landing of the patch on bug 814430 on the mozilla-beta branch.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•