← Back to issue list

Add workflow and integration test reproducing libapt ABI mismatch (Issue #1554)

View original Github issue

Metadata

Project
craft-parts
Number
#1555
Type
pull request
State
open
Author
Copilot
Labels
—
Created
Updated
Closed
—

Current evaluation

Copilot-opened PR adding a GH workflow plus integration test reproducing the libapt ABI mismatch from issue #1554 (lxc network set fixes, IPv6/dnsmasq removal, curl-based connectivity check). 163 days idle, 2 unresolved review comments, several CI jobs failing.

Suggested action: close stale

Reason: The PR only adds a reproducer workflow/integration test (+218 lines, 2 new files) rather than a fix for #1554, whose summary notes 'root cause still debated' and that the issue has an existing 'reproducer branch'. It has been untouched for 163 days with changes_requested review and 2 unresolved comments; the single maintainer reply from @lengau ('sleep for 10 seconds after launching the container. It's not a fix but it's good enough for now') indicates the hack was not accepted as a solution. Multiple checks remain red, including the directly relevant '24.04 – noble python-apt' and '26.04 – noble python-apt' jobs plus 'policy / Check PR title for Conventional Commits' (the title is not conventional-commit formatted), so the branch is not in a mergeable state and the author showed no further intent.

Evaluated by: mr-cal-bot

Impact: 12 Quick Win: 1 Complexity: 45 Confidence: 78 Actionability: 20

Issue body

- [x] Fix `lxc network set` accepting only one key/value at a time - [x] Remove `lxc network set lxdbr0 ipv6.address none` and `ipv6.nat false` — these cause LXD to restart dnsmasq, silently breaking IPv4 DNS inside containers - [x] Fix the wait-for-connectivity loop: replace broken `grep "^[0-9]"` (matched "000" on DNS failure) with a direct `curl` exit-code check (curl only exits 0 on a real HTTP response)

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 12
Quick Win: 1
Complexity: 45
Confidence: 78
Actionability: 20
close stale Copilot-opened PR adding a GH workflow plus integration test reproducing the libapt ABI mismatch from issue #1554 (lxc network set fixes, IPv6/dnsmasq removal, curl-based connectivity check). 163 days idle, 2 unresolved review comments, several CI jobs failing.
qwen/qwen3.6-35b-a3b
Impact: 30
Quick Win: 2
Complexity: 20
Confidence: 75
Actionability: 10
close stale PR adds workflow and integration tests reproducing libapt ABI mismatch (Issue #1554). Open 152 days with no activity since opening, 2 unresolved review comments, and multiple failing CI checks.
qwen/qwen3.8-27b
Impact: 25
Quick Win: 15
Staleness: 78
Complexity: 40
Confidence: 62
close stale Adds a GitHub workflow and integration test to reproduce the libapt ABI mismatch from issue #1554 using LXC containers. Review status is changes_requested with 2 unresolved comments; author unresponsive for 131 days. CI failing on multiple checks including Conventional Commits policy.
qwen/qwen3.6-35b-a3b
Staleness: 65
Complexity: 15
Confidence: 75
close stale Adds workflow and integration tests for libapt ABI mismatch. Status: changes requested with 2 unresolved comments. Inactive for 90 days. Title and body describe unrelated LXD network fixes.
qwen3.6-35b-a3b-mtp-q6
Staleness: 78
Complexity: 20
Confidence: 85
close stale PR inactive for 78 days. Title references a libapt ABI mismatch test, but body describes unrelated LXD network fixes and a connectivity loop workaround. Lacks maintainer review.

Update history

No update history recorded yet.

Related work

  • Related To: canonical/craft-parts#1554 (confidence 95%)

    PR title and body both target this issue; the issue already has its own reproducer branch and open root-cause debate, so the added test here is duplicative and non-diagnostic.

  • Caused By: canonical/craft-parts#1554 (confidence 90%)

    The libapt ABI mismatch on Ubuntu 26.04 is the upstream defect this PR attempts to reproduce, not fix.

Related issues

No related issues found above the similarity threshold.