1403009 - Intermittent extensions/cookie/test/browser_test_favicon.js | Test timed out -

Status: RESOLVED INCOMPLETE

(Firefox :: Tabbed Browser, defect, P2)

Description

[Treeherder Bug Filer]

Filed by: wkocher [at] mozilla.com

https://treeherder.mozilla.org/logviewer.html#?job_id=133131027&repo=autoland

https://queue.taskcluster.net/v1/task/SPPnOtNiRmWKe9CAA7VBuw/runs/0/artifacts/public/logs/live_backing.log

Comment 1

[Intermittent Failures Robot]

7 failures in 885 pushes (0.008 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* autoland: 6
* mozilla-beta: 1

Platform breakdown:
* osx-10-10: 5
* macosx64-stylo-disabled: 1
* macosx64-nightly: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1403009&startday=2017-09-25&endday=2017-10-01&tree=all

Comment 2

[Intermittent Failures Robot]

10 failures in 824 pushes (0.012 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* autoland: 4
* mozilla-inbound: 3
* mozilla-beta: 3

Platform breakdown:
* osx-10-10: 6
* macosx64-nightly: 2
* macosx64-stylo-disabled: 1
* macosx64-devedition: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1403009&startday=2017-10-02&endday=2017-10-08&tree=all

Comment 3

[Shian-Yow Wu [:swu]]

The issue first happened at 25 Sep 2017.  Kershaw, this seems not related to bug 1247843 because that patch was not uplifted to beta.  Ni you just in case you have some idea.

Comment 4

[Kershaw Chang [:kershaw]]

(In reply to Shian-Yow Wu [:swu] from comment #3)
> The issue first happened at 25 Sep 2017.  Kershaw, this seems not related to
> bug 1247843 because that patch was not uplifted to beta.  Ni you just in
> case you have some idea.

Thanks!

This seems to have nothing to do with bug 1247843, but I'll keep this on watchlist.

Comment 5

[Intermittent Failures Robot]

22 failures in 947 pushes (0.023 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* autoland: 8
* mozilla-inbound: 7
* mozilla-central: 4
* mozilla-beta: 3

Platform breakdown:
* osx-10-10: 14
* macosx64-stylo-disabled: 5
* macosx64-nightly: 2
* macosx64-devedition: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1403009&startday=2017-10-09&endday=2017-10-15&tree=all

Comment 6

[Dragana Damjanovic [:dragana]]

Honza, can this be influence with something you landed that delays some requests? I do nod remember when all pieces landed.

Comment 7

[Honza Bambas (:mayhemer)]

(In reply to Dragana Damjanovic [:dragana] from comment #6)
> Honza, can this be influence with something you landed that delays some
> requests? I do nod remember when all pieces landed.

The favicon regression that was fixed with bug 1401538 is on beta (uplift) since 2017-10-12.  So, it was  not the cause since comment 5 shows this test is still failing.

Bug 1358060 has landed on 2017-08-31 on m-c (57 that time).

Bug 1247843 has landed on 2017-09-22.

But this intermittent started and is steadily happening every day since 2017-09-25 on 58 m-c and on 2017-09-29 on 57 m-b, hence it has to be something else.  Note that 2017-09-25 was the 57 m-c -> m-b merge day.



I found following known to me bugs landed during that period that were on the repo at the time the failure was first observed:

https://bugzilla.mozilla.org/show_bug.cgi?id=1360603
https://bugzilla.mozilla.org/show_bug.cgi?id=1400001

Could this be bug 1360603?  Landed on m-c (58) on 2017-09-25 and was uplifted to beta (57) on 2017-09-27.  But it's so negligible change that I doubt that...

Comment 8

[Intermittent Failures Robot]

8 failures in 864 pushes (0.009 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-central: 3
* autoland: 3
* try: 1
* mozilla-inbound: 1

Platform breakdown:
* osx-10-10: 4
* macosx64-stylo-disabled: 2
* windows7-32: 1
* macosx64-nightly: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1403009&startday=2017-10-16&endday=2017-10-22&tree=all

Comment 9

[Arthur Iakab [arthur_iakab]]

In the last 7 days there were 42 failure. Most of the failures occur on Linux but there are also a few occurrences on OS X.
The build type on which the failures mostly occur are opt, pgo and one asan.
Test suite: mochitest-browser-chrome-e10s.

This is an example of a recent log: https://treeherder.mozilla.org/logviewer.html#?repo=mozilla-inbound&job_id=140310315&lineNumber=4345

Here is a part of a log:
[task 2017-10-27T20:51:40.268Z] 20:51:40     INFO - checking window state
4342
[task 2017-10-27T20:51:40.297Z] 20:51:40     INFO - TEST-START | extensions/cookie/test/browser_test_favicon.js
4343
[task 2017-10-27T20:52:25.299Z] 20:52:25     INFO - TEST-INFO | started process screentopng
4344
[task 2017-10-27T20:52:25.928Z] 20:52:25     INFO - TEST-INFO | screentopng: exit 0
4345
[task 2017-10-27T20:52:25.928Z] 20:52:25     INFO - TEST-UNEXPECTED-FAIL | extensions/cookie/test/browser_test_favicon.js | Test timed out - 
4346
[task 2017-10-27T20:52:25.928Z] 20:52:25     INFO - GECKO(4576) | MEMORY STAT | vsize 2330MB | residentFast 235MB | heapAllocated 83MB
4347
[task 2017-10-27T20:52:25.928Z] 20:52:25     INFO - TEST-OK | extensions/cookie/test/browser_test_favicon.js | took 45021ms
4348
[task 2017-10-27T20:52:25.928Z] 20:52:25     INFO - checking window state

:jduell could you please take a look?

Comment 10

[Intermittent Failures Robot]

55 failures in 912 pushes (0.06 failures/push) were associated with this bug in the last 7 days. 

This is the #24 most frequent failure this week.  

** This failure happened more than 30 times this week! Resolving this bug is a high priority. **

** Try to resolve this bug as soon as possible. If unresolved for 2 weeks, the affected test(s) may be disabled. **  

Repository breakdown:
* autoland: 27
* mozilla-inbound: 18
* mozilla-central: 9
* try: 1

Platform breakdown:
* linux64: 24
* linux32: 15
* linux32-stylo-disabled: 6
* linux64-stylo-disabled: 5
* osx-10-10: 3
* macosx64-stylo-disabled: 1
* linux64-nightly: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1403009&startday=2017-10-23&endday=2017-10-29&tree=all

Comment 11

[Jason Duell]

swu: feel free to bounce back to me if you can't find someone.

Comment 12

[Kershaw Chang [:kershaw]]

I'd like to take this, since I might have a solution.

Comment 13

[Kershaw Chang [:kershaw]]

Attachment: Add cleanup function in test

I think this bug might be caused by not doing cleanup before starting loading a favicon. So, I just add a cleanup function in the test case and call it before starting the test.
It looks like the try result [1] agrees with my theory. 

@Marco, could you take a look at this patch? Thanks.




[1] https://treeherder.mozilla.org/#/jobs?repo=try&revision=c6892553491fe287e1a88efad58eb23e218e5d5f&group_state=expanded

Comment 14

[Marco Bonardo [:mak]]

Comment on attachment 8924630 [details] [diff] [review]
Add cleanup function in test

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

::: extensions/cookie/test/browser_test_favicon.js
@@ +32,5 @@
> +  await clearAllPlacesFavicons();
> +  // Clear all image caches and network caches.
> +  clearAllImageCaches();
> +  // Clear Places history.
> +  await PlacesUtils.history.clear();

Off-hand some of these look pointless.
For example setIcon has no relation with Places, so both clearing history and clearing Places icons should have no effect.
The other thing that seems unlikely are the cache and image cache, this image is only loaded by this single test, and we create a new profile per each folder, so why should those matter?

I'd suggest to try just clearing the cookies, would it have an effect?

Another possibility is that the effect of all of these cleanups in in reality is just to space this test from the previous ones, and then it's not really about cleanups, but it's about inter-test interactions...

In a few words, even if this appears to work, we should try to understand why.

Comment 15

[Intermittent Failures Robot]

64 failures in 857 pushes (0.075 failures/push) were associated with this bug in the last 7 days. 

This is the #26 most frequent failure this week.  

** This failure happened more than 30 times this week! Resolving this bug is a high priority. **

** Try to resolve this bug as soon as possible. If unresolved for 2 weeks, the affected test(s) may be disabled. **  

Repository breakdown:
* autoland: 31
* mozilla-inbound: 17
* mozilla-central: 9
* try: 4
* mozilla-beta: 3

Platform breakdown:
* linux64: 24
* linux64-stylo-disabled: 11
* osx-10-10: 8
* linux32-stylo-disabled: 6
* linux32: 6
* macosx64-stylo-disabled: 2
* linux64-devedition: 2
* windows10-64-nightly: 1
* macosx64-nightly: 1
* linux64-nightly: 1
* linux32-nightly: 1
* linux32-devedition: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1403009&startday=2017-10-30&endday=2017-11-05&tree=all

Comment 16

[Kershaw Chang [:kershaw]]

(In reply to Marco Bonardo [::mak] from comment #14)
> Comment on attachment 8924630 [details] [diff] [review]
> Add cleanup function in test
> 
> Review of attachment 8924630 [details] [diff] [review]:
> -----------------------------------------------------------------
> 
> ::: extensions/cookie/test/browser_test_favicon.js
> @@ +32,5 @@
> > +  await clearAllPlacesFavicons();
> > +  // Clear all image caches and network caches.
> > +  clearAllImageCaches();
> > +  // Clear Places history.
> > +  await PlacesUtils.history.clear();
> 
> Off-hand some of these look pointless.
> For example setIcon has no relation with Places, so both clearing history
> and clearing Places icons should have no effect.
> The other thing that seems unlikely are the cache and image cache, this
> image is only loaded by this single test, and we create a new profile per
> each folder, so why should those matter?
> 
> I'd suggest to try just clearing the cookies, would it have an effect?
> 
> Another possibility is that the effect of all of these cleanups in in
> reality is just to space this test from the previous ones, and then it's not
> really about cleanups, but it's about inter-test interactions...
> 
> In a few words, even if this appears to work, we should try to understand
> why.

Thanks for the feedback. I agree with you that we have to figure out the root cause.
After some experiments, it looks like that none of clearing Places icons, cookies, and caches works.

However, I found that the http channel used to load the favicon is not created in the failed test case. Please search the "nsHttpChannel::AsyncOpen" in the passed log [1] and failed log [2] and you can see this.

It looks like this is not a networking issue, since the http channel is not even created.
Tentatively change the component to tabbed browser.


[1] https://public-artifacts.taskcluster.net/XvaFBHF4QsmWNoEPiXjRDA/0/public/logs/live_backing.log
[2] https://public-artifacts.taskcluster.net/FK8TOpJETgaMama2xXhs_A/0/public/logs/live_backing.log

Comment 17

[Marco Bonardo [:mak]]

(In reply to Kershaw Chang [:kershaw] from comment #16)
> Thanks for the feedback. I agree with you that we have to figure out the
> root cause.
> After some experiments, it looks like that none of clearing Places icons,
> cookies, and caches works.

Does this mean the previous green Try build was just by luck?

> However, I found that the http channel used to load the favicon is not
> created in the failed test case. Please search the
> "nsHttpChannel::AsyncOpen" in the passed log [1] and failed log [2] and you
> can see this.

The only thing that setIcon does to start the network load is aTab.setAttribute("image", sizedIconUrl);
I wonder if the problem is that we call gBrowser.setIcon too early. The test harness opens a tab and starts the test, maybe we setIcon and then the default tab setIcon call runs.

I can try doing a simple changes to the test (open a new tab and wait for its load) and see how it reacts.

Comment 18

[Marco Bonardo [:mak]]

let's see.

Comment 19

[Marco Bonardo [:mak]]

ehr, forgot the link https://treeherder.mozilla.org/#/jobs?repo=try&revision=bef977164bc83902395c093a8449181bf58e97bc

Comment 20

[Marco Bonardo [:mak]]

Attachment: Bug 1403009 - Intermittent failure in browser_test_favicon.js.

Review commit: https://reviewboard.mozilla.org/r/196824/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/196824/

Comment 21

[Marco Bonardo [:mak]]

Comment on attachment 8925698 [details]
Bug 1403009 - Intermittent failure in browser_test_favicon.js.

Review request updated; see interdiff: https://reviewboard.mozilla.org/r/196824/diff/1-2/

Comment 22

[Kershaw Chang [:kershaw]]

(In reply to Marco Bonardo [::mak] from comment #17)
> (In reply to Kershaw Chang [:kershaw] from comment #16)
> > Thanks for the feedback. I agree with you that we have to figure out the
> > root cause.
> > After some experiments, it looks like that none of clearing Places icons,
> > cookies, and caches works.
> 
> Does this mean the previous green Try build was just by luck?
> 

Yes, it was just by luck. :(

> > However, I found that the http channel used to load the favicon is not
> > created in the failed test case. Please search the
> > "nsHttpChannel::AsyncOpen" in the passed log [1] and failed log [2] and you
> > can see this.
> 
> The only thing that setIcon does to start the network load is
> aTab.setAttribute("image", sizedIconUrl);
> I wonder if the problem is that we call gBrowser.setIcon too early. The test
> harness opens a tab and starts the test, maybe we setIcon and then the
> default tab setIcon call runs.
> 
> I can try doing a simple changes to the test (open a new tab and wait for
> its load) and see how it reacts.

Unfortunately, I still see a test failure from the link you provided. I see two "SETTING ATTRIBUTE" both in success and failure logs, so the problem must be at somewhere else.

Comment 23

[Marco Bonardo [:mak]]

Even if the attribute is written, in the timeout screenshot the tab has no icon, so I still suspect the 2 set attribute may be happening inverted.
Today I may not have time for further experiments, I'll look in the next days, in the worst case we could take the patch as a first step to reduce the number of failures but leave the bug open.

Comment 24

[Kershaw Chang [:kershaw]]

(In reply to Marco Bonardo [::mak] from comment #23)
> Even if the attribute is written, in the timeout screenshot the tab has no
> icon, so I still suspect the 2 set attribute may be happening inverted.

FWIW, the test is finished before the loading of favicon completed. So, it is normal without seeing the icon in the screenshot.

> Today I may not have time for further experiments, I'll look in the next
> days, in the worst case we could take the patch as a first step to reduce
> the number of failures but leave the bug open.

It seems that your change reduces the failure rate significantly. Besides the one time failure mentioned in comment 22, I can't reproduce this anymore on try server.

https://treeherder.mozilla.org/#/jobs?repo=try&revision=37e1ca3146ca362fe33dad294da75b9b91a75bc4&group_state=expanded

Comment 25

[Kershaw Chang [:kershaw]]

Comment on attachment 8925698 [details]
Bug 1403009 - Intermittent failure in browser_test_favicon.js.

https://reviewboard.mozilla.org/r/196824/#review202780

r+ for reducing the failure rate.

Comment 26

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/9d06816dccb8
Intermittent failure in browser_test_favicon.js. r=kershaw

Comment 27

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

https://hg.mozilla.org/mozilla-central/rev/9d06816dccb8

Comment 28

[Intermittent Failures Robot]

49 failures in 849 pushes (0.058 failures/push) were associated with this bug in the last 7 days. 

This is the #38 most frequent failure this week.  

** This failure happened more than 30 times this week! Resolving this bug is a high priority. **

** Try to resolve this bug as soon as possible. If unresolved for 2 weeks, the affected test(s) may be disabled. **  

Repository breakdown:
* mozilla-inbound: 18
* autoland: 18
* mozilla-central: 11
* mozilla-beta: 2

Platform breakdown:
* linux64: 22
* linux64-stylo-disabled: 8
* osx-10-10: 4
* macosx64-stylo-disabled: 4
* linux32-stylo-disabled: 3
* windows10-64: 2
* linux32: 2
* windows10-64-stylo-disabled: 1
* windows10-64-nightly: 1
* linux64-nightly: 1
* android-4-2-armv7-api16: 1

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

Comment 29

[Marco Bonardo [:mak]]

looking at the orange factor, the number of failures largely reduced on 9th of November, so the partial fix helped. The report in comment 28 is mostly for the previous period.
That said, the bug still hits us, but I'm lacking ideas atm.
I'm unassigning to indicate that I'm not immediately working on it, so that anyone with an idea could chime in.

Comment 30

[Intermittent Failures Robot]

3 failures in 744 pushes (0.004 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* try: 1
* mozilla-central: 1
* autoland: 1

Platform breakdown:
* linux64-stylo-disabled: 1
* linux64: 1
* linux32-nightly: 1

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

Comment 31

[Intermittent Failures Robot]

8 failures in 792 pushes (0.01 failures/push) were associated with this bug in the last 7 days.    

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

Platform breakdown:
* linux32-stylo-disabled: 4
* linux32: 2
* osx-10-10: 1
* linux64-stylo-disabled: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1403009&startday=2017-11-27&endday=2017-12-03&tree=all

Comment 32

[Intermittent Failures Robot]

3 failures in 889 pushes (0.003 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-central: 2
* autoland: 1

Platform breakdown:
* linux64-ccov: 1
* linux32-nightly: 1
* linux32: 1

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

Comment 33

[Intermittent Failures Robot]

1 failures in 423 pushes (0.002 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-central: 1

Platform breakdown:
* linux64-ccov: 1

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

Comment 34

[Intermittent Failures Robot]

1 failures in 590 pushes (0.002 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* autoland: 1

Platform breakdown:
* linux32-stylo-disabled: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1403009&startday=2017-12-18&endday=2017-12-24&tree=all

Comment 35

[Intermittent Failures Robot]

4 failures in 462 pushes (0.009 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-central: 2
* mozilla-inbound: 1
* autoland: 1

Platform breakdown:
* linux32-stylo-disabled: 2
* linux32-nightly: 1
* linux32: 1

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

Comment 36

[Intermittent Failures Robot]

5 failures in 788 pushes (0.006 failures/push) were associated with this bug in the last 7 days.    

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

Platform breakdown:
* linux32: 3
* linux32-stylo-disabled: 2

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1403009&startday=2018-01-08&endday=2018-01-14&tree=all

Comment 37

[Intermittent Failures Robot]

1 failures in 657 pushes (0.002 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-inbound: 1

Platform breakdown:
* osx-10-10: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1403009&startday=2018-01-15&endday=2018-01-21&tree=all

Comment 38

[Intermittent Failures Robot]

3 failures in 701 pushes (0.004 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* try: 1
* mozilla-inbound: 1
* mozilla-central: 1

Platform breakdown:
* linux64-stylo-disabled: 1
* linux32-stylo-disabled: 1
* linux32-nightly: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1403009&startday=2018-01-22&endday=2018-01-28&tree=all

Comment 39

[Intermittent Failures Robot]

1 failures in 735 pushes (0.001 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-central: 1

Platform breakdown:
* linux32-nightly: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1403009&startday=2018-01-29&endday=2018-02-04&tree=all

Comment 40

[Intermittent Failures Robot]

2 failures in 702 pushes (0.003 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* try: 1
* mozilla-central: 1

Platform breakdown:
* windows10-64: 1
* osx-10-10: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1403009&startday=2018-02-05&endday=2018-02-11&tree=all

Comment 41

[Intermittent Failures Robot]

2 failures in 685 pushes (0.003 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* try: 1
* mozilla-inbound: 1

Platform breakdown:
* linux64-stylo-disabled: 1
* linux64: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1403009&startday=2018-02-12&endday=2018-02-18&tree=all

Comment 42

[Intermittent Failures Robot]

4 failures in 675 pushes (0.006 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* autoland: 4

Platform breakdown:
* osx-10-10: 3
* linux32-stylo-disabled: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1403009&startday=2018-02-19&endday=2018-02-25&tree=all

Comment 43

[Intermittent Failures Robot]

7 failures in 831 pushes (0.008 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-inbound: 3
* autoland: 3
* mozilla-beta: 1

Platform breakdown:
* osx-10-10: 5
* linux64-stylo-disabled: 1
* linux64: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1403009&startday=2018-02-26&endday=2018-03-04&tree=all

Comment 44

[Intermittent Failures Robot]

5 failures in 747 pushes (0.007 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-inbound: 2
* try: 1
* mozilla-central: 1
* autoland: 1

Platform breakdown:
* osx-10-10: 3
* linux64-stylo-disabled: 1
* linux32: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1403009&startday=2018-03-05&endday=2018-03-11&tree=all

Comment 45

[Intermittent Failures Robot]

6 failures in 814 pushes (0.007 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-inbound: 2
* mozilla-central: 2
* autoland: 2

Platform breakdown:
* osx-10-10: 3
* linux32-nightly: 2
* linux64-stylo-disabled: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1403009&startday=2018-03-12&endday=2018-03-18&tree=all

Comment 46

[Intermittent Failures Robot]

9 failures in 822 pushes (0.011 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-central: 4
* autoland: 3
* mozilla-inbound: 2

Platform breakdown:
* osx-10-10: 6
* windows10-64-ccov: 2
* linux32: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-03-20&endday=2018-03-26&tree=trunk

Comment 47

[Intermittent Failures Robot]

5 failures in 718 pushes (0.007 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-inbound: 3
* mozilla-central: 2

Platform breakdown:
* osx-10-10: 3
* windows10-64-ccov: 1
* linux32: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-03-26&endday=2018-04-01&tree=trunk

Comment 48

[Intermittent Failures Robot]

3 failures in 765 pushes (0.004 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* autoland: 2
* mozilla-central: 1

Platform breakdown:
* linux32: 2
* windows10-64-ccov: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-04-02&endday=2018-04-08&tree=trunk

Comment 49

[Intermittent Failures Robot]

15 failures in 792 pushes (0.019 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-inbound: 5
* mozilla-central: 4
* try: 3
* autoland: 3

Platform breakdown:
* linux32: 5
* osx-10-10: 4
* windows10-64-ccov: 2
* linux64: 2
* windows7-32: 1
* linux32-nightly: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-04-09&endday=2018-04-15&tree=trunk

Comment 50

[Intermittent Failures Robot]

1 failures in 782 pushes (0.001 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-inbound: 1

Platform breakdown:
* linux32: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-04-16&endday=2018-04-22&tree=trunk

Comment 51

[Intermittent Failures Robot]

3 failures in 780 pushes (0.004 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-central: 2
* mozilla-inbound: 1

Platform breakdown:
* linux32-nightly: 2
* osx-10-10: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-04-23&endday=2018-04-29&tree=trunk

Comment 52

[Intermittent Failures Robot]

9 failures in 551 pushes (0.016 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* autoland: 6
* mozilla-inbound: 3

Platform breakdown:
* osx-10-10: 9

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-04-30&endday=2018-05-06&tree=trunk

Comment 53

[Intermittent Failures Robot]

2 failures in 639 pushes (0.003 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* try: 1
* autoland: 1

Platform breakdown:
* windows10-64-ccov: 1
* osx-10-10: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-05-14&endday=2018-05-20&tree=trunk

Comment 54

[Intermittent Failures Robot]

12 failures in 655 pushes (0.018 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* autoland: 7
* mozilla-inbound: 4
* try: 1

Platform breakdown:
* windows7-32: 7
* osx-10-10: 3
* windows10-64: 2

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-05-28&endday=2018-06-03&tree=trunk

Comment 55

[Intermittent Failures Robot]

35 failures in 669 pushes (0.052 failures/push) were associated with this bug in the last 7 days. 

This is the #37 most frequent failure this week.  

** This failure happened more than 30 times this week! Resolving this bug is a high priority. **

** Try to resolve this bug as soon as possible. If unresolved for 2 weeks, the affected test(s) may be disabled. **  

Repository breakdown:
* mozilla-inbound: 11
* try: 9
* autoland: 9
* mozilla-central: 5
* mozilla-beta: 1

Platform breakdown:
* windows7-32: 17
* windows10-64: 15
* osx-10-10: 2
* linux64: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-06-04&endday=2018-06-10&tree=trunk

Comment 56

[Narcis Beleuzu [:NarcisB]]

There are 27 failures in the last 7 days.
All of them are on Windows - debug:
- windows7-32 -> 11 failures 
- windows10-64 -> 16 failures

Recent failure: https://treeherder.mozilla.org/logviewer.html#?job_id=183062259&repo=autoland&lineNumber=20311

18:44:35     INFO -  852 INFO TEST-START | extensions/cookie/test/browser_test_favicon.js
18:44:35     INFO -  GECKO(5764) | Chrome file doesn't exist: Z:\task_1528912501\build\tests\mochitest\browser\extensions\cookie\test\head.js
18:44:35     INFO -  GECKO(5764) | ++DOCSHELL 09947800 == 3 [pid = 5924] [id = {0ba73d1c-2a4a-496b-98b0-999ecbaac6d4}]
18:44:35     INFO -  GECKO(5764) | ++DOMWINDOW == 6 (059A77A0) [pid = 5924] [serial = 6] [outer = 00000000]
18:44:35     INFO -  GECKO(5764) | ++DOMWINDOW == 7 (09949000) [pid = 5924] [serial = 7] [outer = 059A77A0]
18:44:35     INFO -  GECKO(5764) | [Child 5924, Main Thread] WARNING: site security information will not be persisted: file z:/build/build/src/security/manager/ssl/nsSiteSecurityService.cpp, line 553
18:44:35     INFO -  GECKO(5764) | [Child 3996, Main Thread] WARNING: NS_ENSURE_SUCCESS(rv, rv) failed with result 0x80004005: file z:/build/build/src/xpcom/base/nsSystemInfo.cpp, line 119
18:44:35     INFO -  GECKO(5764) | ++DOCSHELL 05523800 == 1 [pid = 3996] [id = {3207a8cd-7600-409b-9720-280c08252dc9}]
18:44:35     INFO -  GECKO(5764) | [Child 3996, Main Thread] WARNING: 'NS_FAILED(rv)', file z:/build/build/src/widget/windows/nsLookAndFeel.cpp, line 847
18:44:35     INFO -  GECKO(5764) | ++DOMWINDOW == 1 (055BF2E0) [pid = 3996] [serial = 1] [outer = 00000000]
18:44:35     INFO -  GECKO(5764) | ++DOMWINDOW == 8 (0994BC00) [pid = 5924] [serial = 8] [outer = 059A77A0]
18:44:35     INFO -  GECKO(5764) | ++DOMWINDOW == 2 (0A2E8800) [pid = 3996] [serial = 2] [outer = 055BF2E0]
18:44:35     INFO -  GECKO(5764) | [Child 3996, Main Thread] WARNING: 'NS_FAILED(GetAccentColor(unused))', file z:/build/build/src/widget/windows/nsLookAndFeel.cpp, line 473
18:44:35     INFO -  GECKO(5764) | [Parent 5764, Main Thread] WARNING: NS_ENSURE_TRUE(aSecondURI) failed: file z:/build/build/src/dom/base/ThirdPartyUtil.cpp, line 98
18:44:39     INFO -  GECKO(5764) | --DOCSHELL 16402C00 == 6 [pid = 5764] [id = {d5ee518e-37df-4e83-ac3c-e31a52a3e38c}]
18:44:39     INFO -  GECKO(5764) | --DOCSHELL 1B135000 == 5 [pid = 5764] [id = {1e9529aa-87ed-49b1-9f0c-64ee237c571c}]
18:44:40     INFO -  GECKO(5764) | --DOCSHELL 05D0F400 == 1 [pid = 5752] [id = {d471b857-a37c-4ca7-ad96-f8a5d40ea793}]
18:44:41     INFO -  GECKO(5764) | --DOCSHELL 0590F400 == 2 [pid = 5924] [id = {740c7727-b498-4f5f-8c3b-fa253697daee}]
18:44:41     INFO -  GECKO(5764) | --DOCSHELL 09944400 == 1 [pid = 5924] [id = {d7366732-6acc-45ec-8b70-bef2730ad2fc}]
18:44:44     INFO -  GECKO(5764) | --DOMWINDOW == 6 (15716C00) [pid = 5752] [serial = 6] [outer = 00000000] [url = about:blank]
18:44:44     INFO -  GECKO(5764) | --DOMWINDOW == 5 (05D10C00) [pid = 5752] [serial = 2] [outer = 00000000] [url = about:blank]
18:44:46     INFO -  GECKO(5764) | --DOMWINDOW == 7 (05910C00) [pid = 5924] [serial = 2] [outer = 00000000] [url = about:blank]
18:44:46     INFO -  GECKO(5764) | --DOMWINDOW == 6 (09949000) [pid = 5924] [serial = 7] [outer = 00000000] [url = about:blank]
18:44:46     INFO -  GECKO(5764) | --DOMWINDOW == 16 (1640F400) [pid = 5764] [serial = 4] [outer = 00000000] [url = about:blank]
18:44:46     INFO -  GECKO(5764) | --DOMWINDOW == 15 (1F705000) [pid = 5764] [serial = 13] [outer = 00000000] [url = about:blank]
18:44:46     INFO -  GECKO(5764) | --DOMWINDOW == 14 (1F706800) [pid = 5764] [serial = 14] [outer = 00000000] [url = about:blank]
18:44:46     INFO -  GECKO(5764) | --DOMWINDOW == 13 (0ADEAFF0) [pid = 5764] [serial = 9] [outer = 00000000] [url = about:blank]
18:44:47     INFO -  GECKO(5764) | --DOMWINDOW == 2 (05720C00) [pid = 6112] [serial = 2] [outer = 00000000] [url = about:blank]
18:44:48     INFO -  GECKO(5764) | --DOMWINDOW == 4 (05D992E0) [pid = 5752] [serial = 1] [outer = 00000000] [url = about:blank]
18:44:49     INFO -  GECKO(5764) | --DOMWINDOW == 5 (059A7670) [pid = 5924] [serial = 4] [outer = 00000000] [url = about:blank]
18:44:49     INFO -  GECKO(5764) | --DOMWINDOW == 4 (059A72E0) [pid = 5924] [serial = 1] [outer = 00000000] [url = chrome://gfxsanity/content/sanitytest.html]
18:44:50     INFO -  GECKO(5764) | --DOMWINDOW == 2 (05BD3400) [pid = 5660] [serial = 2] [outer = 00000000] [url = about:blank]
18:44:50     INFO -  GECKO(5764) | --DOMWINDOW == 1 (057B92E0) [pid = 6112] [serial = 1] [outer = 00000000] [url = view-source:http://example.com/]
18:44:50     INFO -  GECKO(5764) | --DOMWINDOW == 12 (1C8E4000) [pid = 5764] [serial = 10] [outer = 00000000] [url = about:blank]
18:44:51     INFO -  GECKO(5764) | --DOMWINDOW == 3 (0999B400) [pid = 5924] [serial = 3] [outer = 00000000] [url = chrome://gfxsanity/content/sanitytest.html]
18:44:51     INFO -  GECKO(5764) | --DOMWINDOW == 2 (09946C00) [pid = 5924] [serial = 5] [outer = 00000000] [url = about:blank]
18:44:52     INFO -  GECKO(5764) | --DOMWINDOW == 3 (138AAC00) [pid = 5752] [serial = 4] [outer = 00000000] [url = about:blank]
18:44:52     INFO -  GECKO(5764) | --DOMWINDOW == 2 (05D0F800) [pid = 5752] [serial = 3] [outer = 00000000] [url = about:blank]
18:44:54     INFO -  GECKO(5764) | [Parent 5764, StreamTrans #17] WARNING: 'NS_FAILED(rv)', file z:/build/build/src/modules/libjar/nsJARChannel.cpp, line 417
18:44:54     INFO -  GECKO(5764) | --DOMWINDOW == 0 (0A6F2800) [pid = 6112] [serial = 3] [outer = 00000000] [url = view-source:http://example.com/]
18:44:58     INFO -  GECKO(5764) | --DOCSHELL 0571E000 == 0 [pid = 6112] [id = {5e5cf990-f94e-4e5a-b2d9-d8eb612fbd64}]
18:46:05     INFO -  TEST-INFO | started process screenshot
18:46:05     INFO -  TEST-INFO | screenshot: exit 0
18:46:05     INFO -  Buffered messages logged at 18:44:35
18:46:05     INFO -  853 INFO Entering test bound
18:46:05     INFO -  854 INFO Console message: [JavaScript Warning: "Use of nsIFile in content process is deprecated." {file: "resource://gre/modules/FileUtils.jsm" line: 170}]
18:46:05     INFO -  Buffered messages finished
18:46:05    ERROR -  855 INFO TEST-UNEXPECTED-FAIL | extensions/cookie/test/browser_test_favicon.js | Test timed out -
18:46:05     INFO -  GECKO(5764) | MEMORY STAT | vsize 714MB | vsizeMaxContiguous 752MB | residentFast 203MB | heapAllocated 72MB
18:46:05     INFO -  856 INFO TEST-OK | extensions/cookie/test/browser_test_favicon.js | took 90114ms

:mak, can you take a look?

Comment 57

[Marco Bonardo [:mak]]

I don't have a clear idea about this failure, and previous investigation didn't show anything obvious.

The only thing we may look into is the failure increase range, it looks like it increased between 31st of May and the 2nd of June, I'll check what landed in that timeframe.

We could also just disable this test on Windows-debug to lower the failures frequency.

Adding Kershaw who also did some network investigation here, in case he has further ideas to evaluate.

Comment 58

[Intermittent Failures Robot]

22 failures in 408 pushes (0.054 failures/push) were associated with this bug in the last 7 days. 

This is the #28 most frequent failure this week.   

Repository breakdown:
* autoland: 14
* mozilla-inbound: 6
* try: 1
* mozilla-central: 1

Platform breakdown:
* windows10-64: 19
* windows7-32: 3

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-06-11&endday=2018-06-17&tree=trunk

Comment 59

[Intermittent Failures Robot]

22 failures in 521 pushes (0.042 failures/push) were associated with this bug in the last 7 days. 

This is the #41 most frequent failure this week.   

Repository breakdown:
* mozilla-inbound: 7
* try: 5
* mozilla-central: 5
* mozilla-beta: 3
* autoland: 2

Platform breakdown:
* windows7-32: 16
* windows10-64: 5
* osx-10-10: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-06-18&endday=2018-06-24&tree=trunk

Comment 60

[Tiberius Oros[:tiberius_oros]]

Update:
In the last 7 days, there have been 33 failures.
All of them occur on the debug build type and on the following platforms:
- windows7-32 - 19
- windows10-64 - 12
- osx-10-10 - 2

Here is a recent relevant log file and a snippet with the failure:
https://treeherder.mozilla.org/logviewer.html#?job_id=185176768&repo=mozilla-inbound&lineNumber=25884

14:54:01     INFO -  TEST-INFO | started process screenshot
14:54:01     INFO -  TEST-INFO | screenshot: exit 0
14:54:01     INFO -  Buffered messages logged at 14:52:31
14:54:01     INFO -  692 INFO Entering test bound
14:54:01     INFO -  Buffered messages logged at 14:52:32
14:54:01     INFO -  693 INFO Console message: [JavaScript Warning: "Use of nsIFile in content process is deprecated." {file: "resource://gre/modules/FileUtils.jsm" line: 170}]
14:54:01     INFO -  Buffered messages finished
14:54:01    ERROR -  694 INFO TEST-UNEXPECTED-FAIL | extensions/cookie/test/browser_test_favicon.js | Test timed out -
14:54:01     INFO -  GECKO(5720) | MEMORY STAT | vsize 729MB | vsizeMaxContiguous 512MB | residentFast 203MB | heapAllocated 72MB
14:54:01     INFO -  695 INFO TEST-OK | extensions/cookie/test/browser_test_favicon.js | took 90116ms
14:54:01     INFO -  GECKO(5720) | ++DOCSHELL 05A0C000 == 2 [pid = 3996] [id = {44ea01d0-569d-4e49-bc45-161a5f751365}]
14:54:01     INFO -  GECKO(5720) | ++DOMWINDOW == 3 (013CF410) [pid = 3996] [serial = 9] [outer = 00000000]
14:54:01     INFO -  GECKO(5720) | ++DOMWINDOW == 4 (0A535000) [pid = 3996] [serial = 10] [outer = 013CF410]
14:54:01     INFO -  696 INFO checking window state

Comment 61

[Intermittent Failures Robot]

29 failures in 718 pushes (0.04 failures/push) were associated with this bug in the last 7 days. 

This is the #40 most frequent failure this week.   

Repository breakdown:
* autoland: 15
* mozilla-inbound: 12
* try: 1
* mozilla-central: 1

Platform breakdown:
* windows10-64: 15
* windows7-32: 13
* osx-10-10: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-06-25&endday=2018-07-01&tree=trunk

Comment 62

[Intermittent Failures Robot]

6 failures in 622 pushes (0.01 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-beta: 6

Platform breakdown:
* windows7-32: 3
* windows10-64: 3

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-07-02&endday=2018-07-08&tree=trunk

Comment 63

[Intermittent Failures Robot]

4 failures in 623 pushes (0.006 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-release: 2
* mozilla-beta: 2

Platform breakdown:
* osx-10-10: 4

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-07-09&endday=2018-07-15&tree=trunk

Comment 64

[Intermittent Failures Robot]

2 failures in 653 pushes (0.003 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-beta: 2

Platform breakdown:
* windows7-32: 2

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-07-16&endday=2018-07-22&tree=trunk

Comment 65

[Intermittent Failures Robot]

2 failures in 760 pushes (0.003 failures/push) were associated with this bug in the last 7 days.    

Repository breakdown:
* mozilla-beta: 2

Platform breakdown:
* windows7-32: 1
* windows10-64: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-07-23&endday=2018-07-29&tree=trunk

Comment 66

[Intermittent Failures Robot]

1 failures in 2561 pushes (0.0 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-beta: 1

Platform breakdown:
* windows7-32: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-08-05&endday=2018-08-11&tree=all

Comment 67

[Intermittent Failures Robot]

1 failures in 2579 pushes (0.0 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-beta: 1

Platform breakdown:
* windows7-32: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-08-06&endday=2018-08-12&tree=all

Comment 68

[Intermittent Failures Robot]

4 failures in 2672 pushes (0.001 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-beta: 4

Platform breakdown:
* windows10-64: 4

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-08-13&endday=2018-08-19&tree=all

Comment 69

[Intermittent Failures Robot]

3 failures in 2568 pushes (0.001 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-beta: 2
* mozilla-release: 1

Platform breakdown:
* windows10-64: 2
* windows7-32: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-08-20&endday=2018-08-26&tree=all

Comment 70

[Intermittent Failures Robot]

1 failures in 2545 pushes (0.0 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-release: 1

Platform breakdown:
* windows7-32: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-08-27&endday=2018-09-02&tree=all

Comment 71

[Intermittent Failures Robot]

1 failures in 2667 pushes (0.0 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-release: 1

Platform breakdown:
* windows10-64: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-09-03&endday=2018-09-09&tree=all

Comment 72

[Intermittent Failures Robot]

1 failures in 2684 pushes (0.0 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-release: 1

Platform breakdown:
* windows10-64: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-09-10&endday=2018-09-16&tree=all

Comment 73

[Kershaw Chang [:kershaw]]

(In reply to Marco Bonardo [::mak] from comment #57)
> I don't have a clear idea about this failure, and previous investigation
> didn't show anything obvious.
> 
> The only thing we may look into is the failure increase range, it looks like
> it increased between 31st of May and the 2nd of June, I'll check what landed
> in that timeframe.
> 
> We could also just disable this test on Windows-debug to lower the failures
> frequency.
> 
> Adding Kershaw who also did some network investigation here, in case he has
> further ideas to evaluate.

Sorry that I don't have any idea now.

It seems that the failure rate is pretty low recently. I'll look into this when this is more reproducible.

Comment 74

[Intermittent Failures Robot]

1 failures in 2902 pushes (0.0 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-release: 1

Platform breakdown:
* windows10-64: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-09-17&endday=2018-09-23&tree=all

Comment 75

[Intermittent Failures Robot]

33 failures in 520 pushes (0.063 failures/push) were associated with this bug yesterday.

Repository breakdown:
* try: 33

Platform breakdown:
* linux32-nightly: 2
* windows7-32-devedition: 2
* linux64: 6
* linux64-devedition: 2
* windows7-32: 2
* linux64-nightly: 2
* macosx64-devedition: 2
* windows10-64-devedition: 1
* linux32-devedition: 1
* macosx64-nightly: 2
* windows10-64-nightly: 2
* osx-10-10: 4
* linux32: 3
* windows10-64: 2

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-09-26&endday=2018-09-26&tree=all

Comment 76

[Intermittent Failures Robot]

59 failures in 522 pushes (0.113 failures/push) were associated with this bug yesterday.

Repository breakdown:
* mozilla-beta: 21
* try: 38

Platform breakdown:
* osx-10-10: 5
* windows7-32-nightly: 1
* macosx64-devedition: 3
* linux32-devedition: 5
* linux32-nightly: 3
* macosx64-nightly: 3
* windows7-32: 2
* linux32: 6
* windows10-64: 3
* linux64-nightly: 4
* windows10-64-devedition: 3
* windows10-64-nightly: 3
* windows7-32-devedition: 6
* linux64: 8
* linux64-devedition: 4

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-09-27&endday=2018-09-27&tree=all

Comment 77

[Intermittent Failures Robot]

25 failures in 490 pushes (0.051 failures/push) were associated with this bug yesterday.

Repository breakdown:
* try: 25

Platform breakdown:
* linux64: 3
* macosx64-devedition: 2
* windows10-64-nightly: 2
* osx-10-10: 4
* windows10-64: 6
* windows7-32-nightly: 2
* macosx64-nightly: 2
* linux32: 2
* windows7-32: 2

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-09-28&endday=2018-09-28&tree=all

Comment 78

[Intermittent Failures Robot]

118 failures in 2773 pushes (0.043 failures/push) were associated with this bug in the last 7 days.

This is the #9 most frequent failure this week.

** This failure happened more than 75 times this week! Resolving this bug is a very high priority. ** 

** Try to resolve this bug as soon as possible. If unresolved for 1 week, the affected test(s) may be disabled. ** 

Repository breakdown:
* try: 97
* mozilla-beta: 21

Platform breakdown:
* windows10-64-nightly: 7
* linux32: 11
* macosx64-nightly: 7
* windows10-64-devedition: 4
* windows7-32-devedition: 8
* windows7-32: 6
* linux32-devedition: 6
* linux32-nightly: 5
* osx-10-10: 13
* linux64-nightly: 6
* windows7-32-nightly: 3
* macosx64-devedition: 7
* linux64: 18
* windows10-64: 11
* linux64-devedition: 6

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-09-24&endday=2018-09-30&tree=all

Comment 79

[Intermittent Failures Robot]

1 failures in 2708 pushes (0.0 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-release: 1

Platform breakdown:
* windows10-64: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-10-01&endday=2018-10-07&tree=all

Comment 80

[Intermittent Failures Robot]

1 failures in 3007 pushes (0.0 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-esr60: 1

Platform breakdown:
* osx-10-10: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2018-11-05&endday=2018-11-11&tree=all

Comment 81

[Intermittent Failures Robot]

1 failures in 2832 pushes (0.0 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• mozilla-esr60: 1

Platform breakdown:

• osx-10-10: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2019-02-11&endday=2019-02-17&tree=all

Comment 82

[Intermittent Failures Robot]

8 failures in 4131 pushes (0.002 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• autoland: 4
• mozilla-inbound: 4

Platform breakdown:

• windows10-64: 2
• windows7-32: 2
• windows10-64-shippable: 2
• windows7-32-shippable: 1
• android-hw-p2-8-0-android-aarch64: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2019-04-29&endday=2019-05-05&tree=all

Comment 84

[Intermittent Failures Robot]

2 failures in 5073 pushes (0.0 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• mozilla-esr60: 2

Platform breakdown:

• linux64: 2

For more details, see:
https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?bug=1403009&startday=2019-08-19&endday=2019-08-25&tree=all

Comment 85

[BugBot [:suhaib / :marco/ :calixte]]

https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
For more information, please visit BugBot documentation.

Comment 86

[BugBot (nomail) [:suhaib / :marco/ :calixte]]

Since the bug is closed, the stalled keyword is now meaningless.
For more information, please visit BugBot documentation.