You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using python 2.7.10, pytest 2.8.0 and pytest-xdist 1.13.1.
Testcase:
import pytest, time
@pytest.mark.parametrize('i', list(range(100)))
def test_x(i):
print(i)
time.sleep(i/300.0)
assert i != 42
Run with pytest -n 8 --junit-xml=junit.xml.
The output on the command line looks fine, showing the test_x[42] failure.
But look at the resulting junit.xml file: the failure appears in the wrong <testcase> node:
pytest_runtest_logreport must be careful to not depend on setup/call/teardown
being called sequentially in that order, as xdist will call them as they are reported
from the slaves
Fixpytest-dev#1064
Using python 2.7.10, pytest 2.8.0 and pytest-xdist 1.13.1.
Testcase:
Run with
pytest -n 8 --junit-xml=junit.xml
.The output on the command line looks fine, showing the
test_x[42]
failure.But look at the resulting
junit.xml
file: the failure appears in the wrong<testcase>
node:This causes test failures to be listed incorrectly in our Jenkins CI.
The other
<system-out>
nodes also appear in the wrong<testcase>
nodes.The bug disappears when downgrading pytest to 2.7.3.
The text was updated successfully, but these errors were encountered: