Closed Bug 811949 Opened 13 years ago Closed 13 years ago

Many gaiatest tests are timing out when attempting to launch apps in the CI

Categories

(Remote Protocol :: Marionette, defect)

defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jgriffin, Unassigned)

References

Details

One observation is that we really need to add killAll to all the tests setUp(), but we can't until we merge that change from gaia into the gaia-ui-tests repo; see my recent e-mail to mozwebqa.
(In reply to Jonathan Griffin (:jgriffin) from comment #1) > One observation is that we really need to add killAll to all the tests > setUp(), but we can't until we merge that change from gaia into the > gaia-ui-tests repo; see my recent e-mail to mozwebqa. Just an update for those following along at home; this was done tonight by Jonathan (thanks!), and additional test-stability fixes/attempts were made, as well: https://github.com/mozilla/gaia-ui-tests/commits/master
Severity: normal → critical
I have seen that `window.wrappedJSObject.ScreenManager.turnScreenOn();` has been added in: https://github.com/mozilla/gaia-ui-tests/commit/1b1d3fd2c804b83107a16986cc24fb4923e4b63e Do we really have to use wrappedJSObject? Can't we use XPCNativeWrapper.unwrap() here which is more secure?
It is only less safe if you're not sure what kind of object window is. However, due to the way Marionette is set up, we're 100% certain what window is. However, feel free to file a bug and submit a patch with that change if you like.
Blocks: 801898
Is this still happening frequently? If not, I'd like to downgrade its priority.
(In reply to Jonathan Griffin (:jgriffin) from comment #5) > Is this still happening frequently? If not, I'd like to downgrade its > priority. Dave, were you able to recreate this issue as part of testing the conditions/fix for bug 812541?
I haven't seen this issue for a long time now. Closing as WORKSFORME.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Product: Testing → Remote Protocol
You need to log in before you can comment on or make changes to this bug.