fix(ci): isolate legacy Cargo scratch from workflow PVC#142
Merged
wolfiesch merged 2 commits intoJul 22, 2026
Conversation
wolfiesch
marked this pull request as ready for review
July 22, 2026 02:52
wolfiesch
approved these changes
Jul 22, 2026
wolfiesch
left a comment
Collaborator
There was a problem hiding this comment.
Reviewed exact head 8cd1d28. The change is narrowly scoped to Cargo scratch placement, preserves the final native artifact in the shared continuity workspace, and has coherent red/green contract evidence with terminal selected CI. No blocking issue found.
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.
Summary
This is a focused shared-service blocker fix. It moves only the legacy OMP Cargo target out of Woodpecker's 6 Gi shared workflow PVC and onto container
/tmp, which is governed by the existing 12 Gi pod ephemeral-storage limit. It disables Cargo incremental output while the unchanged upstream build copies its final napi artifact into.continuity/omp/packages/natives/nativefor the subsequentlegacy-bridge-continuitystep.Failure evidence
k3s-worker-01both exited code 1 whenrust-lldreceived SIGBUS.Change
CARGO_TARGET_DIR=/tmp/t4-legacy-authority-targetonlegacy-authority-build.CARGO_INCREMENTAL="0"..continuity/ompartifact path.Remote-CI TDD proof
f2d500c27e08bc0887e999c7d73ec8a6bb5d0cbfCARGO_TARGET_DIRasundefinedinstead of/tmp/t4-legacy-authority-target.8cd1d28ae4abd86a7d730490cbb6e6a91bc6c284changes88817678992,core88817679027,cluster88817706007,tooling88817706009, and terminalverify88818469675 all succeeded. Path-unselected platform/legacy jobs were skipped by the existing classifier.Non-goals
Relation to #125
PR #125 already supplied the Rust/Bun toolchain and resource-limit work now present on
main. This PR does not copy its remaining lower-resource delta; it adds only the isolated Cargo scratch contract/configuration required by the subsequently diagnosed PVC exhaustion.Rollback
Revert
8cd1d28ae4abd86a7d730490cbb6e6a91bc6c284to return Cargo intermediates to the workflow workspace, then revert the test-only contract commit with it.