Skip to content

fix: improve host runner, filesystem tests, and boot verification - #97

Merged
cellrishi-code merged 16 commits into
mainfrom
fix/host-runner-errors-cli-tests
Oct 25, 2026
Merged

cellrishi-code merged 16 commits into
mainfrom
fix/host-runner-errors-cli-tests

Conversation

@cellrishi-code

@cellrishi-code cellrishi-code commented Oct 25, 2026 •

Copy link
Copy Markdown
Owner

Summary

This consolidated PR addresses the ten repository issues created after reviewing the current x86_64/no_std kernel, host QEMU runner, RAM filesystem prototype, memory-map summary, and CI workflow.

  • Improve QEMU and OVMF error diagnostics; add unit tests for CLI parsing.
  • Pin OVMF to EDK2 stable 202508-r1 for reproducible UEFI firmware selection.
  • Publish RAM filesystem size limits and add boundary/path/content regression tests.
  • Add synthetic tests for memory-map aggregation, empty maps, invalid ranges, and saturation.
  • Add a troubleshooting guide and link it from the README.
  • Define a stable [BOOT_OK] marker that is emitted only after early initialization and the RAM filesystem smoke check pass.
  • Add a bounded QEMU BIOS boot smoke test that asserts the serial success marker.
  • Install rust-src, required by the bootloader's build-std build, and format affected sources.

Issues addressed

Closes #87
Closes #88
Closes #89
Closes #90
Closes #91
Closes #92
Closes #93
Closes #94
Closes #95
Closes #96

Validation

The initial CI run found formatting issues and then failed because rust-src was missing for the bootloader's build-std step. Formatting has been corrected and rust-src has been added to the repository toolchain and QEMU job. Please use the latest GitHub Actions run as the verification source; I have not run the compiler or QEMU locally in this session.

@cellrishi-code cellrishi-code changed the title fix: improve host runner diagnostics and test CLI parsing fix: improve host runner, filesystem tests, and boot verification Oct 25, 2026
@cellrishi-code
cellrishi-code merged commit cfa4881 into main Oct 25, 2026
1 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment