[
https://issues.apache.org/jira/browse/HBASE-23779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17040303#comment-17040303
]
Nick Dimiduk commented on HBASE-23779:
--------------------------------------
{quote}
bq. [~busbey] any objection if I modify the Jenkins script as follows?
Sorry, some how missed this. I think the correct thing to do in the case of
running a non-release is to do a build of Yetus and then consume the binary off
of that. I *think* yetus precommit works directly from source, but I don't
think the project promises it will nor intends folks to do that.
{quote}
We base the assumption that Yetus pre-commit works from source in a handful of
places. I found it also in {{Jenkinsfile_Github}} as
{{${WORKSPACE}/${YETUS}/precommit/src/main/shell/test-patch.sh}} and in
{{hbase_nightly_yetus.sh}} as
{{${WORKSPACE}/yetus-git/precommit/test-patch.sh}}.
> Up the default fork count to make builds complete faster; make count relative
> to CPU count
> ------------------------------------------------------------------------------------------
>
> Key: HBASE-23779
> URL: https://issues.apache.org/jira/browse/HBASE-23779
> Project: HBase
> Issue Type: Bug
> Components: test
> Reporter: Michael Stack
> Assignee: Michael Stack
> Priority: Major
> Fix For: 3.0.0, 2.3.0
>
> Attachments: addendum2.patch, test_yetus_934.0.patch
>
>
> Tests take a long time. Our fork count running all tests are conservative --
> 1 (small) for first part and 5 for second part (medium and large). Rather
> than hardcoding we should set the fork count to be relative to machine size.
> Suggestion here is 0.75C where C is CPU count. This ups the CPU use on my box.
> Looking up at jenkins, it seems like the boxes are 24 cores... at least going
> by my random survey. The load reported on a few seems low though this not
> representative (looking at machine/uptime).
> More parallelism willl probably mean more test failure. Let me take a look
> see.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)