Run documentation spread tests in CI
Metadata
Current evaluation
Maintainer task to create a CI job for docs spread tests. The workflow (spread-docs.yaml) now exists and runs on PRs/pushes/weekly. The google backend failure reported by @erinecon was addressed by switching backends. Issue remains open but work appears complete.
Suggested action: close stale
Reason: The CI job was implemented in PR #2126 (commit f1b73a6e 'ci(docs): spread test documentation') and the .github/workflows/spread-docs.yaml file is active, running on PRs, pushes to main, and weekly. The google backend failure @erinecon reported was resolved by PR #2338 ('docs: replace google for ci and fix tests') and PR #2783 ('ci: use openstack for spread'). No activity in 381 days and the original task is no longer applicable.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
24.0
Staleness:
75
Complexity:
40
Confidence:
72
Support Request:
5
|
close stale | Maintainer task to create a CI job for docs spread tests. The workflow (spread-docs.yaml) now exists and runs on PRs/pushes/weekly. The google backend failure reported by @erinecon was addressed by switching backends. Issue remains open but work appears complete. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
50
Confidence:
75
Support Request:
10
|
needs triage | Task to enable CI for documentation spread tests. Currently disabled due to runtime. Contributor reported CI-specific failures vs local, but issue remains unlabelled and inactive for over a year. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
65
Confidence:
80
Support Request:
10
|
close stale | Request to create a CI job for documentation spread tests. Currently blocked by CI backend differences causing postgresql-k8s deployment and flask app integration failures. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
50
Complexity:
50
Confidence:
75
Support Request:
10
|
keep open | Create a CI job to run documentation spread tests. Currently blocked by CI backend integration failures with the google backend, with recent debugging activity in January 2025. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
75
Complexity:
45
Confidence:
85
Support Request:
10
|
needs triage | Add CI job to run documentation spread tests. Tests pass locally but fail in GitHub CI due to postgresql-k8s charm deployment and integration timeouts on the google backend. Issue remains open and awaiting investigation. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/charmcraft#2126
(confidence 85%)
Commit f1b73a6e 'ci(docs): spread test documentation' created the spread-docs.yaml workflow that runs docs spread tests in CI, directly fulfilling this issue's request.
-
Related To:
canonical/charmcraft#2338
(confidence 70%)
Replaced google backend in CI and fixed tests, addressing the specific failure @erinecon reported in the issue comments.
-
Related To:
canonical/charmcraft#2783
(confidence 60%)
Further CI backend change to use openstack for spread tests, continuing the evolution of the docs spread CI setup.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #2126 ci(docs): spread test documentation | charmcraft | merged | Merged changes adding a CI workflow for spread testing documentation and adjusting tasks for Google runners. Approved by two reviewers, the update modifies five files (+100/-22 lines) and resolves CRAFT-3798. | |
| #2338 docs: replace google for ci and fix tests | charmcraft | merged | Merged after approval. Replaced Google CI with self-hosted GitHub runners for spread-docs, updated test configurations for prepare/restore and retries, and adjusted spread doc tests. CI passed with minor policy exceptions. | |
| #143 docs: make docs spread-testable | craft-store | merged | Merged documentation spread-testing infrastructure setup. Approved by two reviewers and passing CI, the change modifies six files (+136/-41 lines) to enable local spread test execution for documentation. |