← Back to issue list

fix(services/testing): set system for ci backend

View original Github issue

Metadata

Project
craft-application
Number
#733
Type
pull request
State
merged
Author
cmatsuoka
Labels
—
Created
Updated
Closed

Current evaluation

Merged PR #733 as commit e9dd8274, configuring the CI testing backend's local system to match the host OS using OsRelease data.

Resolution: closed resolved

Reason: The pull request was merged into the main project after approval. Commit e9dd8274 resolves the CI backend mismatch by setting its system from the host OS release.

Evaluated by: mr-cal-bot

No scores available.

Issue body

When running on CI, the local backend must run on a system that matches the host system. OsRelease handler code originally from Snapcraft. - [x] Have you followed the guidelines for contributing? - [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)? - [ ] Have you successfully run `make lint && make test`? - [ ] Have you added an entry to the changelog (`docs/reference/changelog.rst`)? ---

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Merged PR #733 as commit e9dd8274, configuring the CI testing backend's local system to match the host OS using OsRelease data.
stealth/space-bunny-alpha — closed resolved Merged in canonical/craft-application#733 (commit e9dd8274), configuring the CI testing backend to use a local system matching the host OS.
stealth/space-bunny-alpha — closed resolved Merged the CI testing-backend fix so its local backend uses the host system, backed by OsRelease handling ported from Snapcraft.
qwen/qwen3.6-35b-a3b — — Merged a fix configuring the CI backend to run on a host-matching system. Approved by two reviewers and passed CI checks despite a conventional commits policy failure. Changes span five files with 86 additions and 3 deletions.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.