← Back to issue list

ci: update travis.yaml to use xenial

View original Github issue

Metadata

Project
snapcraft
Number
#2392
Type
pull request
State
merged
Author
sergiusens
Labels
—
Created
Updated
Closed

Current evaluation

Merged into master, updating .travis.yml to use Ubuntu Xenial. The configuration change increased overall code coverage by 0.07%.

Suggested action: —

No scores available.

Issue body

Signed-off-by: Sergio Schvezov <sergio.schvezov@canonical.com> - [ ] Have you followed the [guidelines for contributing](https://github.com/snapcore/snapcraft/blob/master/CONTRIBUTING.md)? - [ ] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)? - [ ] 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)? - [ ] If this is a new feature. Have you discussed the design on the [forum](https://forum.snapcraft.io)? - [ ] Have you successfully run `./runtests.sh static`? - [ ] Have you successfully run `./runtests.sh tests/unit`? -----

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b — — Merged into master, updating .travis.yml to use Ubuntu Xenial. The configuration change increased overall code coverage by 0.07%.
qwen3.6-35b-a3b-mtp-q6 — — Merged into master, updating the Travis CI configuration to use Ubuntu Xenial. The change passed CI checks and increased test coverage by 0.07%.
qwen3.6-35b-a3b-mtp-q6 — — Merged into master, updating the Travis CI configuration to use Ubuntu Xenial. The change increased overall test coverage by 0.07%.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1532213 Run the tests in xenial snapcraft (launchpad) closed Travis CI was updated to run tests on Ubuntu Xenial. The change was implemented, verified, and the issue closed.
71%
#597 Use a xenial docker container for travis executions snapcraft merged Switched Travis CI to a Xenial Docker container. Merged after tests passed despite a timeout and coverage failure requiring dependency #598.
71%