Closed
Bug 866701
Opened 12 years ago
Closed 3 years ago
[OS.File] Cannot initialize OS.Constants in a xpcshell test
Categories
(Toolkit Graveyard :: OS.File, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: sankha, Unassigned)
References
Details
(Whiteboard: [Async:team])
Attachments
(1 file)
|
(deleted),
application/x-javascript
|
Details |
There seems to be some problem if we try to initialize OS.Constants in XPCShell Test.
Here is the error log:
0:00.64 TEST-INFO | e:\developer\mozilla-central\obj-i686-pc-mingw32\_tests\xpcshell\dom\system\tests\unit\test_lazyConstants.js | running test ...
0:00.95 TEST-UNEXPECTED-FAIL | e:\developer\mozilla-central\obj-i686-pc-mingw32\_tests\xpcshell\dom\system\tests\unit\test_lazyConstants.js | test failed (with xpcshell return code: -1073741819), see following log:
0:00.95 >>>>>>>
0:00.95 <<<<<<<
PROCESS-CRASH | e:\developer\mozilla-central\obj-i686-pc-mingw32\_tests\xpcshell\dom\system\tests\unit\test_lazyConstants.js | application crashed [Unknown top frame]
Crash dump filename: e:\developer\mozilla-central\obj-i686-pc-mingw32\_tests\xpcshell\dom\system\tests\unit\20fe4990-4708-495f-bbf8-cca743640f52.dmp
MINIDUMP_STACKWALK not set, can't process dump.
0:00.95 INFO | Result summary:
0:00.95 INFO | Passed: 0
0:00.95 INFO | Failed: 2
0:00.95 INFO | Todo: 0
|
||
Comment 1•12 years ago
|
||
Investigating.
|
|
||
Comment 2•12 years ago
|
||
As a workaround, opening osfile.jsm seems to work:
Cu.import("resource:///gre/modules/osfile.jsm");
|
|
||
Updated•11 years ago
|
Whiteboard: [Async]
|
||
Updated•11 years ago
|
Whiteboard: [Async] → [Async:team]
|
||
Comment 3•3 years ago
|
||
OSFIle is being replaced with IOUtils and PathUtils.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WONTFIX
|
||
Updated•2 years ago
|
Product: Toolkit → Toolkit Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•