Repository navigation
Clean up RavenDB temp files after tests complete - #6024
Merged
Merged
Conversation
rbev
force-pushed
the
remove-test-temp-folder
branch
from
October 19, 2026 07:56
e82fe19 to
0358993
Compare
warwickschroeder
approved these changes
Oct 20, 2026
rbev
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
RavenDB tests leave per-process Voron scratch, journal, and buffer files in
RavenDBServer/Temp. These files accumulate across runs and do not provide reusable state for subsequent tests.ravendb-<pid>-*files from both shared RavenDB test lifecycles. Preserve other processes’ files and server binaries.Production behavior remains unchanged. Cleanup targets the current server process, not files left by earlier runs. Forced termination can still leave files behind.