Closed Bug 1104755 Opened 6 years ago Closed 3 years ago

Intermittent browser_tabMatchesInAwesomebar_perwindowpb.js | undefined assertion name - | Test timed out - expected PASS | Found a browser window after previous test timed out - expected PASS

Categories

(Firefox :: Address Bar, defect, P5)

x86
Linux
defect
Points:
1

Tracking

()

RESOLVED INACTIVE
Firefox 37

People

(Reporter: cbook, Unassigned)

References

()

Details

(Keywords: intermittent-failure, Whiteboard: [unifiedautocomplete][fxsearch])

Attachments

(1 file)

Ubuntu VM 12.04 mozilla-inbound opt test mochitest-browser-chrome-1

https://treeherder.mozilla.org/ui/logviewer.html#?job_id=4195336&repo=mozilla-inbound

06:53:08 INFO - 550 INFO TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/general/browser_tabMatchesInAwesomebar_perwindowpb.js | undefined assertion name -
Summary: Intermittent browser_tabMatchesInAwesomebar_perwindowpb.js | undefined assertion name - → Intermittent browser_tabMatchesInAwesomebar_perwindowpb.js | undefined assertion name - | Test timed out - expected PASS | Found a browser window after previous test timed out - expected PASS
Tag, you're it!
Component: General → Location Bar
Flags: needinfo?(ttaubert)
I disabled this test in bug 1105456 cause it was perma-timing-out locally too, at least for me, and not allowing me to green-ify central.

We should try to re-enable it soon though.
Whiteboard: [test-disabled]
note that it was permanently timing out after DISABLING unified complete. I didn't try before so maybe it was just intermittent before. This could be a good hint to figure the issue.
Turns out I got selecting the last entry a little wrong. Test works at least locally now with and without unified complete.
Assignee: nobody → ttaubert
Status: NEW → ASSIGNED
Flags: needinfo?(ttaubert)
Attachment #8529760 - Flags: review?(mak77)
Iteration: --- → 37.1
Points: --- → 1
Flags: qe-verify-
Flags: firefox-backlog+
Comment on attachment 8529760 [details] [diff] [review]
0001-Bug-1104755-Re-enable-browser_tabMatchesInAwesomebar.patch

Review of attachment 8529760 [details] [diff] [review]:
-----------------------------------------------------------------

it is working fine here!
Attachment #8529760 - Flags: review?(mak77) → review+
https://hg.mozilla.org/mozilla-central/rev/32c23b2935ca
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 37
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Whiteboard: [test-disabled]
Status: REOPENED → ASSIGNED
Iteration: 37.1 → 37.2
How many more weeks of ignoring these failures do we need to have before re-disabling the test?
Flags: needinfo?(ttaubert)
We'll have to see if bug 1073339 helps here - trying to get this landed for some time now. If it doesn't I'll need to take a closer look at just this test again.
Depends on: 1073339
Bug 1073339 landed on fx-team some hours ago, let's see if that improves the situation.
(In reply to TBPL Robot from comment #223)
> submit_timestamp: 2014-12-17T03:38:54
> log:
> https://treeherder.mozilla.org/ui/logviewer.html#?repo=fx-team&job_id=1464062
> repository: fx-team
> who: tomcat[at]mozilla[dot]com
> machine: tst-linux32-spot-724
> buildname: Ubuntu VM 12.04 fx-team opt test mochitest-browser-chrome-1
> revision: a76b8d5ee8dc

Too bad, so it's still happening on fx-team, looks like a slightly lower frequency maybe? I'm having a hard time reproducing that on my Ubuntu VM unfortunately. I see timeouts all over the place in browser/base/content/test/general/ but didn't check whether those timeouts are tracked intermittent failures.
Flags: needinfo?(ttaubert)
This briefly went almost-perma-orange when I landed bug 1079303 (backed out now), and I don't understand why. Marco, ideas? This shouldn't really be affected by changes in PopupNotifications.jsm. :-\
Flags: needinfo?(mak77)