On Mon, 2010-08-16 at 22:26 +1000, Steve Kowalik wrote: > Hi, > > Currently, we are seeing EC2 instances having the test runner die in a > heap due to the OOM killer stepping in and killing the test runner since > it's consuming all of the RAM. > > I had a branch fall victim to this over the weekend, and nailed it down > to lib/lp/soyuz/doc/buildd-slavescanner.txt, line 51, in the call to > .updateStatus().
Did you document anywhere how you nailed it down to the OOM killer kicking in on that specific test? I think others have seen the same symptom but where unable to find out what was causing it, so it'd be good to have that documented. -- Guilherme Salgado <https://launchpad.net/~salgado>
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
