-
Notifications
You must be signed in to change notification settings - Fork 232
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
Options with nonserializable types break under xdist #384
Comments
Indeed, that's a limitation of our backend, we should add this to the documentation. In addition, we could also register a serializer for a |
I had assumed that the options were passed textually and reparsed in the child. Obviously that would not have had this limitation, since the CLI parameters were strings to start with before |
You are right, but to reparse in the worker, you need specialized code for it that knows about |
Oh, no, I meant I assumed that the options weren’t passed as parsed objects at all. I originally assumed that |
Oh I see what you mean, makes sense. It seems I believe (without looking at the code) that xdist will first parse and handle/filter out some of the arguments, because workers won't know what to do with some options ( |
Yes, I realize it will need some investigation. I guess there might be cases where, if workers are being run on other machines, then xdist might not be installed on the worker machines so they might not understand |
structurally pytest itself simply does not support required arguments at all |
@RonnyPfannschmidt comment on wrong ticket? |
@Hawk777 whops, my fault, one shouldn't open all the images right after a oversize dinner |
@nicoddemus it looks like this is still happening and options_dict is still being sent |
I wanted a command-line option to take a filename as its value. It works fine with vanilla py.test, but not with xdist.
The text was updated successfully, but these errors were encountered: