launchpad-dev team mailing list archive

[Steve Kowalik <steve.kowalik@xxxxxxxxxxxxx>]

On 16/08/10 22:49, Guilherme Salgado wrote:
> 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.

Okay, so, I was discussing this with Robert at the time, so most of the 
ideas are his. Take the current output from ec2, and see which test is 
last. Use subunit-ls on a known-good ec2 run, and grab the last test, 
plus the next 20 or 30. Run only them using bin/test -vv --load-list 
<filename>.

That gave me "lib/lp/soyuz/doc/buildd-slavescanner.txtKilled" so that 
has to be the culprit. Then, since it's a doctest, I had no other way of 
debugging, so I went in and binary searched the file by deleting half 
the file, then running the test again and seeing if that fixed it. That 
led me to the block that caused the problem.

Cheers,
--
                                        Steve
Soyuz Developer
Canonical, Ltd