Skip to content

tools/test_template.py: no mcpp pointer in the fixture descriptor - #2

Merged
Sunrisepeak merged 1 commit into
mainfrom
fix/template-harness-pointer
Nov 20, 2026
Merged

Sunrisepeak merged 1 commit into
mainfrom
fix/template-harness-pointer

Conversation

@Sunrisepeak

Copy link
Copy Markdown
Member

The template harness's fixture descriptor says mcpp="mcpp.toml". Since mcpp 2026.11.19.1 a string pointer must match exactly one file under the version directory (the archive's files sit one directory deeper), so mcpp new --list-templates failed with "mcpp pointer 'mcpp.toml' did not match any file" on current mcpp. Dropping the field lets the engine look for */mcpp.toml, as published descriptors do. Verified: the harness passes on mcpp 2026.11.18.1 (the CI pin) and 2026.11.20.1. Found while releasing slint-m, whose harness was copied from this one.

…pp 2026.11.19.1+ reads it as an exact path)

The fixture descriptor said mcpp="mcpp.toml"; since 2026.11.19.1 a string pointer must match exactly one file under the version directory, so the scaffold step failed with "mcpp pointer 'mcpp.toml' did not match any file" on current mcpp. Without the field the engine finds */mcpp.toml, as published descriptors do. Passes on 2026.11.18.1 (CI's pin) and 2026.11.20.1.
@Sunrisepeak
Sunrisepeak merged commit a63e636 into main Nov 20, 2026
6 checks passed
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