Skip to content

ci: add the release target to the pinned Rust toolchain - #8509

Draft
kixelated wants to merge 1 commit into
mainfrom
ci/armv7-pinned-toolchain-target
Draft

kixelated wants to merge 1 commit into
mainfrom
ci/armv7-pinned-toolchain-target

Conversation

@kixelated

Copy link
Copy Markdown
Collaborator

Problem

moq-cli / release / Build (armv7-unknown-linux-gnueabihf) has failed every nightly since armv7 shipped in #8250 (job): E0463 can't find crate for core. dtolnay/rust-toolchain installs the armv7 std into the image's stable (1.99.1), but rust-toolchain.toml pins 1.98.1, which is what cargo actually runs, and that toolchain never gets the target. The native x86_64 and aarch64 builds pass only because the host std ships with every toolchain.

Approach

Replace the action in the Linux build job with rustup target add "$TARGET" run from the checkout, the same pattern android.yml uses: rustup resolves the pinned toolchain from rust-toolchain.toml and adds the target to it.

Impact

  • No public API or wire change. Restores the armv7 moq tarball and .deb in nightly and releases.

Alternatives

  • Listing armv7 under targets in rust-toolchain.toml: every developer and CI job would download its std.
  • toolchain: 1.98.1 on the action: duplicates the pin in another place to keep in sync.

Follow-ups

None. Other nightly failures triaged alongside this: Gate cost needs a host with a PMU (hosted ubuntu-24.04 VMs report No supported events found; the job has never passed), and the apt Temporary failure resolving errors were a roughly two hour Azure DNS outage for the Ubuntu archive hosts (apt on the same ubuntu-26.04 image worked at 12:50 UTC the same day and every prior night).

Review

Skipped: a one-step workflow change, checked with just check (zizmor, actionlint, gh tests).

(Written by Opus 5.5)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@kixelated

Copy link
Copy Markdown
Collaborator Author

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 11, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-11T17:12:02.605111Z edeb4ba Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Breezy!

Reviewed commit: edeb4bab35

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

This branch has not been deployed

No deployments
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