Clear error when specifying a non existing command
Metadata
Current evaluation
Merged snapcraft#350 to show a clear PATH error for missing commands and add test coverage, resolving LP #1550496.
Resolution: closed resolved
Reason: The pull request was merged after the requested test was added and review feedback was resolved. It replaces the unclear missing-command failure with an explicit error and covers it with tests.
Evaluated by: mr-cal-bot
No scores available.
Issue body
When a command is supposed to be in PATH, make sure
the error is clear.
LP: #1550496
Signed-off-by: Sergio Schvezov sergio.schvezov@ubuntu.com
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged snapcraft#350 to show a clear PATH error for missing commands and add test coverage, resolving LP #1550496. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged in canonical/snapcraft#350: improved the error shown when a command is not found in PATH, with added tests, resolving LP #1550496. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged. Improves error messaging when a specified command is not found in PATH, resolving LP #1550496. Approved after reviewer requested an additional test, which was added prior to merge. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged after adding requested test cases. The change improves error messaging when a command specified in PATH does not exist, providing clearer user feedback. Approved and merged following maintainer review. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1550496 Error message when command can't be found/isn't executable is terrible | snapcraft (launchpad) | closed | Replaced the opaque shell failure with a clear missing-command error; fixed by canonical/snapcraft#350 via commit 23e598149. |