[
https://issues.apache.org/jira/browse/HBASE-23823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack updated HBASE-23823:
----------------------------------
Resolution: Later
Status: Resolved (was: Patch Available)
Resolving this as 'later'. I learned some stuff in here and then closed the PR
and the parent issue because thought this a hopeless case. Subsequently thought
different. Reopened the parent. Have put up new PR that ups the forkcount from
0.25C to 0.5C against the parent. Will continue these investigations up there.
> Run maven with more than default single thread (--threads=0.5C)
> ---------------------------------------------------------------
>
> Key: HBASE-23823
> URL: https://issues.apache.org/jira/browse/HBASE-23823
> Project: HBase
> Issue Type: Sub-task
> Reporter: Michael Stack
> Priority: Major
> Attachments:
> 0001-HBASE-23823-Run-maven-with-more-than-default-single-.patch,
> 0001-HBASE-23823-Run-maven-with-more-than-default-single-.patch,
> 0001-HBASE-23823-Run-maven-with-more-than-default-single-.patch,
> 0001-HBASE-23823-Run-maven-with-more-than-default-single-.patch
>
>
> See tail of parent task where we made commits to hbase-personality trying to
> make maven run more furiously on nightly builds by upping the maven thread
> count (the --threads flag ... see
> https://cwiki.apache.org/confluence/display/MAVEN/Parallel+builds+in+Maven+3).
> The effort was abandoned because it unsettled the build. This issue
> separates messing with the maven threads flag from the broader topic the
> parent covers.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
