On Tue, Oct 2, 2018 at 5:37 PM Bert Huijben wrote:
> On Tue, Oct 2, 2018 at 4:30 PM Branko Čibej wrote:
>>
>> On 02.10.2018 02:38, Johan Corveleyn wrote:
>> > I haven't looked deeply into it yet, but it seems that the
>> > conflicts-tests (the C tests) are very slow when testing over
>> > svnserv
I'm happy to announce the release of Apache Subversion 1.11.0-rc2.
Please choose the mirror closest to you by visiting:
https://subversion.apache.org/download.cgi#pre-releases
SHA-512 checksums are available at:
https://www.apache.org/dist/subversion/subversion-1.11.0-rc2.tar.bz2.sha512
It resolves to both ::1 and 127.0.0.1 on Windows, and as (per RFC) ipv6 is
tried before ipv4... things timeout before trying the address used by
default (hardcoded) in svnserve.
(We used to default to ipv6 for some time... But we decided to explicitly
default to ipv4 when not passing the later adde
On 02.10.2018 02:38, Johan Corveleyn wrote:
> I haven't looked deeply into it yet, but it seems that the
> conflicts-tests (the C tests) are very slow when testing over
> svnserve. I noticed this while testing 1.11.0-rc2, but I see the same
> with trunk and with 1.10.x.
>
> Running the entire confl
Johan Corveleyn wrote on Tue, 02 Oct 2018 02:38 +0200:
> Running the entire conflicts-test.exe (on a ramdisk):
Running «make {check,davautocheck,svnserveautocheck}
TESTS=subversion/tests/…/conflicts-test APACHE_MPM=event» with the build tree
in a ramdisk, I get (average of three runs in each case)
This could be related to log requests that are not somehow limited (by last
rev and/or number of results). ra_serf and ar_local allow cancelling
halfway through, while ra_svn doesn't.
(No time to investigate this myself righ now)
Bert
On Tue, Oct 2, 2018 at 2:38 AM Johan Corveleyn wrote:
> I ha
6 matches
Mail list logo
