Memory leak about knapsack_pro-ruby HOT 2 OPEN

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.

Yes, we call ::RSpec::Core::Runner for each batch of tests fetched from Queue API.

In past, we noticed that if you were to use KNAPSACK_PRO_RSPEC_SPLIT_BY_TEST_EXAMPLES=true and run too many RSpec test cases in queue mode it could lead to more memory consumption so that's why we try to run a minimal number of test cases when you use the RSpec split by test examples feature.

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.

Do you have an idea how this could be done other than calling ::RSpec::Core::Runner?

Here is how it's done for Queue Mode now.

After each batch of tests fetched from Queue API we executed the tests with ::RSpec::Core::Runner. After that we clean up some stuff with the rspec_clear_examples method.
It cleans up a few things:

You could use after_subset_queue to run a custom code that could do more cleanup as a next step. Maybe we could put there some code from the PR.

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 after_subset_queue hook is called after the rspec_clear_examples.

from knapsack_pro-ruby.