The unittests in autopkgtest are run twice
Metadata
Current evaluation
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.
Suggested action: —
No scores available.
Issue body
By the time autopkgtests are run, the package has already been built. In order to build the package, the unittests are executed. So by running them in autopkgtest, we are duplicating the work.
In addition to that, autopkgtest is intended to run as installed. The unit tests are white box importing the source modules.
We have to run only integration and snaps suites in autopkgtest.
[Impact]
* For users, none.
* For developers, faster execution times because unit tests are run only once.
[Test Case]
* N/A
[Regression Potential]
* None.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | — | 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. | |
| qwen/qwen3.6-35b-a3b | — | — | Resolved and verified. Autopkgtest configuration was updated to exclude unit tests, running only integration and snaps suites. This eliminates redundant execution during the build phase and reduces developer test times. | |
| qwen/qwen3.6-35b-a3b | — | — | Autopkgtest configuration updated to skip unit tests already executed during package building. Only integration and snaps suites now run in autopkgtest, eliminating duplicate execution and improving build times. Resolved and verified. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #600 Remove the unittests from the autopkgtest execution | snapcraft | merged | Merged to prevent duplicate unittest execution by removing tests from autopkgtest, as they already run during the build phase. Resolved LP #1596068. CI passed after resolving external execution delays. | |
| #1570992 autopkgtests are running snapcraft from source | snapcraft (launchpad) | closed | Fixed and verified. Autopkgtests now install and execute against the built deb package instead of source, ensuring realistic testing conditions with no regression. | |
| #164 Updated the autopkgtests. | snapcraft | merged | Merged autopkgtests update running integration tests, building examples without installing, and skipping redundant unittests. Approved by @kyrofa, changes optimize execution by deferring unittests to package builds and scheduling example tests for daily runs and PRs. | |
| #2380 tests: use autopkgtest to leverage snap testing | snapcraft | merged | Merged. Updates the test suite to use autopkgtest for snap testing, modifying 31 files and reducing 137 lines. Changes were integrated into the main branch after passing CI checks. | |
| #1673981 It's not possible to run only one autopkgtest | snapcraft (launchpad) | closed | 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. | |
| #1716 tests: split the integration autopkgtests | snapcraft | merged | Merged after splitting integration autopkgtests to eliminate timeout failures. The change adds minor per-test setup overhead but resolves recurring execution timeouts. Approved by two reviewers with passing CI checks. |