You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@subversion.apache.org by bu...@apache.org on 2019/11/17 00:32:16 UTC

buildbot failure in on svn-x64-macosx-apr2.0-dev

The Buildbot has detected a new failure on builder svn-x64-macosx-apr2.0-dev while building . Full details are available at:
    https://ci.apache.org/builders/svn-x64-macosx-apr2.0-dev/builds/2871

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: svn-x64-macosx-dgvrs

Build Reason: The Nightly scheduler named 'subversion-trunk-nightly' triggered this build
Build Source Stamp: [branch subversion/trunk] 1869888
Blamelist: julianfoad

BUILD FAILED: failed

Sincerely,
 -The Buildbot

Re: Fwd: buildbot failure in on svn-x64-macosx-apr2.0-dev

Posted by Branko Čibej <br...@apache.org>.
On 17.11.2019 14:39, Daniel Shahaf wrote:
> Nathan Hartman wrote on Sun, Nov 17, 2019 at 00:16:56 -0500:
>> From
>> https://ci.apache.org/builders/svn-x64-macosx-apr2.0-dev/builds/2871/steps/svn/logs/stdio
>> (but all the recent failures are for the same reason):
>>
>>> Updating '.':
>>> svn: E170013: Unable to connect to a repository at URL '
>> http://svn-master.apache.org/repos/asf/subversion/trunk'
>>> svn: E120108: Error running context: The server unexpectedly closed the
>> connection.
>>
>> 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 77.234.149.122. 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
per-commit.

[...]


>> 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
> <https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/subversion.conf>.
> (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.)

+1

-- Brane

Re: Fwd: buildbot failure in on svn-x64-macosx-apr2.0-dev

Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Nathan Hartman wrote on Sun, Nov 17, 2019 at 00:16:56 -0500:
> From
> https://ci.apache.org/builders/svn-x64-macosx-apr2.0-dev/builds/2871/steps/svn/logs/stdio
> (but all the recent failures are for the same reason):
> 
> > Updating '.':
> > svn: E170013: Unable to connect to a repository at URL '
> http://svn-master.apache.org/repos/asf/subversion/trunk'
> > svn: E120108: Error running context: The server unexpectedly closed the
> connection.
> 
> 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; 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).

> Is there a reason the buildbot needs to use
>     http://svn-master.a.o
> as opposed to
>     https://svn.a.o
> ?

Yes.  "svn.apache.org" has several mirrors, using the DAV proxy feature.  The
scenario behind this is:

- Some other Apache project commits a 3000-file javadoc update in rN

- We commit something in rN+1

- The buildbot slave updates to rN+1 before rN finishes svnsync'ing over to the
  svn.a.o mirror used by that buildbot slave

If the buildbot slaves used https://svn.a.o, they'd get the "Revision does not
exist" error when they tried to update/checkout their working copies.  Therefore,
they get their working copies from the master (behind the DAV proxy) directly.

This is ultimately because /repos/asf is a single repository, svnsync is sequential,
and the DAV proxy abstraction gives "Revision does not exist" for revisions that haven't
been svnsynced from the master.

> Or should it be svn-master but with https?

That can't hurt.  You can change this yourself by editing
<https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/subversion.conf>.
(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.)

Cheers,

Daniel

Fwd: buildbot failure in on svn-x64-macosx-apr2.0-dev

Posted by Nathan Hartman <ha...@gmail.com>.
From
https://ci.apache.org/builders/svn-x64-macosx-apr2.0-dev/builds/2871/steps/svn/logs/stdio
(but all the recent failures are for the same reason):

> Updating '.':
> svn: E170013: Unable to connect to a repository at URL '
http://svn-master.apache.org/repos/asf/subversion/trunk'
> svn: E120108: Error running context: The server unexpectedly closed the
connection.

What's with all these failures lately?

Is there a reason the buildbot needs to use
    http://svn-master.a.o
as opposed to
    https://svn.a.o
?

Or should it be svn-master but with https?

Nathan