sleep test needs more time for device check

Bug #1095668 reported by Jeff Lane 
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Checkbox
Fix Released
Medium
Jeff Lane 

Bug Description

the sleep test (suspend_advanced and suspend_30_cycles) currently has a 30 second delay for the device check performed by FWTS. This may not be long enough, as there appears to be a race condition where ethernet and wifi devices may get their IPs back before 30 seconds, or they may get them back just after 30 seconds, which causes a false failure.

This is not unusual, not necessarily unexpected, it can take a bit sometimes to get an IP via DHCP depending on a multitude of factors.

Solution: increase the device-check-delay to 45 seconds to make sure everything is fully ready to go.

Related branches

Jeff Lane  (bladernr)
Changed in checkbox:
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Jeff Lane (bladernr)
Jeff Lane  (bladernr)
Changed in checkbox:
status: In Progress → Fix Committed
Revision history for this message
Jeffrey Chang (modern911) wrote :

Line 132 of suspend.txt.in has an error, that there's a space character between -- and s3-device-check-delay.
This makes suspend_advanced test fail to execute.
This test is a cert. blocker, please fix.

Changed in checkbox:
status: Fix Committed → Confirmed
Revision history for this message
Brendan Donegan (brendan-donegan) wrote :

Thanks for noticing the problem. Since the fix for this already got into trunk, this bug should be considered fix commited and we shouldn't try and overload it with information about the fix of the regression that was just caused, so we should have a seperate bug.

Changed in checkbox:
status: Confirmed → Fix Committed
Changed in checkbox:
status: Fix Committed → 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.