1446186 - Intermittent browser/components/preferences/in-content/tests/browser_search_within_preferences_1.js | Should be in search results -

Status: RESOLVED FIXED

(Firefox :: Settings UI, defect, P5)

Description

[Treeherder Bug Filer]

Filed by: ccoroiu [at] mozilla.com

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

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

[task 2018-03-15T20:56:48.565Z] 20:56:48     INFO - TEST-PASS | browser/components/preferences/in-content/tests/browser_search_within_preferences_1.js | Should not be in general tab: weavePrefsDeck - 
[task 2018-03-15T20:56:48.566Z] 20:56:48     INFO - Leaving test bound 
[task 2018-03-15T20:56:48.567Z] 20:56:48     INFO - Entering test bound 
[task 2018-03-15T20:56:48.568Z] 20:56:48     INFO - Buffered messages logged at 20:56:47
[task 2018-03-15T20:56:48.569Z] 20:56:48     INFO - TEST-PASS | browser/components/preferences/in-content/tests/browser_search_within_preferences_1.js | Element should not be null, when checking visibility - 
[task 2018-03-15T20:56:48.570Z] 20:56:48     INFO - TEST-PASS | browser/components/preferences/in-content/tests/browser_search_within_preferences_1.js | Should not be in search results yet - 
[task 2018-03-15T20:56:48.571Z] 20:56:48     INFO - TEST-PASS | browser/components/preferences/in-content/tests/browser_search_within_preferences_1.js | Search input should be focused when visiting preferences - 
[task 2018-03-15T20:56:48.571Z] 20:56:48     INFO - Buffered messages logged at 20:56:48
[task 2018-03-15T20:56:48.572Z] 20:56:48     INFO - TEST-PASS | browser/components/preferences/in-content/tests/browser_search_within_preferences_1.js | Element should not be null, when checking visibility - 
[task 2018-03-15T20:56:48.573Z] 20:56:48     INFO - Buffered messages finished
[task 2018-03-15T20:56:48.574Z] 20:56:48     INFO - TEST-UNEXPECTED-FAIL | browser/components/preferences/in-content/tests/browser_search_within_preferences_1.js | Should be in search results - 
[task 2018-03-15T20:56:48.575Z] 20:56:48     INFO - Stack trace:
[task 2018-03-15T20:56:48.576Z] 20:56:48     INFO - chrome://mochitests/content/browser/browser/components/preferences/in-content/tests/head.js:is_element_visible:24
[task 2018-03-15T20:56:48.577Z] 20:56:48     INFO - chrome://mochitests/content/browser/browser/components/preferences/in-content/tests/browser_search_within_preferences_1.js:null:164
[task 2018-03-15T20:56:48.724Z] 20:56:48     INFO - TEST-PASS | browser/components/preferences/in-content/tests/browser_search_within_preferences_1.js | Element should not be null, when checking visibility - 
[task 2018-03-15T20:56:48.726Z] 20:56:48     INFO - TEST-PASS | browser/components/preferences/in-content/tests/browser_search_within_preferences_1.js | Should not be in search results - 
[task 2018-03-15T20:56:48.806Z] 20:56:48     INFO - Leaving test bound 
[task 2018-03-15T20:56:48.806Z] 20:56:48     INFO - Entering test bound 
[task 2018-03-15T20:56:50.077Z] 20:56:50     INFO - TEST-PASS | browser/components/preferences/in-content/tests/browser_search_within_preferences_1.js | Element should not be null, when checking visibility - 
[task 2018-03-15T20:56:50.078Z] 20:56:50     INFO - TEST-PASS | browser/components/preferences/in-content/tests/browser_search_within_preferences_1.js | Should not be in general - 
[task 2018-03-15T20:56:50.078Z] 20:56:50     INFO - TEST-PASS | browser/components/preferences/in-content/tests/browser_search_within_preferences_1.js | Search input should be focused when visiting preferences - 
[task 2018-03-15T20:56:51.335Z] 20:56:51     INFO - TEST-PASS | browser/components/preferences/in-content/tests/browser_search_within_preferences_1.js | Element should not be null, when checking visibility - 
[task 2018-03-15T20:56:51.338Z] 20:56:51     INFO - TEST-PASS | browser/components/preferences/in-content/tests/browser_search_within_preferences_1.js | Should be in generalPane - 
[task 2018-03-15T20:56:51.417Z] 20:56:51     INFO - Leaving test bound

Comment 1

[Intermittent Failures Robot]

50 failures in 168 pushes (0.298 failures/push) were associated with this bug yesterday.    

Repository breakdown:
* autoland: 20
* mozilla-central: 16
* try: 11
* mozilla-inbound: 3

Platform breakdown:
* linux64: 13
* linux32: 12
* windows7-32: 4
* linux64-stylo-disabled: 4
* windows10-64: 3
* osx-10-10: 3
* linux64-nightly: 3
* linux64-jsdcov: 3
* linux32-stylo-disabled: 3
* linux64-devedition: 1
* linux32-devedition: 1

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

Comment 2

[Narcis Beleuzu [:NarcisB]]

This fail started 2 days ago and already has 50 failures. Most of them in Linux.
:jaws, can you please take a look?

Comment 3

[Ed Lee :Mardak]

Suspiciously this started with bug 1446053, which has been backed out for bug 1446392. I'll move the ni? to the other bug.

https://hg.mozilla.org/mozilla-central/rev/991d04043b537d38fae8f5f12252ba3b547d86b3

Comment 4

[Intermittent Failures Robot]

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

This is the #18 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: 34
* mozilla-central: 16
* try: 12
* mozilla-inbound: 3

Platform breakdown:
* linux64: 19
* linux32: 15
* windows7-32: 5
* windows10-64: 5
* osx-10-10: 5
* linux64-stylo-disabled: 5
* linux64-nightly: 3
* linux64-jsdcov: 3
* linux32-stylo-disabled: 3
* linux64-devedition: 1
* linux32-devedition: 1

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

Comment 5

[Ed Lee :Mardak]

This might actually have been caused / fixed in bug 1445084 comment 42.

gandalf, does that sound right? I'm trying to reland our about preferences stuff, and comment 0 happened fail with our landing bug 1446053, so I assumed we caused the failure.

I'm still in the process of repushing various m-c commits to try to try to reproduce this failure, but perhaps it's fixed by bug 1445084?

Comment 6

[Zibi Braniecki [:zbraniecki][:gandalf]]

Seems very similar (one line off in the stack).

Comment 7

[Intermittent Failures Robot]

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

Repository breakdown:
* autoland: 1

Platform breakdown:
* windows7-32: 1

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