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

mc does not always return non-zero status after errors #2112

Closed
ameir opened this issue Apr 5, 2017 · 1 comment · Fixed by #2127
Closed

mc does not always return non-zero status after errors #2112

ameir opened this issue Apr 5, 2017 · 1 comment · Fixed by #2127

Comments

@ameir
Copy link

ameir commented Apr 5, 2017

Expected behaviour

Return code should be non-zero

Actual behaviour

Return code is zero

Steps to reproduce the behaviour

$ mc cp -r /tmp/nutcracker-0.4.1/ minio/fake
mc: <ERROR> Failed to copy `/tmp/nutcracker-0.4.1/conf/nutcracker.yml`. Bucket `fake` does not exist.
mc: <ERROR> Failed to copy `/tmp/nutcracker-0.4.1/man/nutcracker.8`. Bucket `fake` does not exist.
mc: <ERROR> Failed to copy `/tmp/nutcracker-0.4.1/scripts/nutcracker.init`. Bucket `fake` does not exist.
mc: <ERROR> Failed to copy `/tmp/nutcracker-0.4.1/src/nutcracker`. Bucket `fake` does not exist.
$ echo $?
0

mc version

  • (paste output of mc version)
Version: 2017-04-03T18:35:01Z
Release-tag: RELEASE.2017-04-03T18-35-01Z
Commit-id: 81d17d28ec28987ba3c57349fc57b4c064bb5b37```
## System information


@lock
Copy link

lock bot commented Apr 25, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Apr 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants