← Back to issue list

Version test rejects dirty suffix in version strings

View original Github issue

Metadata

Project
starbase
Number
#589
Type
issue
State
open
Author
lengaubot
Labels
Created
Updated
Closed

Current evaluation

test_version_with_tags rejects dirty suffix in version strings, causing CI failures on dirty working trees. Untriaged, no maintainer response.

Suggested action: needs triage

Reason: The issue has no labels, no maintainer comments, no assignee, and shows no sign of having been assessed or prioritized. It's a clear bug report with specific reproduction details (expected regex vs actual version string) and references a similar fix in craft-application#864.

Impact: 40 Quick Win: 34.0 Staleness: 40 Complexity: 15 Confidence: 65 Support Request: 10

Issue body

`test_version_with_tags` in `tests/integration/test_version.py` rejects version strings with the dirty suffix, so a merge that carries a dirty working tree fails `make test-fast`. Observed failure: - expected regex: `\\d+\\.\\d+\\.\\d+(\\.post\\d+\\+g[0-9a-f]+)?` - actual version: `7.2.0.post165+g2c9fc684.d20260818` The Craft Application repo has already fixed this in PR [#864](https://github.com/canonical/craft-application/pull/864) (`fix(test): fix version test`). The Starbase-side test should accept the `.dYYYYMMDD` dirty suffix as well.

Evaluation history

Date Model Scores Action Summary
qwen3.6-35b-a3b-mtp-q6
Impact: 40
Quick Win: 34.0
Staleness: 40
Complexity: 15
Confidence: 65
Support Request: 10
needs triage test_version_with_tags rejects dirty suffix in version strings, causing CI failures on dirty working trees. Untriaged, no maintainer response.
qwen/qwen3.6-35b-a3b
Staleness: 0
Complexity: 10
Confidence: 90
Support Request: 0
needs triage Integration test fails on version strings with the .dYYYYMMDD dirty suffix. Unlabelled, no maintainer response yet.

Update history

Date Change
created

Related work

  • Related To: craft-application#864 (confidence 80%)

    Similar fix applied in craft-application repo for the same version test issue, suggesting this is a known pattern across canonical projects.

Related issues

No related issues found above the similarity threshold.