Closed tswast closed 10 months ago
It might just be that my Python 3.11 environment was the one that had a conflict with the root configs.py
file, but I also add some tests for Python 3.11 in my PR: https://github.com/str0zzapreti/pytest-retry/pull/18
We have the same issue, our CI pipelines using pytest-retry (e.g. https://github.com/emqx/emqx/actions/runs/5951459235/job/16147608045?pr=11481) started to fail with the same error: ModuleNotFoundError: No module named 'configs'
.
We had to pin to 1.3.0.
Aha, I can already see how this might've happened, but I'll need to do a bit of testing on my end. Thanks for filing the issue, I'll take a look at your PR in just a moment here.
With the most recent release of pytest-retry, we are seeing some unexpected failures with Python 3.11 and the latest release of pytest.