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

rofiles-fuse: when fuse execution fails, rofiles-fuse still returns exit code 0 #3348

Merged
merged 1 commit into from
Dec 17, 2024

Conversation

qiuzhiqian
Copy link
Contributor

rofiles-fuse: Fixed the problem that when fuse execution fails, the command returns a status code of 0

testcase:
$ sudo rofiles-fuse a b
fuse: bad mount point `b': No such file or directory

$ echo $?
0

…ommand returns a status code of 0

testcase:
`$ sudo rofiles-fuse a b`
fuse: bad mount point `b': No such file or directory
`$ echo $?`
0
Copy link

openshift-ci bot commented Dec 3, 2024

Hi @qiuzhiqian. Thanks for your PR.

I'm waiting for a ostreedev member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@cgwalters cgwalters merged commit 08395e2 into ostreedev:main Dec 17, 2024
23 of 24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants