Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bring back kernel/snapd/gadget snaps revert/refresh jobs to the SRU test plan (BugFix) #1176

Merged
merged 1 commit into from
Apr 11, 2024

Conversation

pieqq
Copy link
Collaborator

@pieqq pieqq commented Apr 11, 2024

Description

The snap-refresh-revert nested part had been removed from the SRU test plan in cd17d9a following some discoveries that, when executed, the jobs executed would change the system state in the wrong order (e.g. updating the kernel snap without reverting it while running other jobs afterwards).

The jobs were modified to prevent this kind of scenario, and the use of manifest entries prevents the jobs from being run on all the devices yet (currently, the only project that enables them is the Xinyi project).

Resolved issues

Fix LM-1522

Documentation

Tests

Tested on Xinyi with a local build of Checkbox.

…est plan

The snap-refresh-revert nested part had been removed from the SRU test
plan in cd17d9a following some
discoveries that, when executed, the jobs executed would change the
system state in the wrong order (e.g. updating the kernel snap without
reverting it while running other jobs afterwards).

The jobs were modified to prevent this kind of scenario[1], and the use
of manifest entries[2] prevents the jobs from being run on all the
devices yet (currently, the only project that enables them is the Xinyi
project).

Fix LM-1522

[1] #1124
[2]
https://github.com/canonical/checkbox/tree/main/providers/base/units/snapd#manifest-entries
Copy link

codecov bot commented Apr 11, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 43.15%. Comparing base (3789fdd) to head (346f61d).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1176   +/-   ##
=======================================
  Coverage   43.15%   43.15%           
=======================================
  Files         355      355           
  Lines       38627    38627           
  Branches     6556     6556           
=======================================
  Hits        16668    16668           
  Misses      21294    21294           
  Partials      665      665           
Flag Coverage Δ
provider-sru 100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

@kissiel kissiel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's go!
+1

@pieqq pieqq merged commit 18d9bd8 into main Apr 11, 2024
13 checks passed
@pieqq pieqq deleted the LM-1522-re-enable-snap-refresh-revert-sru branch April 11, 2024 09:42
LiaoU3 pushed a commit to LiaoU3/checkbox that referenced this pull request Apr 17, 2024
…est plan (BugFix) (canonical#1176)

Bring back kernel/snapd/gadget snaps revert/refresh jobs to the SRU test plan

The snap-refresh-revert nested part had been removed from the SRU test
plan in cd17d9a following some
discoveries that, when executed, the jobs executed would change the
system state in the wrong order (e.g. updating the kernel snap without
reverting it while running other jobs afterwards).

The jobs were modified to prevent this kind of scenario[1], and the use
of manifest entries[2] prevents the jobs from being run on all the
devices yet (currently, the only project that enables them is the Xinyi
project).

Fix LM-1522

[1] canonical#1124
[2]
https://github.com/canonical/checkbox/tree/main/providers/base/units/snapd#manifest-entries
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.

2 participants