-
Notifications
You must be signed in to change notification settings - Fork 27
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
improve error handling 2 #248
Conversation
because these are now covered by the error_handler
No need to use both, `eend 1` and `bailout 1`. In these cases, only `bailout 1` is sufficient.
only delete `$MNTPOINT` if such a folder actually exists
only delete `$MNTPOINT` if such a folder actually exists
because these are now covered by the new error handling method
because it will not always work will not work in cases where /dev etc is still mounted inside the chroot
Seems like an upstream issue as per microsoft/WSL#10450 Previously without strict error handling, the CI simply didn't notice this issue. Solutions:
|
to work around an issue by github actions
to work around an issue by github actions
Done. New issue. The following command has a non-zero exit code:
Any idea why that might be? |
This blkid related bug probably:
Can I ignore it for the purpose of this PR and create a follow-up issue instead? This is what I'll do for now so I can progress with further testing. |
blkid issue...
Done. Now, the CI is mostly passing except for the builds of Debian stretch are failing.
Not sure if this is an intermittent issue because Debian jessie does not have this issue? Potential solutions:
Quote https://wiki.debian.org/DebianStretch
|
#231