← Back to issue list

test: use tics self-hosted runner

View original Github issue

Metadata

Project
fetch-service
Number
#431
Type
pull request
State
merged
Author
cmatsuoka
Labels
—
Created
Updated
Closed

Current evaluation

Merged as commit d3e9aaa, updating the TICS workflow to use self-hosted reactive amd64 runners with Tiobe and Noble labels.

Resolution: closed resolved

Reason: PR fetch-service#431 was merged with commit d3e9aaa. The one-line workflow change enabled TICS on self-hosted runner labels, and all reported CI checks passed.

Evaluated by: mr-cal-bot

No scores available.

Issue body

- [ ] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)? -----

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Merged as commit d3e9aaa, updating the TICS workflow to use self-hosted reactive amd64 runners with Tiobe and Noble labels.
stealth/space-bunny-alpha — closed resolved Merged in canonical/fetch-service#431, configuring tests to use the TICS self-hosted runner. The maintainer confirmed merging it into the tiobe branch after syncing with main.
qwen/qwen3.6-35b-a3b — — Merged into the tiobe branch after syncing with main. The update configures tests to use a self-hosted runner. Approved by two reviewers with all CI checks passing.

Update history

Date Change
created

Related issues

Issue Project State Summary Similarity
#52 fix: use self hosted runner for tics starflow merged Merged PR #52 via commit 528ee7f, moving TICS CI to a self-hosted runner where Charmcraft's LXD-dependent tests work.
76%
#61 fix: use the tiobe runners as proposed by security starflow merged Merged PR canonical/starflow#61 (commit 1237e85), switching the TICS CI job to the security-proposed self-hosted TIOBE Noble runner.
75%
#193 ci: enable Tiobe TiCS fetch-service merged Merged PR #193 (commit 7e7a247) added .github/workflows/tics.yaml, enabling Tiobe TiCS qserver CI on self-hosted Tiobe runners; approved by 2 reviewers and closing fetch-service#115 (CRAFT-3012).
74%
#652 Fix TICS runner fetch-service closed Issue reporting broken TICS runner closed, superseded by subsequent CI workflow updates including PR #654.
71%