It's not possible to run only one autopkgtest
Metadata
Current evaluation
⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.
Abandoned. The request to run individual autopkgtest suites separately was closed without resolution, zero comments, and no fix or merge. The integration and snaps_tests separation remains unimplemented.
Suggested action: —
No scores available.
Issue body
We have two autopkgtest suites: integration and snaps_tests.
I would be good to be able to trigger them sepparately, some times we will only want to run the integration tests, some other times we will like only the snaps tests.
This should be possible now: https://bugs.launchpad.net/auto-package-testing/+bug/1641831
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | Abandoned. The request to run individual autopkgtest suites separately was closed without resolution, zero comments, and no fix or merge. The integration and snaps_tests separation remains unimplemented. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without implementation or resolution. The request to run individual autopkgtest suites separately was abandoned due to inactivity. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. The request to run integration and snaps_tests autopkgtest suites separately was abandoned, with no comments or implementation recorded. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1200 tests: allow to run individual autopkgtest suites | snapcraft | merged | Merged implementation enabling execution of individual autopkgtest suites. Resolves Launchpad bug #1673981. Updated one test file with 17 additions and 13 deletions to support selective suite execution. | |
| #1596068 The unittests in autopkgtest are run twice | snapcraft (launchpad) | closed | Autopkgtest configuration updated to skip unit tests already executed during package builds. Only integration and snaps suites now run, eliminating redundant execution and improving developer build times. Resolved and verified. | |
| #1640276 There is no way to retry a snapcraft autopkgtest run | snapcraft (launchpad) | closed | Closed without resolution. The request for a built-in autopkgtest retry mechanism was abandoned or superseded by newer CI infrastructure. |