-
Notifications
You must be signed in to change notification settings - Fork 142
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
lvm2: Refactor udisks_daemon_util_lvm2_wipe_block() #1212
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
Legacy code, most of the stuff is now offered by the current API.
bfef065
to
4a73a1f
Compare
Cockpit tests failed for commit 4a73a1f. @martinpitt, @jelly, @mvollmer please check. |
The testTeardownRetry rawhide failure is worth retrying ( |
Okay, let's see. It's great that to have this caught by the reverse tests!
Would be interesting to dump the state of block devices after such failure. |
/packit retest-failed |
@tbzatek That's actually our bug. The generic "after failure" cleanup (with the umount/dmsetup remove etc.) failed because
So we have to make the test robust against that, so that the automatic retry has a chance of working. The initial failure was a timeout in the UI. I'll look into that in the next days, sorry for the trouble. The cockpit test is green now, so not blocked by us (of course a lot of other tests are red) |
Oh no worries, it's valuable to see how your testing framework works. Let's merge this then and keep an eye on any related failures. |
Sent cockpit-project/cockpit#19605 to robustify this. |
Legacy code, most of the stuff is now offered by the current API.
Fixes #900