-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
execnet.gateway_base.DumpError: can't serialize <enum 'ExitCode'> #464
Comments
Hi @tiffinysmile, Strange, version Could you provide a minimal reproducible example? I would be glad to try it out. Some suggestions in the future to improve bug reports:
|
it only happens when many UI test cases run |
Strange, I don't see how they could affect this... Any chance of providing a reproducible example? |
I have run into this error a few times recently. It seems elusive. I always works when I restart the test.
|
The same on pytest 5.0.1, 5.1.2. Version 4.6.5 is ok. I guess, there is the reason (5.0.0 release changelog):
|
I encountered a very similar error when trying to use xdist with pytest-molecule:
I mention that the plugin works fine when not used with xdist, only enabling xdist triggers this error. I have no idea what is confusing them because they all use different entry points, like seen on https://github.com/pycontribs/molecule-azure/blob/master/setup.cfg#L85-L87 -- they are not supposed to interfere one with another. |
@ssbarnea different issue - https://github.com/pycontribs/pytest-molecule/blob/master/pytest_molecule/__init__.py#L55 bug in pytest-molecule, unserializable option setups like that arent supported by pytest |
Mainly pytest options must be serializable and our code was passing Driver instances instead of strings to pytest options dictionary. This was breaking python-xdist module, even if pytest-molecule was not used. Related: pytest-dev/pytest-xdist#464
Mainly pytest options must be serializable and our code was passing Driver instances instead of strings to pytest options dictionary. This was breaking python-xdist module, even if pytest-molecule was not used. Related: pytest-dev/pytest-xdist#464
@RonnyPfannschmidt @ssbarnea Same issue here, what is the proposed solution? Triggered by the combination of pytest-xdist + pytest-cov + MacOS. I have no idea why it will pass if any of the three conditions doesn't meet. https://github.com/frostming/pdm/pull/109/checks?check_run_id=587701930 |
for this workflow run logs have been deleted, so you still see the error on the latest pytest-xdist? |
closin this one as not actionable |
The text was updated successfully, but these errors were encountered: