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

Don't use runInSeparateProcess #28676

Merged
merged 2 commits into from
Aug 15, 2017
Merged

Don't use runInSeparateProcess #28676

merged 2 commits into from
Aug 15, 2017

Conversation

DeepDiver1975
Copy link
Member

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

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

Copy link
Contributor

@PVince81 PVince81 left a 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);
Copy link
Contributor

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

Copy link
Member Author

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 ....

Copy link
Contributor

@PVince81 PVince81 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@PVince81 PVince81 merged commit 0ea3ed6 into master Aug 15, 2017
@PVince81 PVince81 deleted the no-runInSeparateProcess branch August 15, 2017 15:14
@PVince81
Copy link
Contributor

@DeepDiver1975 please backport

@DeepDiver1975
Copy link
Member Author

Will do asap

@lock
Copy link

lock bot commented Aug 2, 2019

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 Aug 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants