Open asottile opened 5 years ago
Can still reproduce. I'll try to have a PR up for this soon
Issue comes down to --runxfail
not taking precedent over empty_parameter_set_mark=xfail
. If we make runxfail
take precedent, the issue will go away.
Below is how pytest
has interpreted the mark in the original issue report
pip install -e ../ && python3 -m pytest --runxfail test_change.py
ValueError: Mark(name='skip', args=(), kwargs={'reason': "got empty parameter set ('a', 'b'), function test at /home/gnikonorov/pytest/gleb_test/test_change.py:2"})
pip install -e ../ && python3 -m pytest --runxfail -o empty_parameter_set_mark=xfail test_change.py
ValueError: Mark(name='xfail', args=(), kwargs={'run': False, 'reason': "got empty parameter set ('a', 'b'), function test at /home/gnikonorov/pytest/gleb_test/test_change.py:2"})
This started as a "hmm... that's weird" and ended at a crash. go figure.
This is super low priority and more of a result of "pytest has sooo many options!"
Today I learned that this generates a single test which is always skipped
But with a certain set of arguments: