spread: bump storage for Google 22.04 spread hosts
Metadata
Current evaluation
Merged #4102 in commit 2868dd12c, increasing storage for Google 22.04 Spread hosts to address insufficient disk space.
Resolution: closed resolved
Reason: PR #4102 was approved and merged as commit 2868dd12c, raising the configured storage for Google 22.04 Spread hosts. A separate kill-timeout failure was handled by #4108.
Evaluated by: mr-cal-bot
No scores available.
Issue body
- [x] Have you followed the [guidelines for contributing](https://github.com/snapcore/snapcraft/blob/master/CONTRIBUTING.md)?
- [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)?
- [x] Have you successfully run `make lint`?
- [x] Have you successfully run `pytest tests/unit`?
-----
Looks like the spread tests on 22.04 are failing due to insufficient storage (see: https://github.com/snapcore/snapcraft/actions/runs/4708550869/jobs/8352897128). The default is 10 gigs.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Merged #4102 in commit 2868dd12c, increasing storage for Google 22.04 Spread hosts to address insufficient disk space. | |
| stealth/space-bunny-alpha | — | closed resolved | Merged #4102 as 2868dd12c, raising storage for Google 22.04 Spread hosts. The reported kill-timeout failure was addressed separately by #4108 (945e5bade). | |
| qwen/qwen3.6-35b-a3b | — | — | Merged to increase Google 22.04 spread host storage, resolving test failures. Approved by two reviewers with passing CI. The author clarified the actual failure stems from a kill timeout to be fixed separately. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Merged to increase storage allocation for Google 22.04 spread hosts, resolving test failures caused by insufficient disk space. A separate PR handles a related kill timeout. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/snapcraft#4108
(confidence 95%)
Merged as 945e5bade to increase the Spread kill timeout for a separate intermittent timeout failure.
Related issues
No related issues found above the similarity threshold.