Open Bug 1455882 Opened 2 years ago Updated 9 months ago

Intermittent browser/base/content/test/tabs/browser_new_tab_insert_position.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. -

Categories

(Firefox :: Tabbed Browser, defect, P5)

defect

Tracking

()

People

(Reporter: intermittent-bug-filer, Unassigned)

Details

(Keywords: intermittent-failure, leave-open, Whiteboard: [stockwell disabled][retriggered])

Attachments

(1 file)

Filed by: archaeopteryx [at] coole-files.de

https://treeherder.mozilla.org/logviewer.html#?job_id=174929305&repo=try

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

Seen in a central-as-beta simulation:

[task 2018-04-21T11:22:31.382Z] 11:22:31     INFO - TEST-PASS | browser/base/content/test/tabs/browser_new_tab_insert_position.js | tab pos 4 matched http://mochi.test:8888/#4 - 
[task 2018-04-21T11:22:31.387Z] 11:22:31     INFO - Buffered messages logged at 11:22:30
[task 2018-04-21T11:22:31.389Z] 11:22:31     INFO - Leaving test bound test_settings_always_insertAtEnd
[task 2018-04-21T11:22:31.393Z] 11:22:31     INFO - Buffered messages finished
[task 2018-04-21T11:22:31.398Z] 11:22:31     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/tabs/browser_new_tab_insert_position.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. -
Over the last 7 days there are 32 failures present on this bug. All of these happen on Linux
This is the most recent log example: https://treeherder.mozilla.org/logviewer.html#?repo=autoland&job_id=178098332&lineNumber=7833

[task 2018-05-11T21:29:40.495Z] 21:29:40     INFO - Buffered messages logged at 21:29:39
[task 2018-05-11T21:29:40.496Z] 21:29:40     INFO - Leaving test bound test_settings_always_insertAtEnd
[task 2018-05-11T21:29:40.497Z] 21:29:40     INFO - Buffered messages finished
[task 2018-05-11T21:29:40.497Z] 21:29:40     INFO - TEST-UNEXPECTED-FAIL | browser/base/content/test/tabs/browser_new_tab_insert_position.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N), but only as a last resort. - 
[task 2018-05-11T21:29:40.498Z] 21:29:40     INFO - TEST-FAIL | browser/base/content/test/tabs/browser_new_tab_insert_position.js | Assertion count 15 is greater than expected range 0-0 assertions. - 
[task 2018-05-11T21:29:40.499Z] 21:29:40     INFO - GECKO(1736) | MEMORY STAT | vsize 1245MB | residentFast 314MB | heapAllocated 86MB
[task 2018-05-11T21:29:40.499Z] 21:29:40     INFO - TEST-OK | browser/base/content/test/tabs/browser_new_tab_insert_position.js | took 94542ms
[task 2018-05-11T21:29:40.500Z] 21:29:40     INFO - GECKO(1736) | ++DOCSHELL 0xe1e4d400 == 3 [pid = 1855] [id = {16df34ef-f430-4a74-ad9c-eb37d2e40157}]
Flags: needinfo?(dao+bmo)
Whiteboard: [stockwell needswork]
There is something peculiar that I've noticed working on finding when this started to fail so often in the last couple of days. 
First of all, this moves between chunks and was not easy to follow. 

Worked on this range on autoland http://tinyurl.com/y8spxmfy and it started failling on a merge push so I went to inbound to continue with the investigation. 

The merge candidate from inbound was this one http://tinyurl.com/y7paa2b2. Did some retriggeres there and on a push before that and got no failures at all. This was the range http://tinyurl.com/y8ycjt3r. 
So on inbound it did not fail at all from ~25 jobs (bc8) and then after the merge it almost permafails (30 out of 31 jobs) on bc2 and then moves to bc7 and so on... 
Given the way this looks as a failure rate I'd say a backout is required but can't imagine what exactly should be backed out. 

Joel, can you have a take on what's going on here? Thank you.
Flags: needinfo?(jmaher)
Whiteboard: [stockwell needswork] → [stockwell needswork][retriggered]
It seems to be failing at a normal intermittent rate, nowhere near as it's failing after the merge. At first I thought it is a permafail when I found it in bc7. It keeps moving between chunks but when this test is ran it almost always fails now. 
Looking at the graph for last 7 days it is concerning at least https://treeherder.mozilla.org/intermittent-failures.html#/bugdetails?startday=2018-05-07&endday=2018-05-14&tree=trunk&bug=1455882

Should we consider disabling it for now?
yes, lets disable it
Attachment #8975696 - Flags: review?(nbeleuzu)
Attachment #8975696 - Flags: review?(cbrindusan)
Attachment #8975696 - Flags: review?(nbeleuzu) → review+
Attachment #8975696 - Flags: review?(cbrindusan) → review+
Pushed by csabou@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/b0a2ca2115b3
Disable browser/base/content/test/tabs/browser_new_tab_insert_position.js on Linux 32 debug for almost permafailing. r=nbeleuzu,cbrindusan
Keywords: leave-open
Whiteboard: [stockwell needswork][retriggered] → [stockwell disabled][retriggered]
Flags: needinfo?(dao+bmo)
You need to log in before you can comment on or make changes to this bug.