[
https://issues.apache.org/jira/browse/HBASE-28135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17774653#comment-17774653
]
Hudson commented on HBASE-28135:
--------------------------------
Results for branch master
[build #925 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/925/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/925/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/925/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/925/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Specify -Xms for tests
> ----------------------
>
> Key: HBASE-28135
> URL: https://issues.apache.org/jira/browse/HBASE-28135
> Project: HBase
> Issue Type: Improvement
> Components: test
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Major
> Fix For: 2.6.0, 2.4.18, 2.5.6, 3.0.0-beta-1
>
>
> The default -Xms value is JVM dependent, but the host memory size is usually
> included in the calculation.
> -Xms in turn is used to calculate some GC parameters, for example NewSize and
> OldSize, which affect the behaviour of tests.
> As the memory consumption on the tests is not dependent on the host VM size,
> we could set -Xms for the tests explictly, and enjoy more consistent test
> results.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
