Repository navigation
fix(tests): isolate renderer runtime directories - #120
Merged
Merged
Conversation
azelarin
force-pushed
the
fix/renderer-runtime-isolation
branch
from
November 1, 2026 19:12
a4821d7 to
7c5f79d
Compare
azelarin
marked this pull request as ready for review
November 1, 2026 19:21
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
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.
renderer fixtures now use a private runtime directory for their compositor and thing instance. the parent wayland socket is resolved before switching directories, and the temporary runtime remains until the fixture's process group has stopped. this keeps test command sockets separate from desktop instances.
a regression reproduces the shared runtime on main and checks directory permissions, parent connection, and cleanup ordering. tool tests and guarded opengl and vulkan fixtures pass.
closes #119