Closed
Bug 559190
Opened 14 years ago
Closed 13 years ago
test-securable-module.testSecurableModule fails on trunk Firefox
Categories
(Add-on SDK Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: adw, Unassigned)
References
Details
Attachments
(1 file)
|
6.09 KB,
text/plain
|
Details |
With the current SDK tip (9ac87686d6e9) and trunk Firefox, six assertions fail in test-securable-module.testSecurableModule. (They pass on 3.6.) Failing traces attached.
|
Reporter | |
Updated•14 years ago
|
Attachment #438849 -
Attachment mime type: application/octet-stream → text/plain
|
||
Comment 1•14 years ago
|
||
Thanks. CC'ing mrbkap on this, as they might have something to do with a recent commit of his.
|
|
||
Comment 2•14 years ago
|
||
My naive patch for bug 560626 resolves this, but I'm not too happy about it--it mostly gets around the problem by running the CommonJS compliance tests in sandboxes with chrome privileges. Need to talk to mrbkap to figure out exactly what kind of wrapping is now being done implicitly between unprivileged sandboxes and chrome code.
|
||
Comment 3•14 years ago
|
||
The Add-on SDK is no longer a Mozilla Labs experiment and has become a big enough project to warrant its own Bugzilla product, so the "Add-on SDK" product has been created for it, and I am moving its bugs to that product. To filter bugmail related to this change, filter on the word "looptid".
Component: Jetpack SDK → General
Product: Mozilla Labs → Add-on SDK
QA Contact: jetpack-sdk → general
Version: Trunk → unspecified
|
|
||
Comment 4•13 years ago
|
||
Now fixed!
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•