https://bugs.launchpad.net/juju-core/+bug/1564511
The reboot tests are broken - they patch out the creation of containers when they expect to create them, but not when they don't. They patch out the watching of containers when they want to see them reboot, but not when they don't. AFAIK they always interact with LXD! James On Sat, Apr 9, 2016 at 1:45 AM, David Cheney <[email protected]> wrote: > If the test suite panics, especially during a tear down from a failure > set up, you leak mongos and data in /tmp. I have a cron job that runs > a few times a day to keep this leaking below a few gig. > > On Sat, Apr 9, 2016 at 8:13 AM, Horacio Duran > <[email protected]> wrote: >> Hey, this is more of an open question/sharing. >> I was a good half hour trying to find why reboot test was timeouting and >> found that I had a couple of lxcs that I dont recall creating (at least one >> of them was a juju api server) and a good 5-8 mongos running. >> I killed the test, the mongos and the lxcs and magic, the reboot tests ran >> well. >> Did anyone else detect this kind of behavior? I believe either destroy (I >> deployed a couple of times earlier and destroyed) or the tests are leaking, >> at least, lxcs Ill try to repro later but so far I would like some one >> else's input. >> >> -- >> Juju-dev mailing list >> [email protected] >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/juju-dev >> > > -- > Juju-dev mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev -- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
