Closed Bug 521375 Opened 15 years ago Closed 12 years ago

random failure of browser_privatebrowsing_urlbarfocus.js

Categories

(Firefox :: Private Browsing, defect)

x86
Windows Vista
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: robert.strong.bugs, Unassigned)

References

Details

(Keywords: intermittent-failure)

WINNT 5.2 mozilla-central test opt everythingelse on 2009/10/08 22:27:12

TEST-UNEXPECTED-FAIL | chrome://mochikit/content/browser/browser/components/privatebrowsing/test/browser/browser_privatebrowsing_urlbarfocus.js | URL Bar should be focused inside the private browsing mode - Got null, expected [object HTMLInputElement]

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox-Unittest/1255066032.1255067457.28465.gz
Whiteboard: [orange]
This seems to have only happened once.  Resolving as WFM for now.  Feel free to reopen if you see it again.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Mass marking whiteboard:[orange] bugs WFM (to clean up TBPL bug suggestions) that:
* Haven't changed in > 6months
* Whose whiteboard contains none of the strings: {disabled,marked,random,fuzzy,todo,fails,failing,annotated,leave open,time-bomb}
* Passed a (quick) manual inspection of bug summary/whiteboard to ensure they weren't a false positive.

I've also gone through and searched for cases where the whiteboard wasn't labelled correctly after test disabling, by using attachment description & basic comment searches. However if the test for which this bug was about has in fact been disabled/annotated/..., please accept my apologies & reopen/mark the whiteboard appropriately so this doesn't get re-closed in the future (and please ping me via IRC or email so I can try to tweak the saved searches to avoid more edge cases).

Sorry for the spam! Filter on: #FFA500
Status: REOPENED → RESOLVED
Closed: 14 years ago12 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.