Skip to content

Let rk cross-modules take the reference boot from rk test - #259

Merged
tamnd merged 1 commit into
mainfrom
k2-cross-tested
Nov 17, 2026
Merged

tamnd merged 1 commit into
mainfrom
k2-cross-tested

Conversation

@tamnd

@tamnd tamnd commented Nov 17, 2026

Copy link
Copy Markdown
Owner

The Fedora 7.4 run against gcc-14 (43997097793) ran out of time in rk cross-modules. Each kunit boot of that config takes about 95 minutes on the runner, and cross-modules boots three of them two at a time, so the third boot started at the 95 minute mark and was cut off 25 minutes later. Nothing in the kernels was wrong.

The first of the three boots is the reference kernel with its own modules, which is the boot rk test has just run as reference-kunit-1. This adds --tested DIR to rk cross-modules. When the rk test run directory has that boot's outcome and console for a run, cross-modules reads it from there and only boots the two crossed cells, side by side. A run without it boots all three as before.

The nightly passes --tested "$RUNNER_TEMP/test", so the step needs one round of boots and not two, and the Fedora config fits in the job.

Checked on server3 with cargo fmt, clippy and the cross tests, including a new one for reading the tested boot.

@tamnd
tamnd merged commit 910d754 into main Nov 17, 2026
0 of 2 checks passed
@tamnd
tamnd deleted the k2-cross-tested branch November 17, 2026 07:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant