oxidecomputer / oxidecomputer/propolis

phd(?): we should test more kernels!

Open
#1,176 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

development testing
Dominant language
Rust
Stars
270
Forks
42
Avg merge
4d 5h
Merged PRs (30d)
6

Description

in https://github.com/oxidecomputer/propolis/issues/1173 I alluded to one of the interesting reasons about testing against a gamut of Linux distros, even though at the end of they day "they're all Linux": they've all got different kernels and different drivers.

the most recent Linux (and the most recent FreeBSD, and ..) won't be expressed by most distributions, so just testing distributions means there's a lot of time to miss "Linux change that Propolis/byhve don't play nice with". distributions are convenient single blobs we can boot and test, but in the ideal world of perfect testing we'd be able to build test Linux images with arbitrarily-recent kernels (similar to testing against, say OmniOS bloody or FreeBSD-STABLE)

there might be a nice interim point here, with a rolling release Linux distro? since just a kernel doesn't get you a userland, and mostly I'd have loved to learn about https://github.com/oxidecomputer/propolis/issues/1163 before 26.04 got cut..

@papertigers has fiddled with some scripts to assemble Alpine-like Linux images would would probably be suitable for running PHD tests against, and @lgfa29 has (afaik) used Packer to assemble a test image with fwts pre-installed. it might be possible to use either approach in this way, or maybe we do something different entirely!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading issues 1173 and 1163, then inspect the existing scripts mentioned for Alpine-like image assembly and the Packer approach with fwts. Determine how a test image with an arbitrarily recent kernel could be built and used for PHD tests; done means the image can boot and exercise those tests reliably.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
build-system, operating-systems, testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.