fix: replace Unrecognized VM option MaxPermSize with MaxMetaspaceSize#3759
Merged
aceforeverd merged 1 commit into4paradigm:mainfrom Feb 21, 2024
Merged
fix: replace Unrecognized VM option MaxPermSize with MaxMetaspaceSize#3759aceforeverd merged 1 commit into4paradigm:mainfrom
aceforeverd merged 1 commit into4paradigm:mainfrom
Conversation
replace Unrecognized VM option MaxPermSize with MaxMetaspaceSize and upgrade openmldb-batchjob maven.compiler.source and maven.compiler.target to 1.8
Contributor
SDK Test Report101 files 101 suites 2m 4s ⏱️ For more details on these failures, see this check. Results for commit 73991d5. ♻️ This comment has been updated with latest results. |
Contributor
Linux Test Report 57 files 244 suites 1h 19m 40s ⏱️ Results for commit 73991d5. ♻️ This comment has been updated with latest results. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3759 +/- ##
=============================================
+ Coverage 40.15% 78.18% +38.02%
=============================================
Files 194 542 +348
Lines 11426 120645 +109219
Branches 1378 0 -1378
=============================================
+ Hits 4588 94325 +89737
- Misses 6535 26320 +19785
+ Partials 303 0 -303 ☔ View full report in Codecov by Sentry. |
vagetablechicken
approved these changes
Feb 20, 2024
Collaborator
|
python fails though: #3763 |
aceforeverd
approved these changes
Feb 21, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
replace Unrecognized VM option MaxPermSize with MaxMetaspaceSize and upgrade openmldb-batchjob maven.compiler.source and maven.compiler.target to 1.8
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bug fix
What is the current behavior? (You can also link to an open issue here)
Unrecognized VM option 'MaxPermSize=2048m' when executing scalatest-maven-plugin:1.0:test (test) @ openmldb-spark-connector #3755
What is the new behavior (if this is a feature change)?