Intermittent browser_rules_edit-property-increments.js | This test exceeded the timeout threshold. It should be rewritten or split up.

RESOLVED FIXED in Firefox 52

Status

()

Firefox
Developer Tools: CSS Rules Inspector
P1
normal
RESOLVED FIXED
2 years ago
a year ago

People

(Reporter: philor, Assigned: ochameau)

Tracking

({intermittent-failure})

unspecified
Firefox 53
intermittent-failure
Points:
---
Bug Flags:
in-testsuite -

Firefox Tracking Flags

(firefox51 unaffected, firefox52 fixed, firefox53 fixed)

Details

MozReview Requests

()

Submitter Diff Changes Open Issues Last Updated
Loading...
Error loading review requests:

Attachments

(1 attachment)

(Reporter)

Description

2 years ago
https://treeherder.mozilla.org/logviewer.html#?job_id=28512518&repo=mozilla-inbound
Inspector bug triage (filter on CLIMBING SHOES)
Priority: -- → P3

Comment 2

a year ago
20 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-inbound: 8
* autoland: 7
* fx-team: 3
* mozilla-central: 2

Platform breakdown:
* linux32: 20

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1275446&startday=2016-09-12&endday=2016-09-18&tree=all
Inspector bug triage (filter on CLIMBING SHOES).
Priority: P3 → P2

Comment 4

a year ago
7 automation job failures were associated with this bug in the last 7 days.

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

Platform breakdown:
* linux32: 6
* linux64: 1

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

Comment 5

a year ago
6 automation job failures were associated with this bug in the last 7 days.

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

Platform breakdown:
* linux32: 5
* linux64: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1275446&startday=2016-09-26&endday=2016-10-02&tree=all

Comment 6

a year ago
8 automation job failures were associated with this bug in the last 7 days.

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

Platform breakdown:
* linux32: 8

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

Comment 7

a year ago
10 automation job failures were associated with this bug in the last 7 days.

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

Platform breakdown:
* linux32: 10

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

Comment 8

a year ago
6 automation job failures were associated with this bug in the last 7 days.

Repository breakdown:
* mozilla-inbound: 3
* autoland: 2
* fx-team: 1

Platform breakdown:
* linux32: 5
* linux64: 1

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

Comment 9

a year ago
6 automation job failures were associated with this bug in the last 7 days.

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

Platform breakdown:
* linux32: 6

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1275446&startday=2016-10-31&endday=2016-11-06&tree=all
8 automation job failures were associated with this bug in the last 7 days.

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

Platform breakdown:
* linux32: 8

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1275446&startday=2016-11-07&endday=2016-11-13&tree=all
36 failures in 124 pushes (0.29 failures/push) were associated with this bug yesterday.  

Repository breakdown:
* autoland: 36

Platform breakdown:
* linux32: 36

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1275446&startday=2016-11-14&endday=2016-11-14&tree=all
19 failures in 113 pushes (0.168 failures/push) were associated with this bug yesterday.  

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

Platform breakdown:
* linux32: 18
* windows7-32-vm: 1

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1275446&startday=2016-11-18&endday=2016-11-18&tree=all
100 failures in 715 pushes (0.14 failures/push) were associated with this bug in the last 7 days. 

This is the #13 most frequent failure this week. 

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

Repository breakdown:
* autoland: 54
* mozilla-inbound: 23
* try: 10
* mozilla-aurora: 10
* mozilla-central: 3

Platform breakdown:
* linux32: 97
* windows7-32-vm: 3

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1275446&startday=2016-11-14&endday=2016-11-20&tree=all
:pbro, this bug really spiked on November 14th (maybe the 13th based on how you read the data and comment dates)- can you take a look at this? It is one of the top issues remaining on the trees.

this is 97% on linux32 (the win7 stuff could be mis filed) and it is a timeout- I am not sure if we get a lot of value out of devtools on linux32, so possibly a disabling is easier than a longer investigation.
Flags: needinfo?(pbrosset)
26 failures in 113 pushes (0.23 failures/push) were associated with this bug yesterday.  

Repository breakdown:
* mozilla-inbound: 8
* autoland: 8
* mozilla-aurora: 5
* mozilla-central: 3
* try: 2

Platform breakdown:
* linux32: 26

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1275446&startday=2016-11-21&endday=2016-11-21&tree=all
(In reply to Joel Maher ( :jmaher) from comment #14)
> :pbro, this bug really spiked on November 14th (maybe the 13th based on how
> you read the data and comment dates)- can you take a look at this? It is one
> of the top issues remaining on the trees.
> 
> this is 97% on linux32 (the win7 stuff could be mis filed) and it is a
> timeout- I am not sure if we get a lot of value out of devtools on linux32,
> so possibly a disabling is easier than a longer investigation.
Thanks Joel. This one is another case of a test that passes but started to take a few more seconds than the allowed threshold recently, for some obscure reasons.
You're right that we could disable it (or maybe just increase the timeout), but looking at the test, it seems to be one that can be very easily split up in several parts. It seems to be really long and composed of fairly independent parts. So I'd like us to do this instead. If after this, some parts keep on running for too long, we can then start disabling on linux debug 32 as suggested.

Alex: do you have some time to look into this simple test splitting bug? r=test-only would be fine for something like this.
Flags: needinfo?(pbrosset) → needinfo?(poirot.alex)
Priority: P2 → P1
18 failures in 124 pushes (0.145 failures/push) were associated with this bug yesterday.  

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

Platform breakdown:
* linux32: 16
* windows7-32-vm: 2

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1275446&startday=2016-11-23&endday=2016-11-23&tree=all
(Assignee)

Comment 18

a year ago
Do we ever had a linux32-only bug to fix? Or may be it helped us fix some real world races?
If not, is there value in running linux32 devtools at all?
This test is all about increments, if we split it, it would be quite arbitrary of split in many this time very small piece. I would be more in favor of incresing the timeout while looking at possible performance tweaks.

What is this timeout? 30s? It runs in 10s locally.

Also, the rule view throws some errors to the console.
This is related to: (from bug 1069829):
https://hg.mozilla.org/mozilla-central/rev/99fbe8621fa7
I imagine it can slow the test down. This test runs 20-30% faster by reverting that.
But that's not what recently regressed as it landed long time ago.
Comment hidden (mozreview-request)
(Assignee)

Comment 20

a year ago
https://hg.mozilla.org/integration/mozilla-inbound/rev/b2a7cf1f8f467495d0a3d1f06935ee76d147b466
Bug 1275446 - Bump timeout threshold for browser_rules_edit-property-increments.js on linux32. r=test-only
(In reply to Alexandre Poirot [:ochameau] from comment #18)
> 
> What is this timeout? 30s? It runs in 10s locally.

The timeout is 45 seconds (http://searchfox.org/mozilla-central/rev/b4e6fa3527436bdbcd9dd2e1982382fe423431f3/testing/mochitest/browser-test.js#3)
Assignee: nobody → poirot.alex
Status: NEW → ASSIGNED

Comment 22

a year ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/b2a7cf1f8f46
Status: ASSIGNED → RESOLVED
Last Resolved: a year ago
status-firefox53: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 53
94 failures in 623 pushes (0.151 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 50 times this week! Resolving this bug is a high priority. **

Repository breakdown:
* autoland: 31
* mozilla-inbound: 26
* mozilla-aurora: 22
* mozilla-central: 10
* try: 5

Platform breakdown:
* linux32: 90
* windows7-32-vm: 4

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1275446&startday=2016-11-21&endday=2016-11-27&tree=all
(Assignee)

Updated

a year ago
Flags: needinfo?(poirot.alex)
status-firefox51: --- → unaffected
status-firefox52: --- → affected

Comment 24

a year ago
bugherderuplift
https://hg.mozilla.org/releases/mozilla-aurora/rev/761f6ef1cf34
status-firefox52: affected → fixed
Flags: in-testsuite-
You need to log in before you can comment on or make changes to this bug.