...but I think that axw actually addressed that already. Not sure then; don't really have the bandwidth to investigate deeply right now. Sorry noise.
On Wed, Jun 17, 2015 at 10:52 AM, William Reade <william.re...@canonical.com > wrote: > I think the problem is in the implicit apiserver->leasemgr->state > dependencies; if the lease manager is stopped at the wrong moment, the > apiserver will never shut down because it's waiting on a blocked leasemgr > call. I'll propose something today. > > On Wed, Jun 17, 2015 at 7:33 AM, David Cheney <david.che...@canonical.com> > wrote: > >> This should be achievable. go test sends SIGQUIT on timeout, we can >> setup a SIGQUIT handler in the topmost suite (or import it as a side >> effect package), do whatever cleanup is needed, then os.Exit, unhandle >> the signal and try to send SIGQUIT to ourselves, or just panic. >> >> On Wed, Jun 17, 2015 at 3:25 PM, Tim Penhey <tim.pen...@canonical.com> >> wrote: >> > Hey team, >> > >> > I am getting more and more concerned about the length of time that >> > master has been cursed. >> > >> > It seems that sometime recently we have introduced serious instability >> > in cmd/jujud/agent, and it is often getting wedged and killed by the >> > test timeout. >> > >> > I have spent some time looking, but I have not yet found a definitive >> > cause. At least some of the time the agent is failing to stop and is >> > deadlocked. >> > >> > This is an intermittent failure, but intermittent enough that often at >> > least one of the unit test runs fails with this problem cursing the >> > entire run. >> > >> > One think I have considered to aid in the debugging is to add some code >> > to the juju base suites somewhere (or in testing) that adds a goroutine >> > that will dump the gocheck log just before the test gets killed due to >> > timeout - perhaps a minute before. Not sure if we have access to the >> > timeout or not, but we can at least make a sensible guess. >> > >> > This would give us at least some logging to work through on these >> > situations where the test is getting killed due to running too long. >> > >> > If no one looks at this and fixes it overnight, I'll start poking it >> > with a long stick tomorrow. >> > >> > Cheers, >> > Tim >> > >> > -- >> > Juju-dev mailing list >> > Juju-dev@lists.ubuntu.com >> > Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju-dev >> >> -- >> Juju-dev mailing list >> Juju-dev@lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju-dev >> > >
-- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
