'--workers 2' raise error when working with pytest5.x about pytest-parallel HOT 5 CLOSED

i got the same error.

from pytest-parallel.

It works with 5.2.4.dev6+ge856638ba for me (master), but fails on the "features" branch:

  File "…/Vcs/pytest/src/_pytest/terminal.py", line 468, in pytest_runtest_logfinish
    main_color, _ = _get_main_color(self.stats)
  File "…/Vcs/pytest/src/_pytest/terminal.py", line 1102, in _get_main_color
    for found_type in stats:
  File "<string>", line 2, in __iter__
  File "/usr/lib/python3.7/multiprocessing/managers.py", line 825, in _callmethod
    proxytype = self._manager._registry[token.typeid][-1]
AttributeError: 'NoneType' object has no attribute '_registry'

The following patch for pytest fixes it:

diff --git i/src/_pytest/terminal.py w/src/_pytest/terminal.py
index 40e12e406..e88545eca 100644
--- i/src/_pytest/terminal.py
+++ w/src/_pytest/terminal.py
@@ -1099,7 +1099,7 @@ def _get_main_color(stats) -> Tuple[str, List[str]]:
         "failed passed skipped deselected xfailed xpassed warnings error".split()
     )
     unknown_type_seen = False
-    for found_type in stats:
+    for found_type in stats.keys():
         if found_type not in known_types:
             if found_type:  # setup/teardown reports have an empty key, ignore them
                 known_types.append(found_type)

I have some WIP in that area already, but pytest-parallel should handle iteration of stats probably, if it's easy.

Related code there: https://github.com/browsertron/pytest-parallel/blob/eb851777d354ba79d26d9b088bc1c22a8d44720b/pytest_parallel/__init__.py#L254-L269
(haven't looked at it really)

from pytest-parallel.

JFI: the error I've posted happens when run in the subprocess, and starts to happen with pytest 5.3.0.

I am not sure why the original report is a problem / how it is triggered, since this should run in the main process.

pytest-dev/pytest#6261 however should fix both (at least the one from me).

from pytest-parallel.

@AndyFoolish
Is this fixed with the latest release for you?

from pytest-parallel.

@azmeuk Please consider closing this out. It is seen by the discussion that the issue is related to pytest itself. And I also tested on my synthetic suite all major pytest versions starting from 5.2 till 7.1 without any issues. I would closed this until someone provide a reproducible example.

from pytest-parallel.