release-25.4: raftstorebench: prevent iter use-after-close #156299
+17
−8
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.
Backport 1/1 commits from #156288 on behalf of @tbg.
The
statsLoopcould still be running. In the linked test flake below, we see it call(*pebble).GetMetricswhen the engines are already closed.Rearrange the code so that we wait for
statsLoopto terminate properly before exiting the test.Closes #156138.
Epic: none
Release justification: