🧪 Stop using pytest-forked

cheroot/test/test_server.py

@@ -400,15 +400,6 @@ def test_reuse_port(http_server, ip_addr, mocker):
     assert spy.spy_exception is None
 
 
-ISSUE511 = IS_MACOS
-
-
-if not IS_WINDOWS and not ISSUE511:
-    test_high_number_of_file_descriptors = pytest.mark.forked(
-        test_high_number_of_file_descriptors,
-    )
-
-
 @pytest.fixture
 def _garbage_bin():
     """Disable garbage collection when this fixture is in use."""

docs/changelog-fragments.d/502.contrib.rst

@@ -0,0 +1 @@
+703.contrib.rst

docs/changelog-fragments.d/511.contrib.rst

@@ -0,0 +1 @@
+703.contrib.rst

docs/changelog-fragments.d/680.contrib.rst

@@ -0,0 +1 @@
+703.contrib.rst

docs/changelog-fragments.d/681.contrib.rst

@@ -0,0 +1 @@
+703.contrib.rst

docs/changelog-fragments.d/703.contrib.rst

@@ -0,0 +1,15 @@
+The test infrastructure has been updated to stop using
+the ``pytest-forked`` plugin
+-- by :user:`jaraco` and :user:`webknjaz`.
+
+This plugin was causing problems with upgrading to modern
+versions of Pytest and it is not going to be fixed anytime
+soon.
+
+It was used in a test that interacts with the system
+resource limits under \*NIX environments in hopes to isolate
+the side effects caused by the preparatory code.
+
+It is possible that this will have an effect on the test
+sessions and we may have to look for alternative solutions
+for test process isolation.

requirements/tests.in

@@ -34,18 +34,15 @@ pypytools
 
 pytest-clarity
 pytest-cov==2.12.0
-pytest-forked>=1.2.0; sys_platform != "win32"
 pytest-mock>=1.11.0
 pytest-rerunfailures
 pytest-sugar>=0.9.3
 pytest-watch==4.2.0
 pytest-xdist>=1.28.0
 
-# pytest-forked is currently incompatible with pytest 7
-# Refs:
-# * https://github.com/cherrypy/cheroot/issues/511
-# * https://github.com/pytest-dev/pytest-forked/issues/67
-pytest >= 4.6.6, < 7
+# pytest 7.2 introduces deprecations triggered by pytest-cov
+# * https://github.com/cherrypy/cheroot/issues/682
+pytest >= 7, <7.2
 
 # HTTP over UNIX socket
 requests-unixsocket