[ 
https://issues.apache.org/jira/browse/HBASE-23779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17032526#comment-17032526
 ] 

Nick Dimiduk commented on HBASE-23779:
--------------------------------------

Okay, I cannot test my yetus patch using our precommit because the layout of 
the repo artifact generated by GitHub doesn't match that script's expectations. 
Looks like {{test-patch.sh}} was moved since this job was authored, it's now 
under {{precommit/src/main/shell}}.

{noformat}
08:34:51 + prerelease_dirs=(${TEST_FRAMEWORK}/${YETUS_PRERELEASE_GITHUB/\//-}-*)
08:34:51 + 
TESTPATCHBIN=/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/test_framework/ndimiduk-yetus-7d6ff39/precommit/test-patch.sh
08:34:51 + 
TESTPATCHLIB=/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/test_framework/ndimiduk-yetus-7d6ff39/precommit
08:34:51 + [[ true = \t\r\u\e ]]
08:34:51 + ls -l 
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/test_framework/ndimiduk-yetus-7d6ff39/precommit/test-patch.sh
08:34:51 ls: cannot access 
'/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/test_framework/ndimiduk-yetus-7d6ff39/precommit/test-patch.sh':
 No such file or directory
08:34:52 Build step 'Execute shell' marked build as failure
{noformat}

> 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: 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)

Reply via email to