On Wed, Apr 22, 2020 at 3:50 PM Yasuhito FUTATSUKI <futatuki_at_poem.co.jp> wrote:
> On 2020/04/22 22:18, Nathan Hartman wrote:
> > I'd like to add something along these lines to the Release Notes,
> > under "Known Issues in the Release."
> > Please check for accuracy:
> > (I haven't tested this myself -- haven't reached this point yet in my
> > Windows setup!)
> > [[[
> > When using Python 3.6 or higher on Windows, the test suite fails to
> > run because of changes in Python's implementation of console I/O.
> > Several workarounds are available:
> > Either:
> > * Use Python 2.7, or Python 3.5 or below, or
> > * Run the test suite with the --log-to-stdout command line argument,
> > or
> > * Set the PYTHONLEGACYWINDOWSSTDIO environment variable before running
> > the test suite, or
> > * Apply r1876707 and r[insert number here] and run the test suite.
> r1876707 isn't fix for console I/O issue, it is fix for another
> problem in the testsuite to run it on Windows with Python 3.
> Also, there are still 65 of failure in test on Windows with
> Python 3.
Indeed. Actually 68 test failures if none of your post-1.14.0-rc2
patches are applied.
There is also a problem running gen-make.py with Python 3, when
configuring for a Windows build in Debug configuration (I didn't
notice that earlier on because I always build a Release
configuration). I'll post about that separately.
> ... and what is worse, at least
> > FAIL: merge_tests.py 34: conflict markers should match the file's eol style
> this one seems to be broken even with Python 2.7, on Windows.
> (I'll post about it later).
That's strange. It does succeed on my system when running with Python
2.7.17. I had "All successful" test runs for [fsfs] x [ra_local,
Received on 2020-04-22 16:04:20 CEST