Seeing high rate of unlock failures in krillin smoke testing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity8 (Ubuntu) |
New
|
Undecided
|
Kevin Gunn |
Bug Description
This problem was seen 14 times over images 129-134 from ubuntu-
[console]
+ reboot-
13 KB/s (1049 bytes in 0.078s)
INFO:reboot-
INFO:reboot-
INFO:reboot-
PING launchpad.net (91.189.89.223) 56(84) bytes of data.
INFO:reboot-
I: Unlock attempt 1 failed, script output: 'Error: Timeout was reached
'
I: Unlock attempt 2 failed, script output: 'Error: Timeout was reached
'
I: Unlock attempt 3 failed, script output: 'Error: Timeout was reached
'
I: Unlock attempt 4 failed, script output: 'Error: Timeout was reached
'
I: Unlock attempt 5 failed, script output: 'Error: Timeout was reached
'
I: Too many unlock failures, giving up
[/console]
The smoke tests do reboot the phone between test suites, so it ends up rebooting the phone a few dozen times during a full run. Looking back through prior logs, I see this older examples of this, but it appears to be a little more frequent over the past week. Perhaps this is related to https:/
Here are some examples:
image 134
http://
http://
http://
http://
image 133
http://
image 132
http://
http://
http://
image 131
http://
http://
http://
image 130
http://
http://
image 129
http://
So yeah, this looks exactly like a more frequent bug 1421009, which was due to a dbus mutex hang.
Here are some possibly related dbus hang bugs:
Bug 1421009 (vivid, basically same bug as this one)
Bug 1417773 (RTM)
Bug 1421308 (vivid?)
The most reliable reproducer of the bunch is bug 1421009, which involves reflashing a bunch.
And it also suggests the earliest sign of the bug as vivid image 106.