← Back to issue list

Use a xenial docker container for travis executions

View original Github issue

Metadata

Project
snapcraft
Number
#597
Type
pull request
State
merged
Author
come-maiz
Labels
—
Created
Updated
Closed

Current evaluation

Switched Travis CI to a Xenial Docker container. Merged after tests passed despite a timeout and coverage failure requiring dependency #598.

Suggested action: —

No scores available.

Issue body

No description provided.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b — — Switched Travis CI to a Xenial Docker container. Merged after tests passed despite a timeout and coverage failure requiring dependency #598.
qwen3.6-35b-a3b-mtp-q6 — — Merged after updating Travis CI to use a Xenial Docker container. All tests passed despite a cleanup timeout. Coverage failures were resolved by depending on PR #598.
qwen3.6-35b-a3b-mtp-q6 — — Switched Travis CI to a Xenial Docker container. Unit, integration, and snap tests passed despite an autopkgtest cleanup timeout. Coverage failures were fixed. Merged, requiring PR #598.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#2392 ci: update travis.yaml to use xenial snapcraft merged Merged into master, updating .travis.yml to use Ubuntu Xenial. The configuration change increased overall code coverage by 0.07%.
71%
#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.
70%