-
Notifications
You must be signed in to change notification settings - Fork 1.9k
IGNITE-13551 .NET: Enable ClientServerCompatibilityTest on Linux #8331
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
Conversation
isapego
left a comment
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.
| if (process != null) | ||
| throw new Exception("PlatformProcessUtils can't start more than one process at a time."); |
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.
Is this a limitation, or do we just not need several processes right now and this was the simpliest implementation?
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.
It would be great to return PID and then use it to kill the process. Unfortunately, Process.pid() was only added in Java 9, and we have to be able to run on Java 8.
So yes, this is a simplification - good enough for tests.
Use Java code to start and stop processes to avoid SIGCHLD conflicts.
Java and .NET both install SIGCHLD handler to deal with child processes. Since Ignite direct-io already uses Java process API, we can't use .NET process API in tests.