tests: add jammy packages to stage package apt cache
Metadata
Current evaluation
Merged #494 as commit dcdab592, updating the AptCache stage-package test for Jammy dependencies; follow-up #495 tracked archive-induced extra packages.
Resolution: closed resolved
Reason: PR #494 was approved and merged as dcdab592, adding Jammy's gcc-13-base and libgcc-s1 to the expected test results. Follow-up #495 concluded the extra packages came from mutable Ubuntu archive dependency changes and were expected behavior, not an AptCache bug.
Evaluated by: mr-cal-bot
No scores available.
Issue body
- [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
-----
This week, a unit test started [failing](https://github.com/canonical/craft-parts/actions/runs/5536668539/jobs/10119585228?pr=493#step:8:179) on the Ubuntu 22.04 CI runner:
```
FAILED tests/unit/packages/test_apt_cache.py::TestAptStageCache::test_stage_packages - AssertionError: assert ['gcc-13-base...', 'pciutils'] == ['libpci3', 'pciutils']
At index 0 diff: 'gcc-13-base' != 'libpci3'
Left contains 2 more items, first extra item: 'libpci3'
Full diff:
- ['libpci3', 'pciutils']
+ ['gcc-13-base', 'libgcc-s1', 'libpci3', 'pciutils']
```
I'm not sure what changed or if this is the right solution...
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged #494 as commit dcdab592, updating the AptCache stage-package test for Jammy dependencies; follow-up #495 tracked archive-induced extra packages. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged PR #494 updated the stage-package AptCache test for Jammy's extra dependencies, unblocking CI; further investigation was tracked in #495. | |
| qwen/qwen3.6-35b-a3b | — | — | Merged to fix a failing Ubuntu 22.04 CI test by adding jammy packages to the stage package apt cache. This unblocks other PRs while the underlying cache behavior is tracked for investigation in issue #495. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged to resolve a failing Ubuntu 22.04 CI unit test by adding jammy packages to the apt cache. The update unblocks dependent PRs, with further investigation deferred to issue #495. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/craft-parts#495
(confidence 100%)
Follow-up issue for investigating the Jammy dependency change; closed after it was identified as expected behavior.
-
Related To:
canonical/craft-parts#512
(confidence 95%)
Merged backport of the AptCache test update from #494.
-
Related To:
canonical/craft-parts#520
(confidence 95%)
Another merged backport of the Jammy AptCache test update.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #520 tests: add jammy packages to stage package apt cache (#494) | craft-parts | merged | Merged PR #520 backported the Jammy AptCache test update from #494 via commit dcdab5926, accounting for extra packages marked for installation on Jammy. | |
| #512 tests: add jammy packages to stage package apt cache (#494) | craft-parts | merged | Backport of #494 merged as dcdab592 (also e4f789fc/2d270ec5 on stable branches): added Jammy deps (gcc-13-base, libgcc-s1) to the AptCache stage-package test. With #511 it fixed the CI failure in #513. | |
| #495 AptCache is marking extra packages for installation on Jammy | craft-parts | closed | Test-only Jammy breakage (extra gcc-13-base/libgcc-s1 deps) was already patched by merged PR #494 (commit dcdab592); root-cause issue closed by cmatsuoka as inherent archive dynamism, not a resolver bug. |