Repository navigation
Conversation
1 of 2 tasks
ero-qt
force-pushed
the
issue-168-harness
branch
2 times, most recently
from
October 4, 2026 14:43
58a25f7 to
8ca7346
Compare
ero-qt
force-pushed
the
issue-168-harness
branch
from
October 12, 2026 09:08
d00cdaa to
2b830ed
Compare
ero-qt
marked this pull request as ready for review
October 12, 2026 11:33
This branch has not been deployed
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.
Part of #141. Closes #168.
Adds a harness that runs the Unity fixture players against an auto splitter built on
asr. It lives inharness/as a crate of its own. It fetches the players from the fixtures releases by the manifest at a pinned commit, starts each one headless, loads the auto splitter throughlivesplit-auto-splitting, and checks what the auto splitter reports againstunity-fixture.json.The Linux CI run starts the players under
xvfb-run, because Unity 6000.0 to 6000.5 Linux players crash a few seconds after start without a display, even with-nographics.cargo run --releaseinharness/runs the 64 Windows or 29 Linux players of the pinned manifest.