Test failure: "The tab with index '0' has been selected" in testPrivateBrowsing/testCloseWindow.js



Mozilla QA
Mozmill Tests
5 years ago
5 years ago


(Reporter: whimboo, Assigned: whimboo)



Mac OS X

Firefox Tracking Flags

(firefox13 unaffected, firefox14 fixed, firefox15 fixed)


(Whiteboard: [qa-])


(1 attachment)



5 years ago
This test is only run on OS X and fails on 15.0a1 and 14.0a2 with "The tab with index '0' has been selected". I can even see 'can't access dead object' failures in the list.


Beside that failure I will also add the skip test entry which really disables the test on other platforms, so we can fix:


This first reported issue could be a regression in Firefox we will have to investigate.


5 years ago
status-firefox13: --- → unaffected
status-firefox14: --- → affected
status-firefox15: --- → affected

Comment 1

5 years ago
The first time this failure happened was with 14.0a1 (20120326031149). I did a test with the builds 2012032503 and 2012032603, and can approve that this is a regression in Firefox.


I will do some manual tests to see what's going on here and if this is only tied to automation.

Comment 2

5 years ago
This is a timing issue. Including an additional sleep before selecting a tab after restoring the closed window fixes the problem. Probably one of the changesets has been caused a slowness  in reopening the window. Looks like I will have to do a bisect.


5 years ago
Depends on: 753763

Comment 3

5 years ago
(In reply to Henrik Skupin (:whimboo) from comment #1)
> The first time this failure happened was with 14.0a1 (20120326031149). I did
> a test with the builds 2012032503 and 2012032603, and can approve that this
> is a regression in Firefox.
> Pushlog:
> http://hg.mozilla.org/mozilla-central/
> pushloghtml?fromchange=20a01901480f&tochange=ba4983d9c1f9

I'm not able to build Firefox for changesets in between this range. So can't really figure out what could have been caused this regression.

But as I have found out this issue has something to do with Session Store. When we close the last window while staying in PB mode and leaving PB mode right after, the window gets reopened. The test doesn't fail if I add a little sleep right before we start to work with any of the elements. Also doing those steps manually doesn't show an issue. It's only visible with the current version of the Mozmill test and I can clearly confirm the regression range.

We have to get bug 753763 implemented for Mozmill 2.0. For 1.5 I would propose that we make use of a sleep call which is enough. If we will have a 1.5.13 release I will make sure to get the feature also landed there.

Comment 4

5 years ago
Created attachment 622713 [details] [diff] [review]
Patch v1

This fixes:
* The wrong tab being selected after the closed window has been restored
* Correctly skip the test
* Minor adjustments
Attachment #622713 - Flags: review?(dave.hunt)
Comment on attachment 622713 [details] [diff] [review]
Patch v1

Looks good, and passes! r+
Attachment #622713 - Flags: review?(dave.hunt) → review+

Comment 6

5 years ago
Landed on default as:

I will wait for tomorrows results before the landing on older branches.
Last Resolved: 5 years ago
status-firefox15: affected → fixed
Resolution: --- → FIXED

Comment 7

5 years ago
Latest testrun on OS X for Nightly didn't show this failure:

Because the skip code changes will also affect other branches I have this landed across branches:

http://hg.mozilla.org/qa/mozmill-tests/rev/627f9ed384e5 (aurora)
http://hg.mozilla.org/qa/mozmill-tests/rev/cbad36563bc0 (beta)
http://hg.mozilla.org/qa/mozmill-tests/rev/f9c002f2d6cc (release)
http://hg.mozilla.org/qa/mozmill-tests/rev/959c0d983643 (esr)
status-firefox14: affected → fixed
Keywords: regressionwindow-wanted


5 years ago
Whiteboard: [qa-]
You need to log in before you can comment on or make changes to this bug.