On Mon, Feb 17, 2020 at 2:40 PM Ruediger Pluem <rpl...@apache.org> wrote: > > > > On 02/17/2020 05:31 PM, Joe Orton wrote: > > On Mon, Feb 17, 2020 at 10:52:10AM -0500, Eric Covener wrote: > >> On Mon, Feb 17, 2020 at 10:44 AM Joe Orton <jor...@redhat.com> wrote: > >>> > >>> On Mon, Feb 17, 2020 at 04:30:40PM +0100, Stefan Eissing wrote: > >>>> Does this look like a Travis problem? Just red on some "Linux Ubuntu" > >>>> combinations, but I do not really see the cause. > >>> > >>> Yep, it's a timeout doing the "svn checkout" because the test suite was > >>> updated, you can ignore. > >> > >> Could we point travis at GitHub for that? > > > > The Perl framework isn't mirrored to GitHub at the moment so we have to > > get it from SVN. We could: > > > > a) ask infra to mirror httpd/test/framework to some new github repo name > > (httpd-test-framework? httpd-perl-tests? httpd-tests?) > > > > b) move httpd/test/framework under trunk/test/framework or something > > > > c) work out the underlying issue which makes Travis/SVN fail, my > > assuption is that since a Travis build will hit SVN with 30+ > > near-simultaneous new connections which looks a bit DoS-like so it > > gets rate-limited/banned by the ASF infra somehow, but it's a guess > > > > I have a vague preference for (b) since it would be nice to be able to > > commit tests and code at the same time but it'd be quite a big change. > > (a) might be easier > > > > I am +1 on a) and +0 on b). Regarding c) I guess we need to discuss with > infra if your assumption is true. > OTOH I guess once we have a) or b) in place c) becomes academic :-).
There is also the complicating factor of the svn:external for https://svn.apache.org/repos/asf/perl/Apache-Test/trunk
