Repository navigation
docs: align launch setup with current TIRx Harness - #3
Merged
Merged
Conversation
jinhongyii
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
1 participant
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
The launch tutorial used an outdated KCoral invocation and said Humanize was included in the harness environment. Introduce the run preparation workflow before its commands, install its preparation requirements, use the server dependency group and
python -m kcoral server, describe the per-run environment, and install Humanize separately.Checked against TIRx-harness
a68d2b4and TIRx-kernels909d8e0. Existing kernel links already match the reorganizedported/layout and need no changes.Validation
make htmlpasses with warnings treated as errors.bash -n.git diff --checkpasses.GPU benchmarks and full run preparation were not executed.