[buildd-tools-devel] Bug#566321: Bug#566321: buildd: Does not give a clue what's wrong when something is up with sbuild.

[Kurt Roeckx]

On Sat, Jan 23, 2010 at 12:25:22PM +0000, Roger Leigh wrote:
> On Fri, Jan 22, 2010 at 11:00:56PM +0100, Kurt Roeckx wrote:
> > When sbuild returns an error message, I can never find that
> > error message and need to run sbuild manually to find out
> > what is wrong.
> 
> Could you provide a bit more detail, such as which type of
> error sbuild gives?  Are we talking about errors during a
> build, when initially starting up, when fetching sources?

So I just had an example of this.  When run manually, I get:
W: No chroots are defined in '/etc/schroot/schroot.conf'
W: The specified chroots are not defined in '/etc/schroot/schroot.conf'
Chroot for distribution unstable, architecture powerpc not found

> Are the errors reported in the package build log, or in
> the main log (build-xxx)?

The daemon.log file shows:
Jan 31 11:20:15 buildd[2205]: sbuild failed with status 255/0
Jan 31 11:20:15 buildd[2205]: Assuming all packages unbuilt and adding to REDO:
Jan 31 11:20:15 buildd[2205]: package_version
Jan 31 11:20:15 buildd[2205]: sbuild now failed 21 times in a row; going to sleep

And the build/ dir contains a bunch of 0 length log files, there
is no log file for the package itself.

Without manually running sbuild, I have no clue what is going on.


Kurt