Re: daily pestering about s390 and sparc buildd failure
Ingo Juergensmann <ij@2004.bluespice.org> writes:
> Testing/debugging per frequent uploads via the buildds would mean that the
> project doesn't need any developer accessible means and all debugging can be
> done via uploading packages and reading buildd logs.
Except that "testing by frequent uploads" was not what I did. I had a
problem which I had already determined did not happen in normal builds
on my machine or the failing systems, and did not happen inside
pbuilder on my machine.
> (and when there's a problem with sbuild you can download sbuild (as well
> buildd) and start debug on your own machine. [...]
Well, I used pbuilder at Blars Blarson's suggestion. But of course I
did this first; I did not simply "test by frequent uploads". I made
only one test upload, and it did not in fact impact the overloaded
buildds at all.
And, I took that step only when I was convinced that the problem
didn't happen on my machines (ppc and i386) at all, in any build
environment. (I was correct about this, btw.)
Thomas
Reply to: