travis jobs fail with a timeout after more than 45 minutes executing
Bug #1555386 reported by
Leo Arias
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Snapcraft |
Fix Released
|
High
|
Leo Arias | ||
Bug Description
Something changed on the travis environment and now our jobs grew from ~10 minutes to more than 45, which makes travis kill them.
Revision history for this message
| Leo Arias (elopio) wrote | #1 |
| Changed in snapcraft: | |
| status: | New → In Progress |
| importance: | Undecided → High |
| assignee: | nobody → Leo Arias (elopio) |
Revision history for this message
| Leo Arias (elopio) wrote | #2 |
| Changed in snapcraft: | |
| status: | In Progress → Fix Committed |
| Changed in snapcraft: | |
| status: | Fix Committed → Fix Released |
| Changed in snapcraft: | |
| milestone: | none → 2.5 |
To post a comment you must log in.
After talking with Sergio, we no longer need to run the tests in a xenial machine because we are already running the autopkgtest and examples in there. We are fine running the tests using the pip packages from xenial. So, I'm getting rid of the lxc hack.