Repository navigation
Add bin/test --build-only, which runs the test build and stops - #1155
Merged
Merged
Conversation
Add `--build-only` to `bin/test`, which runs the `cargo build` a test run starts with and then exits, so a script that warms a checkout's `target/` for later `bin/test` runs builds exactly what they reuse, without a copy of the build command that can drift. It skips the ramdisk, leaves test data alone, and refuses `-p`.
Contributor
|
No actionable comments were generated in the recent review.
 |
| Layer / File(s) | Summary |
|---|---|
Add and validate the build-only option bin/test, AGENTS.md |
The script documents and parses --build-only. It exits with status 2 if the option is combined with -p/--python. The building commands document the new option. |
Skip test setup and exit after the build bin/test |
Build-only mode skips test-data and ramdisk cleanup and ramdisk setup. After cargo build, the script exits before server startup and test execution. |
Estimated code review effort: 2 (Simple) | ~10 minutes
Possibly related PRs
- Oxen-AI/Oxen#1120: This PR configures macOS
DYLD_LIBRARY_PATHfor Cargo build and test commands inbin/test, including the Cargo build used by build-only mode when both changes are present.
Merge Risk: 
19792
-
The new option provides the documented build-only workflow without introducing an established merge-blocking risk.
Pre-merge checks: 
-
Check name Status Explanation Title check The title clearly and concisely describes the main change: adding a --build-onlyoption tobin/testthat builds and stops.Description check The description directly explains the --build-onlybehavior, purpose, and restrictions described in the changeset.Linked Issues check Check skipped because no linked issues were found for this pull request. Out of Scope Changes check Check skipped because no linked issues were found for this pull request.
Finishing Touches
-
Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
jcelliott
approved these changes
Nov 2, 2026
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.
Add
--build-onlytobin/test, which runs thecargo builda test run starts with and then exits, so a script that warms a checkout'starget/for laterbin/testruns builds exactly what they reuse, without a copy of the build command that can drift. It skips the ramdisk, leaves test data alone, and refuses-p.