ci: spec22-gems msys harness presses probe images in the leg's format - #113
Merged
Merged
Conversation
The three mkimage invocations hardcoded --format dwarfs. On the arm64 leg that fails by name: the windows/arm64 link unit is limnifs-only (clangarm64 has no native dwarfs-t), so its driver never mounts dwarfs bytes and the tfs CLI (v2.8.16) answers "mkimage --format dwarfs is not available on windows-arm64 ... use --format limnifs" — the second arm64 dogfood's exit 1 (tebako-runtime-ruby run 35690023046, after the arch-detection fix carried staging and the bridge tree green). The press format now rides the same arch detection as the DLL naming: dwarfs on x64 (the x64 env image's format), limnifs on arm64. The setup image and both payload probes (materialized + negative oracle) share the one derivation, so the proof legs always mount the format the runtime under test actually ships.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The second arm64 dogfood (tebako-runtime-ruby run 35690023046) got past staging and the bridge tree with #112, then failed at the probe presses:
All three
mkimagecalls hardcoded--format dwarfs. On windows/arm64 the runtime is limnifs-only by design (the link unit has no native dwarfs-t under clangarm64), so the driver under test never mounts dwarfs bytes and the CLI refuses the press by name.What
PRESS_FORMATderives from the same arch detection #112 added (MSYS_TOOLCHAIN):dwarfson x64 (the x64 env image's format),limnifson arm64. The setup image and both payload probes (materialized + negative oracle) share the one derivation, so the proof legs always mount the format the runtime under test ships.Proof
bash -nclean; the onlydwarfsmentions left are the new comment and the x64 arm of the derivation.