go-use go plugin test fails on non-amd64 architectures
Metadata
Current evaluation
test_go_use failed on arm64 because the unpinned golang/sys source required Go 1.23. Fixed in PR #1455 by pinning source-tag v0.41.0; GitHub-hosted aarch64 jobs are still skipped, tracked in #1313.
Suggested action: close resolved
Reason: The reported failure ("go: download go1.23 for linux/arm64: toolchain not available") came from the unpinned `sys` part sourcing go.googlesource.com/sys at HEAD, which now declares go1.23. The current test file pins `source-tag: v0.41.0` for that part, and git history shows this landed in commit 1d8d4f85 "ci: fix go_use test (#1455)". The residual case — GitHub-hosted aarch64 runners, where the preinstalled Go 1.22 cannot fetch a newer toolchain — is explicitly re-routed by the same maintainer to #1313 via the skipif reason string, so it is no longer tracked here.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
22
Quick Win:
16
Complexity:
15
Confidence:
80
Actionability:
85
|
close resolved | test_go_use failed on arm64 because the unpinned golang/sys source required Go 1.23. Fixed in PR #1455 by pinning source-tag v0.41.0; GitHub-hosted aarch64 jobs are still skipped, tracked in #1313. | |
| stealth/space-bunny-alpha |
Impact:
28
Quick Win:
19
Complexity:
20
Confidence:
82
Actionability:
85
|
close resolved | go-use plugin test fails on arm64 CI (go1.23 toolchain unavailable). Pinned sys v0.41.0 in PR #1455, but GitHub-hosted aarch64 jobs are now skipped via a skipif marker referencing #1313. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
11
Complexity:
40
Confidence:
70
Actionability:
60
|
keep open | test_go_use fails on non-amd64 architectures due to Go toolchain version mismatch; test is currently skipped on arm64 runners via skipif decorator. | |
| qwen/qwen3.8-27b |
Impact:
15
Quick Win:
10
Staleness:
75
Complexity:
30
Confidence:
82
Support Request:
10
|
close stale | test_go_use fails on arm64 due to missing Go toolchain. Superseded by issue #1313 which is the active tracking issue; test is already skipped on aarch64 with a reference to #1313. This issue has 0 comments, no labels, and no maintainer interaction in 356 days. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
40
Confidence:
80
Support Request:
10
|
needs triage | Test test_go_use fails on arm64 due to missing Go 1.23 toolchain. Issue is open, unlabelled, and has had no maintainer comments or activity in over 315 days. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
92
Complexity:
30
Confidence:
75
Support Request:
10
|
needs triage | Test test_go_use fails on arm64 due to missing Go toolchain for linux/arm64. Open for 10 months with no maintainer response or labels. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
craft-parts#1455
(confidence 92%)
Merged PR 'ci: fix go_use test' (commit 1d8d4f85); current test_go.py pins sys to source-tag v0.41.0, matching the PR's described fix.
-
Superseded By:
craft-parts#1313
(confidence 88%)
The skipif decorator in tests/integration/plugins/test_go.py points at #1313 ('go-use test isn't working on arm64 github-hosted runners'), the open follow-up for the remaining GH-hosted aarch64 case.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1313 go-use test isn't working on arm64 github-hosted runners | craft-parts | open | The go-use test was made arm64-compatible by pinning Go sys v0.41.0; GitHub-hosted aarch64 jobs are skipped because that runner only has Go 1.22. |