On Mon, Mar 28, 2016 at 10:53 PM, Andrea Pescetti <pesce...@apache.org> wrote:
> On 01/02/2016 j.nitschke wrote:
>>
>> But a global haltOnFailure would stop the build at 'svn info' step.
>> About the 'svn info' step, this one stopped working ...
>
>
> And we are back here, it seems. With the HTTPS fixes now in place, all the
> Linux and FreeBSD buildbots completed their build successfully, while the
> Windows one ran build --all but then suddenly stopped almost at the end,
> after delivering sc
>
> https://ci.apache.org/builders/aoo-win7/builds/231/steps/build.pl%20--all/logs/stdio
> command timed out: 20000 seconds without output, killing pid 13888
>
> and today it stopped at a very early stage that you had already fixed, the
> "svn info":
>
> https://ci.apache.org/builders/aoo-win7/builds/232/steps/svn%20export/logs/stdio
> Inappropriate ioctl for device
>
> Jochen, Damjan, do you remember how you fixed it back at the time? Or was it
> handled in the chat session with pono Damjan mentions later in this thread
> (which would basically mean that it disappeared magically after a restart
> and some magic by Infra)?

No, the build hanging problem was never fixed. It started
mysteriously, and since I never got access to the Windows build bots
despite asking infra for months and even offering to volunteer, I have
no idea what's wrong or any way to debug it or any other build bot
problem. My own Windows box builds AOO perfectly and always has.

Regards
Damjan

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Reply via email to