Add regular CI tests to verify full demo binaries build for all targets
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github-actions, rust
- Domain
- build-system, ci-cd, testing-qa
Research direction
Start by inspecting the existing weekly CI job and the linked rust-training weekly-canary-build.yml workflow. Compare how full example binaries and targets are selected, then determine whether the proposed checks should also run in QEMU. Done means the regular CI job automatically verifies the agreed demo binaries across the relevant targets.
Written by the indexing model from the issue text.
Description
Occasionally nightly Rust can have breakages in certain targets; we could catch these automatically by extending our existing weekly CI job to include building some full example binaries and possibly running in qemu. See https://github.com/rust-embedded/wg/discussions/941#discussioncomment-18655582, https://github.com/rust-embedded/aarch32/issues/227, https://github.com/ferrous-systems/rust-training/blob/main/.github/workflows/weekly-canary-build.yml.
- Dominant language
- Rust
- Stars
- 1k
- Forks
- 201
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 3
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rust-embedded/cortex-m
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
rust-embedded/cortex-m#651 · 5 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
rust-embedded/cortex-m#637 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
rust-embedded/cortex-m#511 · 2 comments ·
-
Enabling LOBOpen
Difficulty 4/5 3-5 days Newbie friendliness 52/100
rust-embedded/cortex-m#691 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
rust-embedded/cortex-m#660 ·
All issues in rust-embedded/cortex-m
Similar issues
-
feature request good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
TabularisDB/tabularis#853 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
andrewdavidmackenzie/jonesy#267 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 4 days
-
`future_into_py` loses the original panic messagePossibly taken @Danipulok claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
PyO3/pyo3-async-runtimes#91 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day