tests regularly fail on buildbot with "no space left on device"

[Michael Hudson-Doyle]

See for example: https://lpbuildbot.canonical.com/builders/lp/builds/149/steps/shell_7/logs/summary

It's a bit strange, as the test suite doesn't use a significant amount of disk space and there's plenty free on the slave image. Maybe it'll turn out to be "one of those EC2 things" but that seems a bit unlikely to me.

[Michael Hudson-Doyle (mwhudson)]

Aaron points out that for the KVM instance he uses for testing, postgres logs can end up being ridiculously huge.

[Stuart Bishop (stub)]

On Wed, Sep 23, 2009 at 4:36 AM, Michael Hudson
<email address hidden> wrote:

> Aaron points out that for the KVM instance he uses for testing, postgres
> logs can end up being ridiculously huge.

When running tests, PostgreSQL statement logs do nothing except slow
things down. We should run with log_statement = 'none' in
postgresql.conf (the default, which we override for some reason).

--
Stuart Bishop <email address hidden>
http://www.stuartbishop.net/

[Gavin Panella (allenap)]

There was a failure on 2009-09-25, and mthaddon noticed that the slave was running an old version of the AMI with an outdated/incorrect disk layout. He restarted buildbot, and it's now is running the latest AMI (confirmed on 2009-09-28). I'm hopeful (though I don't know enough to be confident or not) that this bug will go away.

[Gavin Panella (allenap)]

Landed (a while back) a branch to disable PostgreSQL statement logging in utilities/launchpad-database-setup. I, or someone, needs to look through the build logs to see if this has made a difference.

[Robert Collins (lifeless)]

No longer using slaves.