[issue27829] test.regrtest: changed environment variables are not logged

2016-12-05 Thread STINNER Victor
Changes by STINNER Victor : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue27829] test.regrtest: changed environment variables are not logged

2016-09-23 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: > More warnings. Excellent result! > my flush=True changes may be removed if my latest change fixed the issue Don't bother. The buffering of standard streams was changed in 3.x and I'm not sure it always work as expected. For example the meaning of the -u o

[issue27829] test.regrtest: changed environment variables are not logged

2016-09-23 Thread STINNER Victor
STINNER Victor added the comment: More warnings. http://buildbot.python.org/all/builders/AMD64%20FreeBSD%209.x%203.x/builds/5058/steps/test/logs/stdio Warning -- threading._dangling was modified by test_logging Warning -- files was modified by test_io http://buildbot.python.org/all/builders/AM

[issue27829] test.regrtest: changed environment variables are not logged

2016-09-23 Thread STINNER Victor
STINNER Victor added the comment: Cool, my change fixed this issue. Examples: http://buildbot.python.org/all/builders/s390x%20RHEL%203.x/builds/1953/steps/test/logs/stdio Warning -- threading._dangling was modified by test_logging http://buildbot.python.org/all/builders/AMD64%20Windows7%20SP1%2

[issue27829] test.regrtest: changed environment variables are not logged

2016-09-23 Thread STINNER Victor
STINNER Victor added the comment: > I tried random changes since I was unable to reproduce the issue and didn't > understand why the the warning was not printed. Ooops, I forgot to say: my flush=True changes may be removed if my latest change fixed the issue (if the warning is now displayed).

[issue27829] test.regrtest: changed environment variables are not logged

2016-09-23 Thread STINNER Victor
STINNER Victor added the comment: > I thought sys.stderr is line buffered and doesn't need flush=True if prints a > complete line. I tried random changes since I was unable to reproduce the issue and didn't understand why the the warning was not printed. I'm not sure that stderr is always lin

[issue27829] test.regrtest: changed environment variables are not logged

2016-09-23 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: I thought sys.stderr is line buffered and doesn't need flush=True if prints a complete line. -- nosy: +serhiy.storchaka ___ Python tracker __

[issue27829] test.regrtest: changed environment variables are not logged

2016-09-23 Thread STINNER Victor
STINNER Victor added the comment: I was able to reproduce the missing warning by modifying test_sys.py to modify sys.path and then run: ./python -m test -W test_sys The -W eats stderr even if the environment changed. I modified regrtest to copy stderr if the test doesn't pass which includes: f

[issue27829] test.regrtest: changed environment variables are not logged

2016-09-23 Thread Roundup Robot
Roundup Robot added the comment: New changeset cbe049647a04 by Victor Stinner in branch '3.5': Issue #27829: regrtest -W displays stderr if env changed https://hg.python.org/cpython/rev/cbe049647a04 New changeset 12e3023d19bd by Victor Stinner in branch '3.6': Merge 3.5 (issue #27829) https://hg

[issue27829] test.regrtest: changed environment variables are not logged

2016-09-10 Thread Roundup Robot
Roundup Robot added the comment: New changeset 491bbba73bca by Victor Stinner in branch 'default': Show regrtest env changed warn on Windows buildbot https://hg.python.org/cpython/rev/491bbba73bca -- ___ Python tracker

[issue27829] test.regrtest: changed environment variables are not logged

2016-08-22 Thread Roundup Robot
Roundup Robot added the comment: New changeset 2e23f7b9515c by Victor Stinner in branch 'default': Issue #27829: libregrtest.save_env: flush stderr https://hg.python.org/cpython/rev/2e23f7b9515c -- nosy: +python-dev ___ Python tracker

[issue27829] test.regrtest: changed environment variables are not logged

2016-08-22 Thread STINNER Victor
New submission from STINNER Victor: It's common to get a random "env failed" issue when tests are run by buildbots, but changed environment variables are not logged, so the "env changed "information cannot be used to fix the issue :-/ Example: -- ... 0:07:32 [160/402] test_io f

[issue27829] test.regrtest: changed environment variables are not logged

2016-08-22 Thread STINNER Victor
Changes by STINNER Victor : -- keywords: +buildbot ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail