Closed
Bug 759584
Opened 13 years ago
Closed 12 years ago
Lots of CI failures with TypeError: this.curBrowser is null
Categories
(Remote Protocol :: Marionette, defect)
Remote Protocol
Marionette
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: jgriffin, Unassigned)
Details
On the CI, many test runs have half or more of the tests failing with:
MarionetteException: {'message': "error occurred while processing 'setScriptTimeout' request: TypeError: this.curBrowser is null", 'from': 'conn18.marionette1', 'error': 'unknownError'}
Some runs pass, however.
My guess is that there is some timing issue on the (slow) CI machine which causes use to try and do things before gecko is really fully started up.
See:
http://brasstacks.mozilla.com/autolog/?tree=b2g&source=autolog&rev=2fbd374ac69833d4a421f6967f9922feeef2b678
| Reporter | ||
Comment 1•12 years ago
|
||
This bug is very old; we'll open a new one if we see this problem in current automation.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Updated•2 years ago
|
Product: Testing → Remote Protocol
You need to log in
before you can comment on or make changes to this bug.
Description
•