-
Notifications
You must be signed in to change notification settings - Fork 234
How xdist according to the test file allocation process? #193
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
Comments
with your question, i dont see a good way to answer since you didnt even remotely outline your use-case your English skill is indeed a major communication blocker there |
How are you I want to use xdist plug-in distribution test files, a process to distribute a test file, instead of distribution according to the amount of test method, what should I do?Thank you very much. |
@linlin547 again, if i cant make sense of your question, i cant hope to help, if your own English is too bad please get help from someone with better English skills, else i will have to close this issue as not actionable due to language barrier |
I'm going on a limb here, but perhaps @linlin547 means that he wants to distribute the tests to workers grouped by test module instead of by individual tests sent to each worker individually? @linlin547 can you confirm? If that's the case, there's #191 going on to fit exactly that. |
all methods execute in a same thread from a same file . |
execute tests group by class in a same thread @RonnyPfannschmidt @nicoddemus |
Thanks for finding an example demonstrating your problem. As I said there's work regarding this on #191. I recommend to watch that issue closely. 👍 Closing this for now. |
example : |
Yep it's clear now. The short answer is: that can't be done right now, but there's work being done in #191. |
Hello, my English is very poor, I want to use xdist allocation process, not according to the distribution of the test method, Need a process distribution a test file, what should I do?Thank you very much.
The text was updated successfully, but these errors were encountered: