74a103d655
On some systems (tested with official Debian Buster-based Python 3.6 docker image), setting the LC_ALL environment variable to en_US.UTF-8 will trigger Python into switching its preferred encoding to ASCII. If any python process tries to read a non-ASCII file in this scenario, it will terminate with an error. And this is exactly what happens to pytest when it tries to load its configuration that ansible-test supplies because the configuration contains an em dash. In order to bypass this issue, we replaced the em dash with a regular dash and things started working again. An alternative solution would be to replace the en_US.UTF-8 locale with something safer, but unfortunately, the en_US.UTF-8 is probably as safe as it gets.
9 lines
370 B
INI
9 lines
370 B
INI
[pytest]
|
|
xfail_strict = true
|
|
mock_use_standalone_module = true
|
|
# It was decided to stick with "legacy" (aka "xunit1") for now.
|
|
# Currently used pytest versions all support xunit2 format too.
|
|
# Except the one used under Python 2.6 - it doesn't process this option
|
|
# at all. Ref:
|
|
# https://github.com/ansible/ansible/pull/66445#discussion_r372530176
|
|
junit_family = xunit1
|