snapd spread kill-timeout too short for dragonboard

Bug #1674378 reported by Selene ToyKeeper on 2017-03-20
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
snapd
Medium
Unassigned

Bug Description

Snapd's test suite fails on dragonboard because the hardware is slower than the tests expect. This is easy to fix by increasing the kill-timeout.

I've seen the test suite take as long as 10 hours to complete on db410c, so it needs pretty lax timeout limits.

Patch for snapd 2.23 attached.

Selene ToyKeeper (toykeeper) wrote :
Paul Larson (pwlars) wrote :

This also seems to be a problem on rpi (unsurprisingly)

Michael Vogt (mvo) wrote :

Adding Sergio for his opinion, he is running the tests on the dragonboard and pi2/3 regularly.

Changed in snapd:
importance: Undecided → Medium
status: New → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments