586652 - Global timeout kills software update tests during download of updates

Status: RESOLVED FIXED

(Mozilla QA Graveyard :: Mozmill Automation, defect)

Description

[Henrik Skupin [:whimboo][⌚️UTC+1]]

With the global timeout added for Mozmill 1.4.2 we kill the browser after 60 seconds, if no communication happened via jsbridge. For software updates we will run into timeouts all the time if a download is served slower. We have to increase it to our internal value of 360 seconds.

Comment 1

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Attachment: Patch v1

This patch modifies the software update testrun class and increases the timeout to 360 seconds. With the refactoring from Jeff, which has been moved all dependent functions from the CLI classes to the Mozmill classes it would be easier now, but we have to persist compatiblity with Mozmill 1.4.1. So this is the only way I can see for now.

Comment 2

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Andrew, for your reference those are the automation scripts we use on our test boxes and for the crowd extension. They can be found here:

http://hg.mozilla.org/qa/mozmill-automation/

Comment 3

[Andrew Halberstadt [:ahal]]

Comment on attachment 465245 [details] [diff] [review]
Patch v1

Looks nice and simple, timeout documented.

r=ahalberstadt

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Landed as:
http://hg.mozilla.org/qa/mozmill-automation/rev/fe7b398bd38a

Comment 5

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Move of Mozmill related project bugs to newly created components. You can
filter out those emails by using "Mozmill-Tests-to-MozillaQA" as criteria.