tests: run integration tests on trusty
Metadata
Current evaluation
Closed unmerged; superseded by snapcraft#2013, which also closed unmerged, so native Trusty integration tests were never added.
Resolution: closed superseded
Reason: The container-based proposal was replaced by snapcraft#2013's native Travis approach. #2013 also closed unmerged, so the proposed Trusty test changes never landed.
Evaluated by: mr-cal-bot
No scores available.
Issue body
- [x] Have you followed the [guidelines for contributing](https://github.com/snapcore/snapcraft/blob/master/CONTRIBUTING.md)?
- [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [x] If this is a bugfix. Have you checked that there is a bug report open for the issue you are trying to fix on [bug reports](https://bugs.launchpad.net/snapcraft)?
- [x] If this is a new feature. Have you discussed the design on the [forum](https://forum.snapcraft.io)?
- [x] Have you successfully run `./runtests.sh static`?
- [x] Have you successfully run `./runtests.sh unit`?
-----
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed superseded | Closed unmerged; superseded by snapcraft#2013, which also closed unmerged, so native Trusty integration tests were never added. | |
| stealth/space-bunny-alpha | — | closed stale | Closed unmerged after the Trusty container approach failed on missing squashfuse and native Trusty Travis infrastructure was unavailable. | |
| stealth/space-bunny-alpha | — | closed stale | PR #2013 was closed unmerged; native Trusty integration testing and its compatibility changes were never added to run_tests.sh. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without merging. The Trusty integration test setup was abandoned due to missing squashfuse dependencies and CI container limitations. The team confirmed native Travis runners are needed, but no further action was taken. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Abandoned and closed due to missing Trusty dependencies and LXC container limitations. The team decided to use native Travis runners instead of containers for integration testing. |
Update history
No update history recorded yet.
Related work
-
Superseded By:
snapcraft#2013
(confidence 98%)
Revised native Trusty testing proposal; closed unmerged.
-
Related To:
snapcraft#2011
(confidence 90%)
Another Trusty-on-Travis proposal was also closed unmerged.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2013 tests: run tests on Trusty on Travis | snapcraft | closed | Closed unmerged; native Trusty Travis testing and optional image support never landed. Related PR canonical/snapcraft#2011 was also closed unmerged. | |
| #2011 tests: run tests on Trusty on Travis | snapcraft | closed | Closed unmerged; snapcraft#2013 proposed the same native Trusty Travis coverage and Python 3.4 compatibility updates, but none landed. | |
| #1625 tests: use the snapcraft snap for integration tests | snapcraft | merged | Merged PR #1625 updated integration tests to run the installed Snapcraft snap, better matching the user environment. Resolution: commit eebb070e6. | |
| #1877 tests: move test files out of the snapcraft dir | snapcraft | closed | Closed unmerged after conflicts; the test reorganization was redone and merged via snapcraft#1948 at commit 55ad11ccc, moving tests out of the snapcraft package. | |
| #1716 tests: split the integration autopkgtests | snapcraft | merged | Merged in snapcraft#1716 via 57af155a7, splitting integration autopkgtests into separate runs to prevent timeout failures despite added setup overhead. |