Skip to content

Conversation

@rickyma
Copy link
Contributor

@rickyma rickyma commented May 23, 2024

What changes were proposed in this pull request?

We adjust the memory arguments refer to Spark's pom.xml:

-ea -Xmx4g -Xss4m -XX:MaxMetaspaceSize=2g -XX:ReservedCodeCacheSize=${CodeCacheSize} ${extraJavaTestArgs}

and make-distribution.sh:

export MAVEN_OPTS="${MAVEN_OPTS:--Xss128m -Xmx4g -XX:ReservedCodeCacheSize=128m}"

This is more reasonable.

Why are the changes needed?

Fix: #1698.
After #1726, I found that the issue may still exist.

Does this PR introduce any user-facing change?

No.

How was this patch tested?

Unnecessary.

@rickyma rickyma force-pushed the issue-1698-followup branch 2 times, most recently from f8f288e to 46ed754 Compare May 23, 2024 16:04
@rickyma rickyma force-pushed the issue-1698-followup branch from 46ed754 to 002f9c2 Compare May 23, 2024 16:09
@github-actions
Copy link

github-actions bot commented May 23, 2024

Test Results

 2 419 files  ±0   2 419 suites  ±0   4h 59m 59s ⏱️ + 2m 6s
   933 tests ±0     932 ✅ ±0   1 💤 ±0  0 ❌ ±0 
10 819 runs  ±0  10 805 ✅ ±0  14 💤 ±0  0 ❌ ±0 

Results for commit 28ab11c. ± Comparison against base commit a0e88da.

♻️ This comment has been updated with latest results.

@rickyma
Copy link
Contributor Author

rickyma commented May 23, 2024

@zuston @jerqi PTAL.

@zuston zuston merged commit 37d64a4 into apache:master May 28, 2024
zhengchenyu pushed a commit that referenced this pull request Aug 2, 2024
… tests (#1739)

### What changes were proposed in this pull request?

We adjust the memory arguments refer to Spark's [pom.xml](https://github.com/apache/spark/blob/master/pom.xml):
> -ea -Xmx4g -Xss4m -XX:MaxMetaspaceSize=2g -XX:ReservedCodeCacheSize=${CodeCacheSize} ${extraJavaTestArgs}

and [make-distribution.sh](https://github.com/apache/spark/blob/master/dev/make-distribution.sh):
> export MAVEN_OPTS="${MAVEN_OPTS:--Xss128m -Xmx4g -XX:ReservedCodeCacheSize=128m}"

This is more reasonable.

### Why are the changes needed?

Fix: #1698.
After #1726, I found that the issue may still exist.

### Does this PR introduce _any_ user-facing change?

No.

### How was this patch tested?

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

[Flaky Test] Tests fail because of VM crash

2 participants