[
https://issues.apache.org/jira/browse/HBASE-26828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508072#comment-17508072
]
Hudson commented on HBASE-26828:
--------------------------------
Results for branch master
[build #538 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/538/]:
(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/538/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/538/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/master/538/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}
> Increase the concurrency when running UTs in pre commit job
> -----------------------------------------------------------
>
> Key: HBASE-26828
> URL: https://issues.apache.org/jira/browse/HBASE-26828
> Project: HBase
> Issue Type: Improvement
> Components: jenkins, test
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 2.5.0, 2.6.0, 3.0.0-alpha-3, 2.4.11
>
>
> The default forkCount is 0.25C. We used to run on a 16 cores machine so the
> concurrency is 4, but now our build nodes are all 8 cores, so the concurrency
> is 2. The build time is way more slower than before.
> Since we only have 2 slots on the build node, I think it is OK to increase
> the forkCount to 0.5C. But I'm not sure whether we should change the default
> value in pom, or we just set it in the pre commit job.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
