Open stanislavlevin opened 2 years ago
I have more test failures for that reason:
FAILED tests/test_benchmark.py::test_groups - Failed: nomatch: '*collected 5 items'
FAILED tests/test_benchmark.py::test_group_by_func - Failed: fnmatch: '*'
FAILED tests/test_benchmark.py::test_group_by_fullfunc - Failed: fnmatch: '*'
FAILED tests/test_benchmark.py::test_group_by_param_all - Failed: fnmatch: '*'
FAILED tests/test_benchmark.py::test_group_by_param_select - Failed: fnmatch: '*'
FAILED tests/test_benchmark.py::test_group_by_param_select_multiple - Failed: fnmatch: '*'
FAILED tests/test_benchmark.py::test_group_by_fullname - Failed: matched: "* benchmark 'test_x.py::test_a[[]0[]]': 1 tests *"
FAILED tests/test_benchmark.py::test_only_override_skip - Failed: nomatch: '*collected 2 items'
FAILED tests/test_benchmark.py::test_fixtures_also_skipped - Failed: nomatch: '*collected 2 items'
FAILED tests/test_benchmark.py::test_max_time_min_rounds - Failed: nomatch: '*collected 3 items'
FAILED tests/test_benchmark.py::test_max_time - Failed: nomatch: '*collected 3 items'
FAILED tests/test_benchmark.py::test_disable_gc - Failed: nomatch: '*collected 2 items'
FAILED tests/test_benchmark.py::test_custom_timer - Failed: nomatch: '*collected 2 items'
FAILED tests/test_benchmark.py::test_sort_by_mean - Failed: nomatch: '*collected 2 items'
FAILED tests/test_benchmark.py::test_basic - Failed: nomatch: '*collected 5 items'
FAILED tests/test_benchmark.py::test_skip - Failed: nomatch: '*collected 5 items'
FAILED tests/test_benchmark.py::test_disable - Failed: nomatch: '*collected 5 items'
FAILED tests/test_benchmark.py::test_mark_selection - Failed: nomatch: '*collected 5 items*'
FAILED tests/test_benchmark.py::test_only_benchmarks - Failed: nomatch: '*collected 5 items'
With Pytest 7 benchmark tests fail:
failure report for one test:
The actual order of reported passed tests differs from the expected one. This is due to pytest-dev/pytest#5196: Tests are now ordered by definition order in more cases.
I think there is no point to check the behavior of duplicated tests functions and I can only assume that originally this was a typo. In my opinion - there are 2 solutions - removal of the first duplicated
test_fast
function or renaming it and syncing all affected tests' assumptions.See also https://github.com/pytest-dev/pytest/issues/9724