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

On 2019-10-12 07:47, Daniel Shahaf wrote: Yasuhito FUTATSUKI wrote on Sat, Oct 12, 2019 at 05:31:53 +0900: Yes, it will fix local_missing_dir_endless_loop() itself correctly. But the stack trace before fix indicate there is at least one problem in svntest.verify.compare_and_display_lines().

Re: PMCs: any Hackathon requests? (deadline 11 October)

Nathan Hartman wrote on Fri, Oct 11, 2019 at 12:53:23 -0400: > (2) Once this is more-or-less under control, I'd like to start actively > looking for volunteers, hackathon events, and any other opportunities > to get more involvement. This might be easier to do on an ASF-wide scale. comdev¹ would

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

Nathan Hartman wrote on Fri, Oct 11, 2019 at 16:50:39 -0400: > On Fri, Oct 11, 2019 at 4:32 PM Yasuhito FUTATSUKI > wrote: > > This is caused by mixing bytes object drived from file contents and str > > object to construct log message. > > Does something like this answer help: > >

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

Yasuhito FUTATSUKI wrote on Sat, Oct 12, 2019 at 05:31:53 +0900: > Yes, it will fix local_missing_dir_endless_loop() itself correctly. > But the stack trace before fix indicate there is at least one problem > in svntest.verify.compare_and_display_lines(). > > Assume the file contents is broken

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

On Fri, Oct 11, 2019 at 4:32 PM Yasuhito FUTATSUKI wrote: > This is caused by mixing bytes object drived from file contents and str > object to construct log message. Does something like this answer help:

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

On 2019-10-12 02:56, Daniel Shahaf wrote: Yasuhito FUTATSUKI wrote on Fri, Oct 11, 2019 at 16:35:19 +0900: The latter also can be fixed by fix_tree_conflict_tests_patch.txt at least so that the test can be passed on Python 3. However, from above stack trace, I think it is incomplete because

Re: Subversion semantics: no no-op changes

Julian Foad wrote on Fri, Oct 11, 2019 at 15:56:31 +0100: > Hello Eric. Not to preëmpt Eric, but may I share my thoughts too? > In conclusion, I consider svn would be a better system -- more predictable, > testable, composable, etc.; more generally dependable -- and would lose no > significant

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

Yasuhito FUTATSUKI wrote on Fri, Oct 11, 2019 at 16:35:19 +0900: > On 2019-10-11 06:45, Daniel Shahaf wrote: > ... > > From autogen.sh to 'make check', all steps pass with > > PYTHON=/usr/bin/python3. > > There were two failures in 1.11 on tests. > >

Re: PMCs: any Hackathon requests? (deadline 11 October)

On Fri, Oct 11, 2019 at 11:45 AM Julian Foad wrote: > Daniel Shahaf wrote: > > Julian, do you have any release.py tasks to suggest? > > There are certainly some things need doing in release.py. Unfortunately I didn't hear back in time to put that on the list for this hackathon. If the event

Re: PMCs: any Hackathon requests? (deadline 11 October)

Daniel Shahaf wrote: Julian, do you have any release.py tasks to suggest? There are certainly some things need doing in release.py. One thing I've taken from this discussion is there are sometimes potential contributors coming along who might take a well defined and contained task, so it's

Re: Remove From Mailing List

Gillead, Gennar wrote: Please remove my email from all mailing list. I sent a request; I think you will have to reply to a confirmation. Anyone can unsubscribe themself from this list by sending any (e.g. blank) email to: And the equivalent

Subversion semantics: no no-op changes

Hello Eric. TL;DR: I explain why I am convinced no-op changes don't belong in the Subversion versioning semantics. With your work on Subversion repository and dump stream semantics, is this something you can offer a view on? I have previously failed to convince the developer community [1].

Re: Python3 work [was: The run up to Subversion 1.13.0]

On 2019-09-30 06:32, Johan Corveleyn wrote: ... At this point, I think the only thing blocking reintegration of this branch into trunk seems to be the C4115 warning / error. As I said, I have no informed opinion either way (and Brane was okay with turning it into a warning). So if Bert doesn't

Remove From Mailing List

Please remove my email from all mailing list. gennar.gill...@teradata.com gg123...@teradata.com Thanks and Best Regards, Gennar Gillead Americas Platform Engineering Practice Teradata Consulting 678-485-8757 Upcoming OOO Dates:

Re: Creating directory copy operations in a dump stream

Johan Corveleyn : > - Just guessing here, but perhaps the problem with your test is that > your working copy is "mixed-revision" after you added the three files. > I.e. the 'trunk' directory is a revision behind, after you added the > three files. See if it makes a difference if you do "svn up

Re: Adding Apache Subversion to the hackCBS 2.0 task list

Rohan, We have Apache OFBiz, Ignite, and now SVN providing a list of tasks for the hackathon. Each Apache Project has detailed what their requirements are, which has been forwarded to you. I don't know how the event organizers are grouping the development themes/activities: we are

Re: Creating directory copy operations in a dump stream

On Fri, Oct 11, 2019 at 11:41 AM Eric S. Raymond wrote: > > After years of eyeballing Subversion dump streams as part of making > reposurgeon work, I have belatedly realized there is a dump stream > operation I don't know how to generate with the CLI. And I need to > to get good test load

Creating directory copy operations in a dump stream

After years of eyeballing Subversion dump streams as part of making reposurgeon work, I have belatedly realized there is a dump stream operation I don't know how to generate with the CLI. And I need to to get good test load coverage. If, in a normally-set up Subversion repository, I create and

Adding Apache Subversion to the hackCBS 2.0 task list

Thank you, Nathan. I'm copying Rohan Vij from hackCBS 2.0 here so he can follow up with you directly. @Rohan --kindly advise next steps. Best regards, Sally - - - Vice President Marketing & Publicity Vice President Sponsor Relations The Apache Software Foundation Tel +1 617 921 8656 |

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

On 2019-10-11 06:45, Daniel Shahaf wrote: ... From autogen.sh to 'make check', all steps pass with PYTHON=/usr/bin/python3. There were two failures in 1.11 on tests.