tests: Port away from nushell
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start by locating the Nushell test scripts and the test infrastructure that builds or runs them; the issue does not name specific files or a particular test. Read the existing tests and identify one with some complexity, such as an on-target build, to use as the initial port. Done means a Rust-based test binary using xshell can run that test, with infrastructure in place to continue migrating the rest.
Written by the indexing model from the issue text.
Description
I championed using nushell, but I regret it now mostly. It's not bad per se (certainly better than shell script IMO) but the core problem is:
- They keep making subtle behavioral changes that break us periodically (it's not often but we really do want a 1.0 stable language for our tests)
- It's a relatively obscure language that while does support some static analysis (definitely better than bash!) many failures are still runtime, and LLMs just don't know it as well. Also it's just another language.
A big complexity here is that of course in going to a compiled language. I think basically what we do is generate a separate bootc-tests binary that embeds all the logic.
I think basically we should use Rust with https://docs.rs/xshell/latest/xshell/ for our tests. It'll be more verbose, but that's probably OK.
To implement this I think we can basically just try to port one test (one that has some complexity, like is doing on-target builds etc) and build out the infra (which will necessarily involve some duplication) but then gradually port over all of the others.
- Dominant language
- Rust
- Stars
- 2.3k
- Forks
- 230
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 42
Getting set up
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 bootc-dev/bootc
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
install: improve error message when systemd-boot is selected without composefs backendMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
Maintainers usually reply within 2 days
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Wait for the IDS correction dialog to settle in the stale-audit testPossibly taken @louistrue claimed this today. Openready
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
dutchman-cad/dutchman#874 ·
Maintainers usually reply within 1 day
-
bug good first issue ready
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
MartinPTielemans/ilo#3840 ·
Maintainers usually reply within 1 day
-
bug file-compat priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
storytold/wordcraft#7248 · 1 comment ·
Maintainers usually reply within 4 days