On 17.11.2019 14:39, Daniel Shahaf wrote:
> Nathan Hartman wrote on Sun, Nov 17, 2019 at 00:16:56 -0500:
>> (but all the recent failures are for the same reason):
>>> Updating '.':
>>> svn: E170013: Unable to connect to a repository at URL '
>>> svn: E120108: Error running context: The server unexpectedly closed the
>> What's with all these failures lately?
> Ask Infra to check the server's error log? They'll want to know the timestamp,
> the IP of the host the build ran on (if we have it;
It's 220.127.116.11. Or at least, that's the SNAT-ed address.
> otherwise, the buildbot
> builder's name, whence they can presumably work out the IP via the buildmaster),
> and that the error was from svn-master.a.o (as opposed to a mirror).
I'm assuming that some maintenance is happening on the master repository
at the same time and access is temporarily disabled. These failures only
seem to be happening on the configurations that run once a day, not
>> Or should it be svn-master but with https?
> That can't hurt.
Unless the OpenSSL on that machine (it's a rather old macOS) happens to
not trust the ASF server certs. I'd say, try it and we'll find out.
> You can change this yourself by editing
> (It'll get auto-deployed within five minutes of the commit. You can use
> «python -mpy_compile» to sanity check the diff before you commit it.)
Received on 2019-11-17 15:50:56 CET