Skip to content

Conversation

@sarutak
Copy link
Member

@sarutak sarutak commented Jul 9, 2015

spark.unsafe.exceptionOnMemoryLeak is present in the config of surefire.

        <!-- Surefire runs all Java tests -->
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-surefire-plugin</artifactId>
          <version>2.18.1</version>
          <!-- Note config is repeated in scalatest config -->
...

<spark.unsafe.exceptionOnMemoryLeak>true</spark.unsafe.exceptionOnMemoryLeak>
            </systemProperties>
...

but is absent in the config ScalaTest.

@JoshRosen
Copy link
Contributor

LGTM pending Jenkins.

@andrewor14
Copy link
Contributor

LGTM

@SparkQA
Copy link

SparkQA commented Jul 9, 2015

Test build #36877 has finished for PR 7308 at commit 95644e7.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@sarutak
Copy link
Member Author

sarutak commented Jul 9, 2015

Merging into master and branch-1.4.

asfgit pushed a commit that referenced this pull request Jul 9, 2015
…s missing in ScalaTest config.

`spark.unsafe.exceptionOnMemoryLeak` is present in the config of surefire.

```
        <!-- Surefire runs all Java tests -->
        <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-surefire-plugin</artifactId>
          <version>2.18.1</version>
          <!-- Note config is repeated in scalatest config -->
...

<spark.unsafe.exceptionOnMemoryLeak>true</spark.unsafe.exceptionOnMemoryLeak>
            </systemProperties>
...
```

 but is absent in the config ScalaTest.

Author: Kousuke Saruta <[email protected]>

Closes #7308 from sarutak/add-setting-for-memory-leak and squashes the following commits:

95644e7 [Kousuke Saruta] Added a setting for memory leak

(cherry picked from commit aba5784)
Signed-off-by: Kousuke Saruta <[email protected]>
@asfgit asfgit closed this in aba5784 Jul 9, 2015
@sarutak sarutak deleted the add-setting-for-memory-leak branch April 12, 2016 13:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants