Skip to content

fix(ci): use hardcoded target/ path in Package runtime step#322

Merged
DorianZheng merged 1 commit intomainfrom
fix/ci-package-runtime-cargo-deleted
Mar 2, 2026
Merged

fix(ci): use hardcoded target/ path in Package runtime step#322
DorianZheng merged 1 commit intomainfrom
fix/ci-package-runtime-cargo-deleted

Conversation

@DorianZheng
Copy link
Copy Markdown
Member

Summary

  • Fix CI "Package runtime" step failing on Linux because cargo was deleted earlier in the build flow
  • The Linux build deletes ~/.rustup and ~/.cargo after building the guest binary (to save disk space), so cargo metadata fails silently, leaving TARGET_DIR empty
  • Replace cargo metadata lookup with direct target/ reference — no custom target-dir is configured in this project

Test plan

  • Verify CI build-runtime workflow passes on Linux targets
  • Verify CI build-runtime workflow still passes on macOS targets

The Linux build flow deletes ~/.rustup and ~/.cargo after building the
guest binary to save disk space. The Package runtime step then calls
cargo metadata on the host, which fails silently due to 2>/dev/null,
leaving TARGET_DIR empty and causing the step to error out.

Replace the cargo metadata lookup with a direct target/ reference since
no custom target-dir is configured in this project.
@DorianZheng DorianZheng merged commit 243fde1 into main Mar 2, 2026
@DorianZheng DorianZheng deleted the fix/ci-package-runtime-cargo-deleted branch March 2, 2026 01:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant