Closed Bug 498704 Opened 15 years ago Closed 15 years ago

Intermittent failure in browser_ctrlTab.js on Linux

Categories

(Core :: XUL, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla1.9.2a1

People

(Reporter: mossop, Assigned: dao)

References

Details

(Keywords: intermittent-failure, platform-parity, regression)

TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/browser/base/content/test/browser_ctrlTab.js | With 4 tabs open, Ctrl+Tab opens the preview panel
TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/browser/base/content/test/browser_ctrlTab.js | With 4 tabs open and tab 2 selected, Ctrl+Tab*1 goes back to the previously selected tab - Got 2, expected 0
TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/browser/base/content/test/browser_ctrlTab.js | With 4 tabs open, Ctrl+Tab opens the preview panel
TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/browser/base/content/test/browser_ctrlTab.js | With 4 tabs open and tab 1 selected, Ctrl+Tab*2 goes 2 tabs back in most-recently-selected order - Got 1, expected 2
TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/browser/base/content/test/browser_ctrlTab.js | With 4 tabs open, Ctrl+Tab opens the preview panel
TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/browser/base/content/test/browser_ctrlTab.js | With 4 tabs open and tab 1 selected, Ctrl+Tab*4 goes 0 tabs back in most-recently-selected order - Got 1, expected 2
TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/browser/base/content/test/browser_ctrlTab.js | Ctrl+Tab -> Ctrl+W removes one tab - Got 4, expected 3
TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/browser/base/content/test/browser_ctrlTab.js | Exception thrown - expected 3 open tabs, got 4

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1245164712.1245170826.6590.gz&fulltext=1
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1245170817.1245178694.23799.gz&fulltext=1
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1245171345.1245177056.20023.gz&fulltext=1

Dao believes that this is likely caused by the focus changes.
Whiteboard: [orange]
Probably just a test that isn't waiting for the window to be focused before sending keys to it. Especially likely for a problem that only occurs on Linux.
There's no dedicated window for that test, though. It's a browser chrome test that's loaded in the browser scope.
Component: Tabbed Browser → XUL
Keywords: pp, regression
Product: Firefox → Core
QA Contact: tabbed.browser → xptoolkit.widgets
(In reply to comment #2)
> There's no dedicated window for that test, though. It's a browser chrome test
> that's loaded in the browser scope.

No, but the previous test does open a different window and the test system doesn't wait for windows to close before continuing.
Depends on: 497839
http://hg.mozilla.org/mozilla-central/rev/4ff5b53b3f8e
Assignee: nobody → dao
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9.2a1
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.