LAVA Timeout for boot is too long

Bug #874594 reported by Paul Larson
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
LAVA Dispatcher
Fix Released
Low
Spring Zhang
Linaro Android
Fix Released
Undecided
Unassigned

Bug Description

The time it takes to notice that we have booted into the master or test image uses the default timeout of 1 hour. We should shorten this to something more reasonable - not too short, but short enough to keep the job from taking an hour to realize that the kernel hung or panicked on boot.

Related branches

Revision history for this message
Paul Larson (pwlars) wrote :

This is for both ubuntu and android of course

Changed in lava-dispatcher:
importance: Undecided → Low
status: New → Triaged
assignee: nobody → Spring Zhang (qzhang)
Revision history for this message
Zach Pfeffer (pfefferz) wrote :

I think it would be good to be able to set these independently and expose this parameter through the API so that the default could be overwritten.

Revision history for this message
Paul Sokolovsky (pfalcon) wrote :

Was also reported as part of https://bugs.launchpad.net/lava-scheduler/+bug/874270

For linaro-android, importance should be more than Low, as it affects Gerrit CI integration seriously.

summary: - Timeout for boot is too long
+ LAVA Timeout for boot is too long
Revision history for this message
Spring Zhang (qzhang) wrote :

The timeout mainly occur in lava_android_test_install and lava_android_test_run with timeout 3600s in bug 874270, but they should be timeout when 2400s for:
    def run(self, tests, timeout=2400):

but the pexpect code set timeout as "None", I think it will wait until client.proc timeout which is 3600s.
rc = pexpect.run(cmd, timeout=None, logfile=sys.stdout, withexitstatus=True)[1]

It is also suggested to have a timeout specified in job file.

Revision history for this message
Yongqin Liu (liuyq0307) wrote :

As I commented in https://bugs.launchpad.net/lava-scheduler/+bug/874270, I don't think this place is needed to modify.
And for the test to be executed, we don't know the time it runs. for example, the long time test will run dozen hours.

Revision history for this message
Spring Zhang (qzhang) wrote :

Even we allow an timeless timeout here, we can't set the timeout to None, we can pass the timeout from the caller to allow a flexible control here, and set the default to -1 but not None.

Spring Zhang (qzhang)
Changed in lava-dispatcher:
status: Triaged → In Progress
milestone: none → 2011.11
Spring Zhang (qzhang)
Changed in lava-dispatcher:
status: In Progress → Fix Committed
Fathi Boudra (fboudra)
Changed in lava-dispatcher:
status: Fix Committed → Fix Released
Amit Pundir (pundiramit)
Changed in linaro-android:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.