Add test for memory leak through StepExecutionIterator
when build is stuck loading programPromise
#357
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Comparable to #347.
I ran into another similar memory leak, but unlike in the previous case where the problematic build was stuck in an infinite loop in its
CpsVmExecutorService
, in this case the problematic build'sprogramPromise
was stuck and never finished loading pickles because aFilePathPickle
was looping forever.This PR just adds a test to show that the fix in the previous PR handles memory leaks in both cases.
Testing done
Submitter checklist