RunnerSuite.TestOneWorkerStartWhenStopping timed out
Bug #1583771 reported by
Curtis Hovey
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
William Reade |
Bug Description
As seen in
http://
The RunnerSuite.
runner_test.go:147:
starter.
runner_test.go:351:
c.Fatalf("timed out waiting for start notification")
... Error: timed out waiting for start notification
Changed in juju-core: | |
importance: | Medium → High |
Changed in juju-core: | |
assignee: | nobody → William Reade (fwereade) |
Changed in juju-core: | |
status: | Triaged → Fix Committed |
Changed in juju-core: | |
milestone: | none → 2.0-beta14 |
Changed in juju-core: | |
status: | Fix Committed → In Progress |
Changed in juju-core: | |
milestone: | 2.0-beta14 → 2.0-beta15 |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0-beta15 → none |
milestone: | none → 2.0-beta15 |
To post a comment you must log in.
Ha, found the other race now: just because the *worker* knows it's been started doesn't mean the *runner* knows that yet, which means that we need synchronisation between lines 136-137:
starter. assertStarted( c, true) StopWorker( "id")
err = runner.
...lest the stop be ignored because "nothing is started", and the rest of the test continue to run against an unexpected state. Trying to think of something more reliable than a voodoo sleep.