Closed Bug 1169795 Opened 10 years ago Closed 10 years ago

Intermittent browser_oneOffHeader.js | Test timed out

Categories

(Firefox :: Search, defect)

x86_64
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1170500

People

(Reporter: RyanVM, Unassigned)

Details

(Keywords: intermittent-failure)

Attachments

(1 file)

Attached image test screenshot —
12:31:05 INFO - 1436 INFO TEST-START | browser/components/search/test/browser_oneOffHeader.js 12:31:50 INFO - TEST-INFO | screencapture: exit 0 12:31:50 INFO - 1437 INFO checking window state 12:31:50 INFO - 1438 INFO Entering test init 12:31:50 INFO - 1439 INFO Waiting for engine to be added: testEngine.xml 12:31:50 INFO - 1440 INFO Search engine added: testEngine.xml 12:31:50 INFO - 1441 INFO Leaving test init 12:31:50 INFO - 1442 INFO Entering test test_notext 12:31:50 INFO - 1443 INFO Opening search panel 12:31:50 INFO - 1444 INFO TEST-PASS | browser/components/search/test/browser_oneOffHeader.js | Header has the correct index selected with no search terms. 12:31:50 INFO - 1445 INFO TEST-PASS | browser/components/search/test/browser_oneOffHeader.js | Search header string is correct when no search terms have been entered 12:31:50 INFO - 1446 INFO TEST-PASS | browser/components/search/test/browser_oneOffHeader.js | Header has the correct index when no search terms have been entered and the Change Search Settings button is selected. 12:31:50 INFO - 1447 INFO TEST-PASS | browser/components/search/test/browser_oneOffHeader.js | Header has the correct text when no search terms have been entered and the Change Search Settings button is selected. 12:31:50 INFO - 1448 INFO TEST-PASS | browser/components/search/test/browser_oneOffHeader.js | Header has the correct index selected when a search engine has been selected 12:31:50 INFO - 1449 INFO TEST-PASS | browser/components/search/test/browser_oneOffHeader.js | Is the header text correct when a search engine is selected and no terms have been entered. 12:31:50 INFO - 1450 INFO Closing search panel 12:31:50 INFO - 1451 INFO Leaving test test_notext 12:31:50 INFO - 1452 INFO Entering test test_text 12:31:50 INFO - 1453 INFO Opening search panel 12:31:50 INFO - 1454 INFO TEST-PASS | browser/components/search/test/browser_oneOffHeader.js | Header has the correct index selected with a search term. 12:31:50 INFO - 1455 INFO TEST-PASS | browser/components/search/test/browser_oneOffHeader.js | Search header string is correct when a search term has been entered 12:31:50 INFO - 1456 INFO TEST-UNEXPECTED-FAIL | browser/components/search/test/browser_oneOffHeader.js | Test timed out - expected PASS 12:31:50 INFO - 1457 INFO Search engine removed: testEngine.xml 12:31:50 INFO - MEMORY STAT vsize after test: 3588055040 12:31:50 INFO - MEMORY STAT residentFast after test: 422612992 12:31:50 INFO - MEMORY STAT heapAllocated after test: 87698392 12:31:50 INFO - 1458 INFO TEST-OK | browser/components/search/test/browser_oneOffHeader.js | took 45037ms
Chris, this is pretty frequent. Do you have time to look at this by chance?
Flags: needinfo?(chrishood)
(In reply to Ryan VanderMeulen [:RyanVM UTC-4] from comment #163) > Chris, this is pretty frequent. Do you have time to look at this by chance? This test landed several months ago, and this intermittent failure seems quite recent, do we have any idea of what regressed this?
(In reply to Florian Quèze [:florian] [:flo] from comment #164) > (In reply to Ryan VanderMeulen [:RyanVM UTC-4] from comment #163) > > Chris, this is pretty frequent. Do you have time to look at this by chance? > > This test landed several months ago, and this intermittent failure seems > quite recent, do we have any idea of what regressed this? Oh, just noticed this is Mac only. The search panel's is known to be broken on Mac right now, there's an r+'ed fix in bug 1170500. So I don't think we should spend time investigating here before that fix reaches all the integration branches.
It looks like this started failing on 05/29/2015 which was when the patch for bug 459563 (referenced in bug 1170500) landed which was likely what caused the regression causing mac's search panel breakage. I'm inclined to agree with Florian in that we should wait for the fix for bug 1170500 to be integrated and then see if that fixes the problem.
Flags: needinfo?(chrishood)
Bug 1170500 just landed on fx-team, so we should know soon if this failure disappears. I'm hoping it will, but in any case, it's kinda annoying that the failure was only intermittent. If it had failed all the time, it would have saved us from seeing this broken panel for a couple days.
Not happening anymore now that bug 1170500 is fixed. I would still prefer this failure to have been permanent rather than intermittent, but I don't think this bug is the right one to fix it (bug 1107178 seems better for that; I'm adding a comment there).
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: