Closed Bug 1390910 Opened 7 years ago Closed 7 years ago

Intermittent browser/components/preferences/in-content-new/tests/browser_search_subdialogs_within_preferences_7.js | This test exceeded the timeout threshold. It should be rewritten or split up. If that's not possible, use requestLongerTimeout(N)

Categories

(Firefox :: Settings UI, defect, P5)

Product:
Firefox
Component:
Settings UI
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1391507

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Keywords: intermittent-failure, Whiteboard: [stockwell fixed:other]) 

this failure has really increased in frequency in the last couple days, all on linux32 debug.

here is a recent log file:
https://treeherder.mozilla.org/logviewer.html#?repo=mozilla-central&job_id=124880675&lineNumber=10873

and the related screenshot:
https://queue.taskcluster.net/v1/task/YVV0B3ACRF6jQGnLKARX5A/runs/0/artifacts/public/test_info//mozilla-test-fail-screenshot_zoQaJh.png

here is related failure information from the above log:
task 2017-08-22T14:29:58.343833Z] 14:29:58     INFO - TEST-PASS | browser/components/preferences/in-content-new/tests/browser_search_subdialogs_within_preferences_7.js | Element should not be null, when checking visibility - 
[task 2017-08-22T14:29:58.346113Z] 14:29:58     INFO - TEST-PASS | browser/components/preferences/in-content-new/tests/browser_search_subdialogs_within_preferences_7.js | Should not be in search results - 
[task 2017-08-22T14:29:58.350060Z] 14:29:58     INFO - TEST-PASS | browser/components/preferences/in-content-new/tests/browser_search_subdialogs_within_preferences_7.js | Element should not be null, when checking visibility - 
[task 2017-08-22T14:29:58.352369Z] 14:29:58     INFO - TEST-PASS | browser/components/preferences/in-content-new/tests/browser_search_subdialogs_within_preferences_7.js | Should not be in search results - 
[task 2017-08-22T14:29:58.359923Z] 14:29:58     INFO - TEST-PASS | browser/components/preferences/in-content-new/tests/browser_search_subdialogs_within_preferences_7.js | Element should not be null, when checking visibility - 
[task 2017-08-22T14:29:58.362184Z] 14:29:58     INFO - TEST-PASS | browser/components/preferences/in-content-new/tests/browser_search_subdialogs_within_preferences_7.js | Should not be in search results - 
[task 2017-08-22T14:29:58.365887Z] 14:29:58     INFO - TEST-PASS | browser/components/preferences/in-content-new/tests/browser_search_subdialogs_within_preferences_7.js | Element should not be null, when checking visibility - 
[task 2017-08-22T14:29:58.372276Z] 14:29:58     INFO - TEST-PASS | browser/components/preferences/in-content-new/tests/browser_search_subdialogs_within_preferences_7.js | Should not be in search results - 
[task 2017-08-22T14:29:58.375531Z] 14:29:58     INFO - TEST-PASS | browser/components/preferences/in-content-new/tests/browser_search_subdialogs_within_preferences_7.js | Element should not be null, when checking visibility - 
[task 2017-08-22T14:29:58.379934Z] 14:29:58     INFO - TEST-PASS | browser/components/preferences/in-content-new/tests/browser_search_subdialogs_within_preferences_7.js | Should not be in search results - 
[task 2017-08-22T14:29:58.383477Z] 14:29:58     INFO - TEST-PASS | browser/components/preferences/in-content-new/tests/browser_search_subdialogs_within_preferences_7.js | Element should not be null, when checking visibility - 
[task 2017-08-22T14:29:58.385878Z] 14:29:58     INFO - TEST-PASS | browser/components/preferences/in-content-new/tests/browser_search_subdialogs_within_preferences_7.js | Should not be in search results - 
[task 2017-08-22T14:29:58.389780Z] 14:29:58     INFO - TEST-PASS | browser/components/preferences/in-content-new/tests/browser_search_subdialogs_within_preferences_7.js | Element should not be null, when checking visibility - 
[task 2017-08-22T14:29:58.392010Z] 14:29:58     INFO - TEST-PASS | browser/components/preferences/in-content-new/tests/browser_search_subdialogs_within_preferences_7.js | Should not be in search results - 
[task 2017-08-22T14:29:58.396321Z] 14:29:58     INFO - Buffered messages logged at 14:29:53
[task 2017-08-22T14:29:58.400362Z] 14:29:58     INFO - Leaving test bound 
[task 2017-08-22T14:29:58.402632Z] 14:29:58     INFO - Buffered messages finished
[task 2017-08-22T14:29:58.406281Z] 14:29:58     INFO - TEST-UNEXPECTED-FAIL | browser/components/preferences/in-content-new/tests/browser_search_subdialogs_within_preferences_7.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 2017-08-22T14:29:58.409537Z] 14:29:58     INFO - GECKO(1492) | MEMORY STAT | vsize 1042MB | residentFast 261MB | heapAllocated 92MB
[task 2017-08-22T14:29:58.413811Z] 14:29:58     INFO - TEST-OK | browser/components/preferences/in-content-new/tests/browser_search_subdialogs_within_preferences_7.js | took 95080ms


quite possibly we just need to extend the timeout given that we typically see many 90+ second test runs for this specific test.


:jaws, do you see other things we should do to this test?  are you ok with extending the runtime assuming that fixes the test?
Flags: needinfo?(jaws)
Whiteboard: [stockwell needswork]
I don't see anything particular with this test, just that we need to make searching faster. Extending the time for this test is OK with me.
Flags: needinfo?(jaws)
fixing this with a patch in bug 1391507
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Whiteboard: [stockwell needswork] → [stockwell fixed:other]
You need to log in before you can comment on or make changes to this bug.