-
Notifications
You must be signed in to change notification settings - Fork 28
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
Memory leak #200
Comments
Yes, we call In past, we noticed that if you were to use
Do you have an idea how this could be done other than calling Here is how it's done for Queue Mode now. After each batch of tests fetched from Queue API we executed the tests with
You could use KnapsackPro::Hooks::Queue.after_subset_queue do |queue_id, subset_queue_id|
puts 'after_subset_queue - run after the previous subset of tests'
end The
|
We have released version 7.0.0 of the knapsack_pro gem. This version has many improvements in Queue Mode for RSpec. We have not found any memory leaks. Therefore, I am closing this issue. Please find the migration steps at the following link: |
Based on this: rspec/rspec-core#2987
It looks like rspec has a memory leak when doing multiple runs within the same process. If I’m not mistaken, I think is how knapsack pro operates. We’ve notice our rspec instance taking significantly more memory in CI after switching to knapsack pro. Just wanted to put this issue up for further discussion.
Along the same lines, it would be better if knapsack pro could write custom runner that queries and adds tests on the fly to a single test run. This would make the output more seamless and address the memory issue, if it were the case.
The text was updated successfully, but these errors were encountered: