[ https://issues.apache.org/jira/browse/HBASE-23779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034097#comment-17034097 ]
Mark Robert Miller commented on HBASE-23779: -------------------------------------------- FYI re: the -T arg I'm finding it's pretty sensitive to the Maven version - the 3.5.* I seem to get from the yetus Dockerfile in dev-support is crashing all the time, 3.6.1 has been behaving as I've been used to (my main desktop had 3.6.1 to start) > 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)