-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Don't use runInSeparateProcess #28676
Conversation
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.
Hmm ok 👍
@@ -351,7 +355,7 @@ public function testPutSingleFile() { | |||
* @return boolean true if negative mtime is supported | |||
*/ | |||
private function supportsNegativeMtime() { | |||
return (getenv("PRIMARY_STORAGE_CONFIG") !== "swift"); | |||
return !(getenv("RUN_OBJECTSTORE_TESTS") !== false); |
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 clear as mud to you?
having the 2 "!" - I guess the construction !== false
is a way of saying "if true" -> "if RUN_OBJECTSTORE_TESTS" and then the "!" at the front negates that.
but it messes my brain a bit
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.
but it messes my brain a bit
me too .... I need to understand the initial logic as well ... see rocket chat ....
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.
👍
@DeepDiver1975 please backport |
Will do asap |
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. |
Description
There is not need in running a test in a separate process ....
Motivation and Context
Clean code, better unit test execution
Types of changes
Checklist: