Skip to content

fix: keep a check's level when a merged layer doesn't set one - #2895

Open
aozmekik wants to merge 1 commit into
canonical:mainfrom
aozmekik:check-merge-keeps-level
Open

aozmekik wants to merge 1 commit into
canonical:mainfrom
aozmekik:check-merge-keeps-level

Conversation

@aozmekik

Copy link
Copy Markdown

Fixes #2894 (the check level part).

Check._merge skipped an unset startup but not an unset level, so merging a layer that doesn't mention level reset it to CheckLevel.UNSET. Pebble only takes the level from the merged layer when it's set, so this skips CheckLevel.UNSET the same way.

test_merge_keeps_level fails on main and passes here; tox -e lint and tox -e unit pass.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Harness plan doesn't match Pebble's when merging layers: repeated list entries and a lost check level

1 participant