ci: Remove pytest-forked from requirements-testing.txt#6611
1 issue
find-bugs: Found 1 issue (1 medium)
Medium
Removing pytest-forked from requirements-testing.txt leaves gevent and opentelemetry tox environments without it - `requirements-testing.txt:5`
After removing pytest-forked from requirements-testing.txt, the gevent and opentelemetry tox environments have no path to install it, yet both contain tests decorated with @pytest.mark.forked that require process isolation.
Also found at:
scripts/populate_tox/config.py:378
⏱ 4m 18s · 519.2k in / 31.0k out · $1.12
Annotations
Check warning on line 5 in requirements-testing.txt
sentry-warden / warden: find-bugs
Removing pytest-forked from requirements-testing.txt leaves gevent and opentelemetry tox environments without it
After removing `pytest-forked` from `requirements-testing.txt`, the `gevent` and `opentelemetry` tox environments have no path to install it, yet both contain tests decorated with `@pytest.mark.forked` that require process isolation.
Check warning on line 378 in scripts/populate_tox/config.py
sentry-warden / warden: find-bugs
[NDD-H4C] Removing pytest-forked from requirements-testing.txt leaves gevent and opentelemetry tox environments without it (additional location)
After removing `pytest-forked` from `requirements-testing.txt`, the `gevent` and `opentelemetry` tox environments have no path to install it, yet both contain tests decorated with `@pytest.mark.forked` that require process isolation.