Handle zramctl command failure gracefully - #661
Conversation
Elide unnecessary failure when no zram devices are setup.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #661 +/- ##
==========================================
- Coverage 71.71% 71.31% -0.40%
==========================================
Files 3 3
Lines 502 502
==========================================
- Hits 360 358 -2
- Misses 142 144 +2 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
OpenQA test summaryComplete test suite and dependencies: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2026082421-devel&flavor=pull-requests Test run included the following:
New failures, excluding unstableCompared to: https://openqa.qubes-os.org/tests/overview?distri=qubesos&version=4.3&build=2026050504-devel&flavor=update
Failed tests7 failures
Fixed failuresCompared to: https://openqa.qubes-os.org/tests/176874#dependencies 31 fixed
Unstable testsDetails
Performance TestsPerformance degradation:16 performance degradations
Remaining performance tests:95 tests
|
|
That would be a good idea. I am not at a console logged into GH to do this right now, and won't be for several days.
|
Ensure /dev/zram0 exists before attempting to disable it.
Elide unnecessary failure when no zram devices are setup.