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
Fix quadratic performance with nextest #8
Comments
Here's how to address this:
I'd estimate around 4-6 hours of work for someone new to the project, with the bulk of that time being spent in writing tests. You're encouraged to submit a PR even if your implementation isn't totally perfect. I'm happy to pick up the last 10-20%. |
thinking of trying this out this weekend 🥳 |
@poopsicles if you aren't working on it, then I'd like to give it a try. |
@jalil-salame yeah, that would be for the best have fun 🥳 |
I thought I would have some free time these last few weeks, but I didn't, if anyone was holding back because of me, please don't and feel free to pick this up, just drop a comment if you start work on this. |
No worries, totally understandable. I'd still love it if someone picked it up! |
Some performance numbers using
All my test files are named by the hash of their content, so that's why adding more |
I'll pick this one up 😄. |
Let's say you have 10k files. Datatest-stable iterates over all files currently to build the list of tests. Since nextest has a process-per-test model, each test will iterate over every file. That's not great.
Instead, if
--exact
is passed in, we should be able to pinpoint the exact test and just use that.The text was updated successfully, but these errors were encountered: