i386 unit-tests fail
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| juju-core | ||||||
| 1.22 |
Fix Released
|
Critical
|
Dimiter Naydenov | |||
Bug Description
The i386 unit tests are failing recently. The last successful run on these tests for 1.22 was Commit 9246af3. As
Commit 2e31f07 Merge pull request #1635 from axw/lp1420049-
the suite fails 100% of the time because of
FAIL github.
and 25% of the failures include
FAIL: filter_test.go:106: FilterSuite.
As ec2 can only provide an under powered instance for i386 testing, QA setup a dedicated and powerful trusty 386 machine in HP Cloud. There tests also fail, but for different reasons. Changes were merged to fix an outstanding issue for the ping tests that always failed. The tests are run in lxc to isolate the packages from the local-deployment tests. The are two remaining failures....
The suite fails 50% of the time because of a timeout
FAIL github.
and 50% of the time because of
FAIL github.
The QA team prefers that the trusty-i386-lxc on HP case be fix so because the tests run in 1 hour, half the time of the ec2 tests. These tests are run on many other series and archs. If we are confident the failures are not about architecuture but about tests infrastructure on 386, skipping the tests would be acceptable.
I am attached logs for the errors seen.
| Curtis Hovey (sinzui) wrote | #1 |
| Curtis Hovey (sinzui) wrote | #2 |
| Curtis Hovey (sinzui) wrote | #3 |
| Dimiter Naydenov (dimitern) wrote | #5 |
| Dimiter Naydenov (dimitern) wrote | #7 |
The ec2 precise tests were run this way
juju-