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.71%
=======================================
Files 3 3
Lines 502 502
=======================================
Hits 360 360
Misses 142 142 ☔ 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=2026072219-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 tests14 failures
Fixed failuresCompared to: https://openqa.qubes-os.org/tests/176874#dependencies 27 fixed
Unstable testsDetails
Performance TestsPerformance degradation:42 performance degradations
Remaining performance tests:69 tests
|
| systemctl daemon-reload | ||
| if command -v zramctl >/dev/null; then | ||
| zramctl -r zram0 | ||
| zramctl -r zram0 || true # Elide unnecessary failure when no zram devices are setup. |
There was a problem hiding this comment.
What about checking if /dev/zram0 exists first?
|
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.
|
Elide unnecessary failure when no zram devices are setup.