Closed
Bug 776493
Opened 12 years ago
Closed 12 years ago
Intermittent DOMCore/tests/approved/test_Range-insertNode.html | 15,16: resulting DOM for range [document.documentElement, 0, document.documentElement, 1], node xmlDoc; Exception seems to not be a DOMException? [Exception... "Node cannot be inserted...
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: emorley, Unassigned)
References
Details
(Keywords: intermittent-failure)
Rev3 Fedora 12 mozilla-inbound pgo test mochitests-2/5 on 2012-07-22 19:09:25 PDT for push c07793b7dc10
slave: talos-r3-fed-070
https://tbpl.mozilla.org/php/getParsedLog.php?id=13761417&tree=Mozilla-Inbound
{
6491 ERROR TEST-UNEXPECTED-FAIL | /tests/dom/imptests/webapps/DOMCore/tests/approved/test_Range-insertNode.html | 15,16: resulting DOM for range [document.documentElement, 0, document.documentElement, 1], node xmlDoc; Exception seems to not be a DOMException? [Exception... "Node cannot be inserted at the specified point in the hierarchy" code: "3" nsresult: "0x80530003 (HierarchyRequestError)" location: "http://mochi.test:8888/tests/dom/imptests/webapps/DOMCore/tests/approved/common.js Line: 883"]
...
...
2 ERROR TEST-UNEXPECTED-FAIL | /tests/dom/indexedDB/test/test_transaction_lifetimes.html | request.transaction should still be set - got null, expected [object IDBTransaction]
}
Comment 1•12 years ago
|
||
My best bet is PGO miscompiling something.
Comment 2•12 years ago
|
||
Or racy test? The test has all sorts of load event listeners
Comment 3•12 years ago
|
||
Well, 2 at least :)
Comment 4•12 years ago
|
||
The failure in test_Range-insertNode.html is caused by getDomExceptionName throwing an exception, here:
https://hg.mozilla.org/mozilla-central/file/82b6c5885345/dom/imptests/webapps/DOMCore/tests/approved/common.js#l918
The complete function is:
/**
* Given a DOMException, return the name (e.g., "HIERARCHY_REQUEST_ERR").
*/
function getDomExceptionName(e) {
var ret = null;
for (var prop in e) {
if (/^[A-Z_]+_ERR$/.test(prop) && e[prop] == e.code) {
return prop;
}
}
throw "Exception seems to not be a DOMException? " + e;
}
The throw line is actually being hit. That is not even slightly sane -- it means the HierarchyRequestError object doesn't have the proper HIERARCHY_REQUEST_ERR member. It can't be just a race condition. I agree with Ms2ger that it's more likely to be a compiler bug than anything.
Let's see if it reoccurs.
Comment hidden (Legacy TBPL/Treeherder Robot) |
Comment hidden (Legacy TBPL/Treeherder Robot) |
Assignee | ||
Updated•12 years ago
|
Keywords: intermittent-failure
Assignee | ||
Updated•12 years ago
|
Whiteboard: [orange]
Comment hidden (Legacy TBPL/Treeherder Robot) |
Comment hidden (Legacy TBPL/Treeherder Robot) |
Comment hidden (Legacy TBPL/Treeherder Robot) |
Reporter | ||
Comment 10•12 years ago
|
||
Resolving WFM keyword:intermittent-failure bugs last modified >3 months ago, whose whiteboard contains none of:
{random,disabled,marked,fuzzy,todo,fails,failing,annotated,time-bomb,leave open}
There will inevitably be some false positives; for that (and the bugspam) I apologise. Filter on orangewfm.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•