Reduce repeated CI setup work
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github-actions, rust
- Domain
- build-system, ci-cd
Research direction
Start with the linked runs (42549528764, 42549528582, 42549528544) to see which setup steps dominate each job. The changes span several workflow jobs, the Asterinas cleanup, the openEuler self-test matrix, cargo-binutils versus llvm-objcopy, and the Library check grouping, so find the rust-objcopy and rust-nm callers first. Done means the same toolchain, feature and boot-path coverage with measured cold and warm timings.
Written by the indexing model from the issue text.
Description
Some CI jobs spend more time on setup than on the checks themselves. A few things we could simplify:
- Skip Asterinas disk cleanup when cached boot products are available. It took 125s and 142s in this run. Move cleanup into the container-build path, and measure disk usage before deciding whether cold builds still need it.
- Run the openEuler offline self-tests once per workflow. Each matrix job currently runs the full suite, taking about 218s in this run.
- Use
llvm-objcopywhere possible instead of compilingcargo-binutilsin every boot job. Check directrust-objcopyandrust-nmcallers when doing this. - Group small Library checks to share toolchain setup. This run started 15 jobs for about 45s of build and test steps.
Keep the existing toolchain, feature and boot-path coverage. Compare both cold and warm runs.
Related: #466, #468.
- Dominant language
- Rust
- Stars
- 1.3k
- Forks
- 184
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 29
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
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 rustsbi/rustsbi
-
[Bug]: RFENCE rejects the architecturally defined full-range size when start_addr is nonzeroPossibly taken @hongwei-2026 claimed this today. OpenC-bug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
rustsbi/rustsbi#484 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 22/100
Maintainers usually reply within 1 day
-
C-enhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 22/100
Maintainers usually reply within 1 day
-
C-bug help wanted P-high
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
[Bug]: Fix pmpm and smm region and slot managementPossibly taken @rkb32 claimed this today. OpenC-bug help wanted I-unsound P-high
Difficulty 5/5 Over a week Newbie friendliness 18/100
rustsbi/rustsbi#502 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
-
bug UI
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
wardian-app/Wardian#1746 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
jlcodes99/cockpit-tools#3125 ·
Maintainers usually reply within 2 days