pingerSuite tests consistenly fail on trusty+386 and vivid+amd64
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | juju-core |
Medium
|
Eric Snow | ||
| | 1.23 |
Medium
|
Eric Snow | ||
Bug Description
We want to move the 386 unit tests to a dedicated fast machine. We cannot because the Juju test suite has never passed on trusty 386. The pingerSuite is the common failure, but the specifc test varies.
pinger_
root_
Addendum: Vivid+amd64 also fails because of these tests, but vivid is an openstack instance, not lxc.
| tags: |
added: ci i386 removed: 386 |
| Curtis Hovey (sinzui) wrote : | #1 |
| Curtis Hovey (sinzui) wrote : | #2 |
This is the non-voting job that shows the problem over many runs http://
| Martin Packman (gz) wrote : | #3 |
Both of these tests involve time.Sleep calls - I have seen them fail previously running under lxc for what I presumed were speed issues. Ideally the tests get redone to not involve sleeps, but otherwise skipping in some fashion would unblock us.
| summary: |
- pingerSuite tests consistenly fail on trusty 386 + pingerSuite tests consistenly fail on trusty+386 and vivid+amd64 |
| description: | updated |
| Curtis Hovey (sinzui) wrote : | #4 |
The vivid unit tests no longer run in lxc, but the pinger suites are still among the failures.
| Eric Snow (ericsnowcurrently) wrote : | #5 |
| Changed in juju-core: | |
| assignee: | nobody → Eric Snow (ericsnowcurrently) |
| status: | Triaged → In Progress |
| milestone: | none → 1.24-alpha1 |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |


Attached is an example of one of the failure.