snapcraft points to wrong entry in apps as being invalid.
Metadata
Current evaluation
Snapcraft 6.1 misreports runtests as invalid even though get_cache_info, which contains an underscore, is the actual invalid app name; the issue remains open without a confirmed fix.
Suggested action: keep open
Reason: The report provides a concrete snapcraft.yaml and error: get_cache_info contains an underscore, while runtests uses only allowed letters, yet the error blames runtests. Despite the craft-1293 and snapcraft labels, there is no maintainer comment or resolving commit or PR reference, so this valid diagnostic bug should remain open.
Evaluated by: mr-cal-bot
Impact:
35
Quick Win:
22
Complexity:
25
Confidence:
82
Actionability:
85
Issue body
snapcraft version 6.1
I'm building a snap from a github repository that produces a bunch of small binaries, and a shell script called "run_tests.sh" that executes them all.
I wish to make this script, as well as each individual binary, available from the snap.
In my snapcraft.yaml, I started a section for apps:
apps:
# provided script that runs all tests
runtests:
command: perf_event_tests/run_tests.sh
# individual test binaries
get_cache_info:
command: perf_event_tests/utils/get_cache_info
events:
command: perf_event_tests/sysfs/events
However I'm getting this error from snapcraft:
Issues while validating snapcraft.yaml: The 'apps' property does not match the required schema: 'runtests' is not a valid app name. App names consist of upper- and lower-case alphanumeric characters and hyphens. They cannot start or end with a hyphen.
However, runtests isn't invalid - get_cache_info is.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
35
Quick Win:
22
Complexity:
25
Confidence:
82
Actionability:
85
|
keep open | Snapcraft 6.1 misreports runtests as invalid even though get_cache_info, which contains an underscore, is the actual invalid app name; the issue remains open without a confirmed fix. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
14
Complexity:
20
Confidence:
60
Actionability:
60
|
keep open | Snapcraft incorrectly reports 'runtests' as an invalid app name. The actual invalid name is likely 'get_cache_info' (contains underscore), but the error message misidentifies the culprit. | |
| qwen/qwen3.8-27b |
Impact:
25
Quick Win:
18
Staleness:
95
Complexity:
30
Confidence:
70
Support Request:
20
|
keep open | Snapcraft 6.1 validation error misreports the first app ('runtests') as invalid when the actual offending app name ('get_cache_info', with an underscore) is the real problem. No maintainer interaction; zero comments; ~4 years old. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
20
Confidence:
85
Support Request:
30
|
close stale | snapcraft 6.1 incorrectly reports 'runtests' as an invalid app name in snapcraft.yaml. The report lacks maintainer interaction, has no comments, and is over 3.5 years old. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
30
Confidence:
85
Support Request:
0
|
close stale | snapcraft v6.1 incorrectly flags 'runtests' as an invalid app name instead of 'get_cache_info'. No maintainer interaction in over 3.9 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
20
Confidence:
80
Support Request:
0
|
needs triage | Snapcraft v6.1 validation incorrectly flags valid app names as invalid while ignoring actually invalid ones. Issue remains unassessed by maintainers with zero comments after nearly four years. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
snapcraft (launchpad)#1996525
(confidence 78%)
A separate open Launchpad issue reports the same misleading app-name diagnostic, where the first app is blamed instead of the entry containing the invalid underscore.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1996525 inaccurate error for a misformatted app name | snapcraft (launchpad) | open | Snapcraft 7.2.7 reports the first app name when the later ccc_ccc app key is invalid; the report remains untriaged with no comments, labels, or confirmed fix. |