Open Bug 1264604 Opened 6 years ago Updated 1 year ago

Findbar focus handling test test_bug360437.xul permafails on Linux only

Categories

(Core :: DOM: Core & HTML, defect, P5)

All
Linux
defect

Tracking

()

Tracking Status
e10s + ---

People

(Reporter: mikedeboer, Unassigned)

References

(Blocks 1 open bug)

Details

Whilst working on bug 1261584 to add e10s coverage to the test_bug360437.xul mochitest-chrome test, a try push revealed that it will permanently fail on all Linux variants we run it on.
Note that this makes the intermittent in bug 1261600 _always_ reproducible.

Thusly, I landed this test as disabled on Linux.

STR:
1. Re-enable 'test_bug360437.xul' in toolkit/content/tests/chrome/chrome.ini
2. Run `./mach mochitest toolkit/content/tests/chrome/test_bug360437.xul in a local debug build
3. Watch it fail ;-)

I get the following debug-build log spew in my console that might someone find useful. Please note that you will get the same log output when you run the test:

[Child 657] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x80004005: file /home/mike/Projects/fx-team/toolkit/xre/nsXREDirProvider.cpp, line 1476
[Parent 541] WARNING: '!NodeIsInTraversalRange(mLast, mPre, startNode, startIndx, endNode, endIndx)', file /home/mike/Projects/fx-team/dom/base/nsContentIterator.cpp, line 477
[Parent 541] WARNING: '!cChild', file /home/mike/Projects/fx-team/dom/base/nsContentIterator.cpp, line 356
[Parent 541] WARNING: '!parent', file /home/mike/Projects/fx-team/dom/base/nsContentIterator.cpp, line 642
[Parent 541] WARNING: '!mFirst', file /home/mike/Projects/fx-team/dom/base/nsContentIterator.cpp, line 375
[Parent 541] WARNING: '!NodeIsInTraversalRange(mLast, mPre, startNode, startIndx, endNode, endIndx)', file /home/mike/Projects/fx-team/dom/base/nsContentIterator.cpp, line 477
[Parent 541] WARNING: '!NodeIsInTraversalRange(mLast, mPre, startNode, startIndx, endNode, endIndx)', file /home/mike/Projects/fx-team/dom/base/nsContentIterator.cpp, line 477
[Parent 541] WARNING: '!cChild', file /home/mike/Projects/fx-team/dom/base/nsContentIterator.cpp, line 356
[Parent 541] WARNING: '!parent', file /home/mike/Projects/fx-team/dom/base/nsContentIterator.cpp, line 642
[Parent 541] WARNING: '!mFirst', file /home/mike/Projects/fx-team/dom/base/nsContentIterator.cpp, line 375
[Parent 541] WARNING: '!NodeIsInTraversalRange(mLast, mPre, startNode, startIndx, endNode, endIndx)', file /home/mike/Projects/fx-team/dom/base/nsContentIterator.cpp, line 477
3 INFO TEST-PASS | toolkit/content/tests/chrome/test_bug360437.xul | Find field isn't focused 
[Parent 541] WARNING: '!NodeIsInTraversalRange(mLast, mPre, startNode, startIndx, endNode, endIndx)', file /home/mike/Projects/fx-team/dom/base/nsContentIterator.cpp, line 477
[Parent 541] WARNING: '!cChild', file /home/mike/Projects/fx-team/dom/base/nsContentIterator.cpp, line 356
[Parent 541] WARNING: '!parent', file /home/mike/Projects/fx-team/dom/base/nsContentIterator.cpp, line 642
[Parent 541] WARNING: '!mFirst', file /home/mike/Projects/fx-team/dom/base/nsContentIterator.cpp, line 375
[Parent 541] WARNING: '!NodeIsInTraversalRange(mLast, mPre, startNode, startIndx, endNode, endIndx)', file /home/mike/Projects/fx-team/dom/base/nsContentIterator.cpp, line 477
[Parent 541] WARNING: '!cChild', file /home/mike/Projects/fx-team/dom/base/nsContentIterator.cpp, line 356
[Parent 541] WARNING: '!parent', file /home/mike/Projects/fx-team/dom/base/nsContentIterator.cpp, line 642
[Parent 541] WARNING: '!mFirst', file /home/mike/Projects/fx-team/dom/base/nsContentIterator.cpp, line 375
[Parent 541] WARNING: '!NodeIsInTraversalRange(mLast, mPre, startNode, startIndx, endNode, endIndx)', file /home/mike/Projects/fx-team/dom/base/nsContentIterator.cpp, line 477

... and here the assertion fails due to `document.commandDispatcher.focusedElement` being set to document.body, not the input element that we're expecting.
Oh, I forgot the most interesting bit: it doesn't fail when testing a document in a remote, e10s browser, only the non-remote variant!
Blocks: e10s-tests
tracking-e10s: --- → ?

Bulk-downgrade of unassigned, 4 years untouched DOM/Storage bugs' priority.

If you have reason to believe this is wrong (especially for the severity), please write a comment and ni :jstutte.

Severity: normal → S4
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.