On 18.10.2019 01:39, Branko Čibej wrote:
> 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:
>>>>>>> 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?
>>>>>> https://ci.apache.org/builders/svn-x64-macosx-local-python3
>>>>>>
>>>>>> Been there, done that, bought the DVD.
>>>>> Why are svnadmin_tests 69 and tree_conflict_tests 26 passing on that
>>>>> bot? They (currently) fail under python3.
>>>> I don't know. It's possible, I suppose, that the activation of the
>>>> python3 virtual environment has no effect on the test driver. It might
>>>> not be a bad idea to have the tests print the Python version in the
>>>> summary and possibly in the log of every test case.
>>> What's the value of $(PYTHON) in Makefile? That's what the «check» target uses.
>> Yep, apparently that's the bug ... I'm testing script changes now, along
>> with r1868566 for good measure.
> I've set up this:
> https://ci.apache.org/builders/svn-x64-macosx-local-python3-swig
>
> It will build and test the core libraries and swig-py bindings with
> Python 3 on the swig-py3 branch.
>
> I hope ... build #0 running as we speak.
Running the build scripts and tests with Python3 works now on trunk,
with the latest fixes. Except for this warning:
.../run_tests.py:53: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses
import optparse, subprocess, imp, threading, traceback
I know we make 'imp' vs. 'importlib' choices elsewhere in the code, we
probably just missed a case here.
-- Brane
Received on 2019-10-18 15:21:59 CEST