-
Notifications
You must be signed in to change notification settings - Fork 432
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
Test case in ExternalCommandTest failing on MacOS #3006
Comments
@rohanKanojia Should it be disabled on MacOS as well as Windows? |
@arman-yekkehkhani : Okay, let's disable it on MacOS. Also, I would add an equivalent test for MacOS ( |
@rohanKanojia Thx! Could you assign it to me? I can make a PR for that. |
Maybe we can just check that the exit code is not 0 which will work in both OSs |
Or just modify the command for something that's cross-os (*nix/bsd) compatible. |
…ode, issue eclipse-jkube#3006 Signed-off-by: arman-yekkehkhani <arman.yekkehkhani@gmail.com>
…ndTest, issue #3006 Signed-off-by: arman-yekkehkhani <arman.yekkehkhani@gmail.com>
…ndTest, issue eclipse-jkube#3006 Signed-off-by: arman-yekkehkhani <arman.yekkehkhani@gmail.com>
Describe the bug
When running test
execute_whenCommandFailed_thenThrowException
in classExternalCommandTest
on MacOS, it fails. It does not happen on Ubuntu. The reason for that is the inconsistent behaviour of commandls
in the occasion of failure on these operating systems.If we try to run
ls
in GNU with a nonexistent file as an argument, it fails with exit code 2:While on MacOS, the exit code is 1:
Eclipse JKube version
SNAPSHOT
Component
JKube Kit
Apache Maven version
None
Gradle version
None
Steps to reproduce
ExternalCommandTest
execute_whenCommandFailed_thenThrowException
will failExpected behavior
Either the test case should be platform-independent or disabled on MacOS (like Windows)
Runtime
other (please specify in additional context)
Kubernetes API Server version
1.25.3
Environment
macOS
Eclipse JKube Logs
No response
Sample Reproducer Project
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: