Bundle spread tests are failing
Metadata
Current evaluation
Bundle spread tests were fixed by merged PR #1287 (commit f60186ce), which validated YAML semantically and removed an obsolete charm-path assertion.
Resolution: closed resolved
Reason: PR #1287 merged as f60186ce and explicitly resolved #1262. It validates generated bundle YAML with Python and drops the charm-path check because equivalent bundles use different valid path values.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### What needs to get done
Figure out why and fix the tests. It looks like it's just because of yaml formatting differences.
https://github.com/canonical/charmcraft/actions/runs/6210409286/job/16858681409
- [ ] google:ubuntu-22.04-64:tests/spread/charms/bundle:argo
- [ ] google:ubuntu-22.04-64:tests/spread/charms/bundle:istio
- [ ] google:ubuntu-22.04-64:tests/spread/charms/bundle:kfp
- [ ] google:ubuntu-22.04-64:tests/spread/charms/bundle:notebook_operators
### Why it needs to get done
They used to succeed, so this may be an introduced regression
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Bundle spread tests were fixed by merged PR #1287 (commit f60186ce), which validated YAML semantically and removed an obsolete charm-path assertion. | |
| stealth/space-bunny-alpha | — | closed stale | Closed after investigation reported successful bundle builds but a remaining YAML charm-path mismatch; no resolving PR or commit is identified. | |
| stealth/space-bunny-alpha | — | closed stale | Bundle spread tests remained failing because bundles used charm names instead of `charm: ${PWD}`; the reported YAML changes did not resolve the incompatibility. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Abandoned after identifying that failures stemmed from YAML formatting changes and mismatched charm reference expectations. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. Abandoned after identifying YAML formatting differences and test expectation mismatches. Tests failed due to relative path vs explicit charm reference conflicts. | |
| qwen/qwen3.6-35b-a3b | — | — | Fixed by updating test expectations to match YAML formatting changes and ch: charm references, resolving the regression. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed after determining test failures were false positives caused by YAML formatting changes and a task.yaml configuration mismatch using explicit charm references instead of ${PWD}. No code fix required. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/charmcraft#1287
(confidence 100%)
Merged fix for #1262, committed as f60186ce.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1287 fix(tests): fixes bundle spread test | charmcraft | merged | Merged PR #1287 (commit f60186ce, CRAFT-2052) fixed the failing bundle spread test by validating YAML with Python and dropping a non-working charm path check, resolving #1262. | |
| #1266 tests(spread): requirements dependencies | charmcraft | merged | Merged PR #1266 at 97d95b39, adding spread tests for requirements-file and charm-dependency combinations; the PR explicitly fixes #1179. | |
| #1324 test(spread): test-deploy charms in large spread tests | charmcraft | merged | Merged PR #1324 via commit a14d6d91, adding test deployment of charms and bundles to large Spread tests. | |
| #1556 refactor(tests/spread): test with explicit charmcraft.yaml files | charmcraft | merged | Merged PR #1556 in commit 4682b32b, replacing prepare-step manipulation of charmcraft.yaml with explicit spread-test configuration files. | |
| #1469 Charm upload/release spread test is flaky | charmcraft | closed | Fixed the flaky store spread test by waiting and retrying release checks; merged in canonical/charmcraft#1460 (fd5bd6ba). | |
| #1555 refactor(tests/spread): stop use init in most spread tests | charmcraft | closed | Closed unmerged and replaced by PR #1556, merged as commit 4682b32b, which updated Spread tests to use explicit charmcraft.yaml files instead of charmcraft init. | |
| #1217 tests: add more charms and bundles to large spread suite | charmcraft | merged | Merged #1217 as commit 0f4591a9, expanding the large spread suite with more charms and bundles to broaden breaking-change coverage. | |
| #291 Refactor spread testing to use spread extensions | fetch-service | closed | Fixed by merged PR #299 (commit 44d9906), which refactored spread tests to generate spread.yaml and use the new spread extension framework. | |
| #1855 Disable bundle registration spread test | charmcraft | closed | Disabled the obsolete bundle-registration spread test in PRs #1860 and #1884, commits c5f0ba23 and d2fcbfd5. | |
| #1849 tests(2.7): remove mantic spread test | charmcraft | merged | Merged PR #1849 removed the EOL Mantic spread test, restoring CI for Charmcraft 2.7 bugfix releases. |