On 06/03/2010 06:16 PM, Wouter Verhelst wrote:
> On Thu, Jun 03, 2010 at 10:30:22AM -0400, Daniel Kahn Gillmor wrote:
>> Unfortunately, the latest version of xdotool (2.20100602.2915, which has
>> a substantially overhauled test suite geared to address these concerns)
>> *also* FTBFS on the buildd network:
>>
>>>>  
>>>> https://buildd.debian.org/fetch.cgi?pkg=xdotool&arch=amd64&ver=1%3A2.20100602.2915-1&stamp=1275566388&file=log
>>>>  
>>>> https://buildd.debian.org/fetch.cgi?pkg=xdotool&arch=ia64&ver=1%3A2.20100602.2915-1&stamp=1275566969&file=log
>>>>  
>>>> https://buildd.debian.org/fetch.cgi?pkg=xdotool&arch=powerpc&ver=1%3A2.20100602.2915-1&stamp=1275568171&file=log
>>
>> However, the same package builds fine for me in both:
>>
>>  * an up-to-date amd64 sid cowbuilder environment, and
>>  * on an i386 workstation running mostly testing with some packages from sid
>>
>> Any assistance in sorting out the cause of these FTBFS would be welcome.
>>  Where should i look?
> 
> Those build logs don't really reveal anything to me; it doesn't look
> like it's a known issue. It does say something about "pkill: not found,"
> which could point to a missing build-dep, but as that happens upon
> trying to finalize a test from the test suite that has failed, I guess
> that's not the actual problem.
> 
> If you don't manage to find the issue, I might be able to get you a
> build directory. I would hope

I haven't been able to find the issue yet (i agree that the pkill
business is a missing build-dep to handle the corner case where the
tests fail, but i don't think it's the cause of the failure itself).

And the build still works fine for me in my own up-to-date sid
cowbuilder amd64 instance.

I suspect there are some resource limits on the buildd's that i don't
have replicated, but i'm not sure how to track down what the problem is
specifically.

Wouter, you seem to be offering assistance in getting access to a build
directory (meaning to a live buildd itself?  or something else?)  -- can
i take you up on that?  I'm not sure what my next steps should be otherwise.

        --dkg

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to