Intermittent browser_bug556061.js | Found an unexpected tab at the end of test run: about:blank

NEW
Unassigned

Status

()

Firefox
Address Bar
P3
normal
2 years ago
a year ago

People

(Reporter: RyanVM, Unassigned)

Tracking

({intermittent-failure, leave-open})

Trunk
intermittent-failure, leave-open
Points:
---

Firefox Tracking Flags

(firefox49 affected, firefox50 affected)

Details

(Whiteboard: [fxsearch])

Attachments

(1 attachment)

(Reporter)

Description

2 years ago
This is extremely frequent now that this is running in the mochitest-clipboard job. Not sure if it's related to bug 1274299 or not (or whether that will hit anymore with the clipboard split). Gijs, do you have cycles to look into this?

https://treeherder.mozilla.org/logviewer.html#?job_id=9557993&repo=fx-team#L4911
Flags: needinfo?(gijskruitbosch+bugs)
I'll have to make some, as I just requested uplift on all those URL bar fixes. Meanwhile, do you know what's up with that log viewer? Trying to actually view anything produces "The long no longer exists or has expired." ?
Flags: needinfo?(gijskruitbosch+bugs) → needinfo?(ryanvm)
Stupid bugzilla. Can't keep needinfo flags anymore if also requesting info from someone else. :-\
Flags: needinfo?(gijskruitbosch+bugs)
(Reporter)

Comment 3

2 years ago
Bug 1275796. Full logs still work in the mean time.
Flags: needinfo?(ryanvm)

Comment 5

2 years ago
11 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-inbound: 9
* fx-team: 1
* ash: 1

Platform breakdown:
* linux32: 6
* linux64: 5

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1275963&startday=2016-05-23&endday=2016-05-29&tree=all
(In reply to :Gijs Kruitbosch from comment #4)
> remote:  
> https://treeherder.mozilla.org/#/jobs?repo=try&revision=57e2b6b96d41

This seems to not help.

Ryan, can you clarify the 'very frequent' thing? I don't see this on brass stacks: https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1275963&startday=2016-05-25&endday=2016-06-01&tree=all
Flags: needinfo?(ryanvm)
(Reporter)

Comment 7

2 years ago
When I filed this, there were 9 instances in less than a day, which was a pace that was trending for the top 10. Hard to make much in the way of judgments since then, however, since we're in the middle of a holiday week and I'm sure that push volumes are down.
Flags: needinfo?(ryanvm)

Comment 8

2 years ago
29 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-inbound: 19
* fx-team: 8
* try: 1
* ash: 1

Platform breakdown:
* linux64: 19
* linux32: 10

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1275963&startday=2016-05-30&endday=2016-06-05&tree=all

Comment 9

2 years ago
49 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-inbound: 25
* fx-team: 16
* mozilla-central: 3
* try: 2
* mozilla-aurora: 2
* ash: 1

Platform breakdown:
* linux64: 40
* linux32: 9

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1275963&startday=2016-06-06&endday=2016-06-12&tree=all

Comment 10

2 years ago
25 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-inbound: 17
* fx-team: 5
* try: 2
* mozilla-central: 1

Platform breakdown:
* linux64: 21
* linux32: 3
* windows7-32: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1275963&startday=2016-06-13&endday=2016-06-19&tree=all

Comment 11

2 years ago
40 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-inbound: 22
* fx-team: 8
* try: 3
* mozilla-central: 3
* mozilla-aurora: 3
* autoland: 1

Platform breakdown:
* linux64: 30
* linux32: 10

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1275963&startday=2016-06-20&endday=2016-06-26&tree=all

Comment 12

2 years ago
27 automation job failures were associated with this bug yesterday.

Repository breakdown:
* mozilla-inbound: 17
* fx-team: 5
* mozilla-central: 2
* mozilla-aurora: 2
* autoland: 1

Platform breakdown:
* linux64: 26
* linux32: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1275963&startday=2016-06-27&endday=2016-06-27&tree=all

Comment 13

2 years ago
Its the #3 intermittent today:

https://brasstacks.mozilla.com/orangefactor/?display=OrangeFactor&endday=2016-06-28&startday=2016-06-28&tree=trunk
Flags: needinfo?(gijskruitbosch+bugs)

Comment 14

2 years ago
22 automation job failures were associated with this bug yesterday.

Repository breakdown:
* mozilla-inbound: 18
* fx-team: 3
* mozilla-central: 1

Platform breakdown:
* linux64: 22

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1275963&startday=2016-06-28&endday=2016-06-28&tree=all
The majority of these failures are now on taskcluster jobs. That's partly because taskcluster Linux 64 pgo and Linux 64 asan jobs run more frequently than their buildbot counterparts. But even taking that into account, it seems to me that this failure happens more frequently on taskcluster than on buildbot.

:jmaher -- Any thoughts on how I might modify the taskcluster config to help make this more reliable?
Flags: needinfo?(jmaher)
Why did this spike so suddenly? Has anyone tried bisecting it by retriggering? Shouldn't be too hard given it started so suddenly... unless it's the result of an infra change? Leaving ni for jmaher in that respect. I don't have any obvious ideas - I tried to reproduce this a month ago and failed, seems unlikely it'll be any different today.
Flags: needinfo?(gijskruitbosch+bugs)
The spike around June 26 is because that's when we started running Linux x64 asan tests on taskcluster. The taskcluster tests are the same as the traditional tests run from buildbot. For a trial period, the buildbot tests still run, in addition to the taskcluster ones: So Linux x64 asan mochitest-clipboard and mochitest-clipboard-e10s now run twice as often as they did previous to June 26. In fact, it's worse than that, because the taskcluster tests sometimes run when the buildbot ones don't (they are scheduled more aggressively). And on top of that, I think this failure has a greater chance of occuring on a taskcluster run than on buildbot, which is unusual and unexpected to me, and what I'm asking jmaher about.

That said, it is still not hard to find this failure on buildbot -- it's not all taskcluster's fault!

Comment 18

2 years ago
63 automation job failures were associated with this bug yesterday.

Repository breakdown:
* mozilla-inbound: 28
* autoland: 18
* fx-team: 14
* mozilla-central: 2
* try: 1

Platform breakdown:
* linux64: 62
* linux32: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1275963&startday=2016-06-29&endday=2016-06-29&tree=all
this is the clipboard job and this test is the first test to run in the browser-chrome portion of the test.  So what test is leaving the previous tab open?  I believe this is marionette which we use to load the addons to avoid signing.

I believe browser chrome has a control window, then the browser window, this looks to be accurate based on a screenshot from a failure:
https://public-artifacts.taskcluster.net/AvHtCpepTXSSD1ZWQ10LMw/0/public/test_info//mozilla-test-fail-screenshot_MmIKKy.png

I am not sure where in the process Marionette interferes.

:ahal, does Marionette open a tab up upon launch of the browser?
Flags: needinfo?(jmaher) → needinfo?(ahalberstadt)
Created attachment 8766835 [details] [diff] [review]
use desktop-test-xlarge for linux 64 mochitest-clipboard

I'd prefer to find the root cause of this failure, but here's an alternative: Using a faster worker type appears to effectively avoid this failure.

https://treeherder.mozilla.org/#/jobs?repo=try&revision=279a8d28b5975f5be1e26b66fe194c8c2268bb25

(Compare to normal: https://treeherder.mozilla.org/#/jobs?repo=try&revision=919d5739b7678fce00f1a45adf86fca44d7f3ae5 )
Attachment #8766835 - Flags: review?(jmaher)
Comment on attachment 8766835 [details] [diff] [review]
use desktop-test-xlarge for linux 64 mochitest-clipboard

Review of attachment 8766835 [details] [diff] [review]:
-----------------------------------------------------------------

ok, lets just get it green!
Attachment #8766835 - Flags: review?(jmaher) → review+
(In reply to Joel Maher (:jmaher) from comment #19)
> this is the clipboard job and this test is the first test to run in the
> browser-chrome portion of the test.  So what test is leaving the previous
> tab open?  I believe this is marionette which we use to load the addons to
> avoid signing.
> 
> I believe browser chrome has a control window, then the browser window, this
> looks to be accurate based on a screenshot from a failure:
> https://public-artifacts.taskcluster.net/AvHtCpepTXSSD1ZWQ10LMw/0/public/
> test_info//mozilla-test-fail-screenshot_MmIKKy.png
> 
> I am not sure where in the process Marionette interferes.
> 
> :ahal, does Marionette open a tab up upon launch of the browser?

Not that I'm aware of.. I mean aside from the normal tab that is opened when you regularly launch a browser
Flags: needinfo?(ahalberstadt)

Comment 23

2 years ago
Pushed by gbrown@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/ec69950a1438
Use desktop-test-xlarge for linux x64 mochitest-clipboard tests; r=jmaher
Leave open since my patch won't affect buildbot jobs and may not fully eliminate failures on taskcluster.
Keywords: leave-open

Comment 25

2 years ago
17 automation job failures were associated with this bug yesterday.

Repository breakdown:
* mozilla-inbound: 12
* mozilla-central: 4
* autoland: 1

Platform breakdown:
* linux64: 16
* linux32: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1275963&startday=2016-06-30&endday=2016-06-30&tree=all

Comment 27

2 years ago
189 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-inbound: 85
* fx-team: 43
* autoland: 42
* mozilla-central: 13
* try: 4
* mozilla-aurora: 2

Platform breakdown:
* linux64: 183
* linux32: 6

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1275963&startday=2016-06-27&endday=2016-07-03&tree=all

Comment 28

2 years ago
34 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* autoland: 11
* fx-team: 9
* mozilla-inbound: 4
* mozilla-central: 4
* mozilla-aurora: 4
* try: 1
* ash: 1

Platform breakdown:
* linux64: 22
* linux32: 12

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1275963&startday=2016-07-04&endday=2016-07-10&tree=all

Comment 29

2 years ago
33 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* fx-team: 11
* mozilla-inbound: 9
* autoland: 7
* mozilla-central: 3
* try: 1
* mozilla-aurora: 1
* ash: 1

Platform breakdown:
* linux64: 20
* linux32: 13

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1275963&startday=2016-07-11&endday=2016-07-17&tree=all

Comment 30

2 years ago
17 automation job failures were associated with this bug yesterday.

Repository breakdown:
* mozilla-inbound: 10
* fx-team: 4
* autoland: 2
* mozilla-central: 1

Platform breakdown:
* linux64: 15
* linux32: 2

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1275963&startday=2016-07-22&endday=2016-07-22&tree=all

Comment 31

2 years ago
54 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-inbound: 21
* fx-team: 13
* try: 8
* autoland: 6
* mozilla-central: 4
* mozilla-aurora: 2

Platform breakdown:
* linux64: 31
* linux32: 23

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1275963&startday=2016-07-18&endday=2016-07-24&tree=all
(Reporter)

Updated

2 years ago
status-firefox50: --- → affected

Comment 32

a year ago
Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3
Whiteboard: [fxsearch]
You need to log in before you can comment on or make changes to this bug.