Re: svn commit: r1868561 - /subversion/trunk/subversion/tests/cmdline/diff_tests.py

On Fri, Oct 18, 2019 at 12:37 AM Daniel Shahaf wrote: > Nathan Hartman wrote on Fri, Oct 18, 2019 at 00:08:48 -0400: > > On Thu, Oct 17, 2019 at 5:48 PM Daniel Shahaf > > wrote: > > > > > Good morning Nathan, > > > > > > > Good morning! Or whatever time it happens to be in your part of the

Re: svn commit: r1868561 - /subversion/trunk/subversion/tests/cmdline/diff_tests.py

Nathan Hartman wrote on Fri, Oct 18, 2019 at 00:08:48 -0400: > On Thu, Oct 17, 2019 at 5:48 PM Daniel Shahaf > wrote: > > > Good morning Nathan, > > > > Good morning! Or whatever time it happens to be in your part of the world > :-) , fifth sense. >

Re: Test failures with Python 3 (Re: PMCs: any Hackathon requests? (deadline 11 October))

Yasuhito FUTATSUKI wrote on Thu, 17 Oct 2019 22:57 +00:00: > I'm sorry, I missed to answer to these questions. > > On 2019/10/16 16:55, Daniel Shahaf wrote: > > Good catch. Yes, we should update INSTALL to reflect that Python 3 is > > supported for the build and test process, even if it's not

Re: svn commit: r1868561 - /subversion/trunk/subversion/tests/cmdline/diff_tests.py

On Thu, Oct 17, 2019 at 5:48 PM Daniel Shahaf wrote: > Good morning Nathan, > Good morning! Or whatever time it happens to be in your part of the world :-) If instead of using «echo test > file» you would use the existing file > 'iota' > (see subversion/tests/README), you'd be able to pass

Re: Issue tracker housecleaning: SVN-1722

On 17.10.2019 23:46, Branko Čibej wrote: > On 17.10.2019 23:01, Daniel Shahaf wrote: >> Branko Čibej wrote on Thu, Oct 17, 2019 at 22:56:29 +0200: >>> On 17.10.2019 22:37, Daniel Shahaf wrote: Branko Čibej wrote on Thu, 17 Oct 2019 06:49 +00:00: > On 16.10.2019 10:01, Daniel Shahaf wrote:

Re: Test failures with Python 3 (Re: PMCs: any Hackathon requests? (deadline 11 October))

I'm sorry, I missed to answer to these questions. On 2019/10/16 16:55, Daniel Shahaf wrote: Good catch. Yes, we should update INSTALL to reflect that Python 3 is supported for the build and test process, even if it's not yet supported by the swig bindings in trunk and 1.13.x. Would you be

Re: svn commit: r1868561 - /subversion/trunk/subversion/tests/cmdline/diff_tests.py

Good morning Nathan, hartmannat...@apache.org wrote on Thu, Oct 17, 2019 at 16:23:21 -: > +++ subversion/trunk/subversion/tests/cmdline/diff_tests.py Thu Oct 17 > 16:23:21 2019 > @@ -5253,6 +5253,83 @@ def diff_git_format_copy(sbox): > +def diff_nonexistent_in_wc(sbox): > + "nonexistent in

Re: Issue tracker housecleaning: SVN-1722

On 17.10.2019 23:01, Daniel Shahaf wrote: > Branko Čibej wrote on Thu, Oct 17, 2019 at 22:56:29 +0200: >> On 17.10.2019 22:37, Daniel Shahaf wrote: >>> Branko Čibej wrote on Thu, 17 Oct 2019 06:49 +00:00: On 16.10.2019 10:01, Daniel Shahaf wrote: > Which reminds me: it'd be nice to set up

Re: Issue tracker housecleaning: SVN-1722

Branko Čibej wrote on Thu, Oct 17, 2019 at 22:56:29 +0200: > On 17.10.2019 22:37, Daniel Shahaf wrote: > > Branko Čibej wrote on Thu, 17 Oct 2019 06:49 +00:00: > >> On 16.10.2019 10:01, Daniel Shahaf wrote: > >>> Which reminds me: it'd be nice to set up a buildbot to run the build and > >>> test

Re: Issue tracker housecleaning: SVN-1722

On 17.10.2019 22:37, Daniel Shahaf wrote: > Branko Čibej wrote on Thu, 17 Oct 2019 06:49 +00:00: >> On 16.10.2019 10:01, Daniel Shahaf wrote: >>> Which reminds me: it'd be nice to set up a buildbot to run the build and >>> test process under Python 3. Any committer can edit the buildbot >>>

Re: Issue tracker housecleaning: SVN-1722

Branko Čibej wrote on Thu, 17 Oct 2019 06:49 +00:00: > On 16.10.2019 10:01, Daniel Shahaf wrote: > > Which reminds me: it'd be nice to set up a buildbot to run the build and > > test process under Python 3. Any committer can edit the buildbot > > scripts[1], but the question is which of the

Re: Issue tracker housecleaning: SVN-1722

On Thu, Oct 17, 2019 at 3:03 PM Nathan Hartman wrote: > On Thu, Oct 17, 2019 at 2:30 PM Julian Foad wrote: > > Close buttons are at top of page when logged in. > > Nope. I am logged in. I have a feeling my account isn't setup > correctly with permissions. I might have to bother infra... :-(

Re: Issue tracker housecleaning: SVN-1722

Close buttons are at top of page when logged in.

Re: Issue tracker housecleaning: SVN-1722

On Thu, Oct 17, 2019 at 11:44 AM Julian Foad wrote: > Looks good to me. Thanks! Regression test added in r1868561. Now, here's a dumb question... How do I close the issue?! There doesn't seem to be a button for it.

Re: Issue tracker housecleaning: SVN-1722

Nathan Hartman wrote: Test below. Please review... Looks good to me. - Julian

Re: Cross compiling build instructions

On Tue, Oct 15, 2019 at 4:00 PM Robert Dailey wrote: > I am trying to cross-compile the subversion library for Android using > the Android NDK. Hello Robert, Were you successful in getting the SVN client library to build? Thanks Nathan

Re: Issue tracker housecleaning: SVN-1722

Test below. Please review... On Thu, Oct 17, 2019 at 8:18 AM Branko Čibej wrote: > >> Is it possible, through some incantation that I've overlooked, to run > >> the cmdline tests against an arbitrary svn binary? > make check SVN_BIN_DIR=/opt/foo/some/path > > See Makefile.in, line 617. Btw,

Run tests against an arbitrary installed svn

It would be good if we could run the test suite against an arbitrary installed set of Subversion binaries and libraries. We have this for a starting point: make check SVN_BIN_DIR=/opt/foo/some/path For the Python tests, it mostly uses the given path for loading 'svn*' executables. In a few

Re: Issue tracker housecleaning: SVN-1722

On Thu, Oct 17, 2019 at 8:18 AM Branko Čibej wrote: > On 17.10.2019 13:55, Julian Foad wrote: > >> Is it possible, through some incantation that I've overlooked, to run > >> the cmdline tests against an arbitrary svn binary? > > > > Unfortunately that's something we never got around to. I would

Re: Issue tracker housecleaning: SVN-1722

On 17.10.2019 13:55, Julian Foad wrote: >> Is it possible, through some incantation that I've overlooked, to run >> the cmdline tests against an arbitrary svn binary? > > Unfortunately that's something we never got around to.  I would love > to make that possible. ??? make check

Re: Issue tracker housecleaning: SVN-1722

On Wed, Oct 16, 2019 at 4:46 AM Julian Foad wrote: > Of course, ideally, it is lovely to improve the test coverage, if you > have spare time and spare enthusiasm, or can do so really quickly so it > doesn't impact other activities. However, it's not required and not > necessarily worth it. A

Re: Adding Apache Subversion to the hackCBS 2.0 task list

Excellent --thank you for the confirmation and best of luck with the event. Go Apache! - - - Vice President Marketing & Publicity Vice President Sponsor Relations The Apache Software Foundation Tel +1 617 921 8656 | s...@apache.org On Thu, Oct 17, 2019, at 01:30, Rohan Vij wrote: > Hi Sally

Re: Issue tracker housecleaning: SVN-1722

On 16.10.2019 10:01, Daniel Shahaf wrote: > Which reminds me: it'd be nice to set up a buildbot to run the build and > test process under Python 3. Any committer can edit the buildbot > scripts[1], but the question is which of the buildbot slaves has Python 3 > installed?