Skip to content

test(unpack): register per-fixture native cases under portable names - #588

Merged
gmh5225 merged 1 commit into
devfrom
claude/unpack-fixnames
Oct 6, 2026
Merged

gmh5225 merged 1 commit into
devfrom
claude/unpack-fixnames

Conversation

@gmh5225

@gmh5225 gmh5225 commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

Follow-up to #579. The fixture matrix used testing::Combine, whose default parameter name carries spaces and parentheses in the GetParam() comment. The pinned CMake 4.2.3 test discovery (local and the Linux KVM runner) registers that form rather than the custom Kvm_<fixture> suffix, so the native CPU inventory gate could not find the required Backends/UnpackFixture.RecoversEntrySectionsAndImports/Kvm_* names and the KVM native CPU run failed at the inventory check (the unpacking itself passed). The Windows CMake happened to register the clean names, so WHP passed.

Fix: use one flat case struct with a PrintTo that emits the single-token Backend_Fixture name, as the other value-parameterized native tests (WindowsDeferred, user-execution) already do. ctest now registers .../Kvm_PlainLZMA etc. on every CMake version; the required-name gate is satisfied and the cases run unchanged (verified locally, and KVM native CPU CI dispatched).

The fixture matrix used testing::Combine, whose default parameter name
carries spaces and parentheses in the GetParam() comment. CMake test
discovery before 3.x and the pinned 4.2.3 register that form rather than
the custom suffix, so the native CPU inventory could not find the
Kvm_<fixture> case names on the Linux runner. Use one flat case struct
with a PrintTo that emits the single-token name, as the other
value-parameterized native tests do.
@gmh5225
gmh5225 merged commit 251ed4e into dev Oct 6, 2026
9 of 14 checks passed
@gmh5225
gmh5225 deleted the claude/unpack-fixnames branch October 6, 2026 11:20
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.

2 participants