race in StatusHistoryTest
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
John A Meinel | ||
2.3 |
Fix Released
|
High
|
John A Meinel |
Bug Description
As seen here (though incorrectly targeted):
http://
I was able to reproduce it locally, just by doing
cd cmd/juju/status
go test --race --check.v
^- unfortunately some of the earlier tests take 90s to complete, so this is a bit expensive (wall clock time is 222s for the whole suite, and a huge amount of time to build.)
Note that I also tried:
go test --race --check.v --check.f StatusHistorySuite
and that does *not* appear to trigger the failure.
==================
WARNING: DATA RACE
Write at 0x00000317e500 by goroutine 35:
reflect.
/
github.
/
github.
/
github.
/
runtime.call32()
/
reflect.
/
gopkg.
/
gopkg.
/
Previous read at 0x00000317e500 by goroutine 36:
time.Now()
/
time.sendTime()
/
Goroutine 35 (running) created at:
gopkg.
/
gopkg.
/
gopkg.
/
gopkg.
/
gopkg.
/
gopkg.
/
Goroutine 36 (running) created at:
runtime.
/
context.
/
net.(
/
net.(
/
net.DialTimeout()
/
gopkg.
/
==================
Changed in juju: | |
status: | Triaged → In Progress |
Changed in juju: | |
milestone: | 2.3.0 → 2.4-beta1 |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
It does seem to be the transition between test suites, I can trigger it a bit faster with: TestSummaryStat usWithUnresolva bleDns"
gt --race --check.f "StatusHistory|