Re: svn commit: r1743556 - /subversion/trunk/build/run_tests.py
On 13.05.2016 00:00, Evgeny Kotkov wrote:
> Stefan Fuhrmann <stefan2_at_apache.org> writes:
>> TestHarness._run_test): The log is binary data, so write byte strings
>> to it.
>> if self.opts.list_tests:
>> - log.write('LISTING: %s\n' % progbase)
>> + log.write(('LISTING: %s\n' % progbase).encode())
>> - log.write('START: %s\n' % progbase)
>> + log.write(('START: %s\n' % progbase).encode())
> Hm, do these log.write() calls always expect bytes? I see that `log'
> can be set to two different values, as per run_tests.py:880:
> if self.log:
> log = self.log
> log = sys.stdout # with --log-to-stdout
> And sys.stdout.write() works with strings, so this probably won't work
> if tests are run with the --log-to-stdout option.
That looks like a win-tests.py -only feature,
although run_tests.py has remnants of that.
If not, I'd have to add a wrapper around stdout.
Feel free to make the tests run on Windows
with Python 3. I for sure won't do anything
along those lines.
Received on 2016-05-13 05:00:51 CEST
This is an archived mail posted to the Subversion Dev