MeterStatusWatcher tests fail on windows test slave

Bug #1446857 reported by Martin Packman
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
High
Matthew Williams

Bug Description

Both metering tests in state that use s.unit.WatchMeterStatus()/assertMeterStatusChanged() fail on the windows unit test run on CI:

<http://reports.vapour.ws/releases/2549/job/run-unit-tests-win2012-amd64/attempt/276>

FAIL: meterstatus_test.go:105: MeterStateSuite.TestMeterStatusWatcherRespondsToMetricsManager
FAIL: meterstatus_test.go:98: MeterStateSuite.TestMeterStatusWatcherRespondstoMeterStatus
...
SetUpTest done
[LOG] 0:00.336 INFO juju.mongo dialled mongo successfully on address "127.0.0.1:58193"
[LOG] 0:00.338 INFO juju.mongo dialled mongo successfully on address "127.0.0.1:58193"
meterstatus_test.go:102:
    assertMeterStatusChanged(c, watcher)
meterstatus_test.go:125:
    c.Fatalf("expected event from watcher by now")
...

This may not be directly windows related. The current windows VM is pretty slow, so could also be a timing issue. That said, the code appears to use LongWait correctly, and 10 seconds should be enough for anyone?

Changed in juju-core:
assignee: nobody → Matthew Williams (mattyw)
status: Triaged → In Progress
Revision history for this message
Matthew Williams (mattyw) wrote :
Changed in juju-core:
status: In Progress → Fix Committed
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.