[
https://issues.apache.org/jira/browse/HADOOP-11984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14563246#comment-14563246
]
Chris Nauroth commented on HADOOP-11984:
----------------------------------------
[~vinayrpet], thank you!
I just want to clarify something about those timings too. The 98 minutes that
you mentioned was for the full pre-commit job run (checking javac warnings,
javadoc warnings, checkstyle, etc.). If we look at just the test execution
time, hadoop-common tests are down from ~24 minutes to ~8 minutes, and
hadoop-hdfs tests are down from ~2 hours to ~45 minutes.
For hadoop-common, we're approaching a situation where test execution is no
longer the long pole in the overall pre-commit job execution time. There is
still plenty of room for optimization in the HDFS tests though.
> Enable parallel JUnit tests in pre-commit.
> ------------------------------------------
>
> Key: HADOOP-11984
> URL: https://issues.apache.org/jira/browse/HADOOP-11984
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build, scripts, test
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Attachments: HADOOP-11984.001.patch, HADOOP-11984.002.patch,
> HADOOP-11984.003.patch, HADOOP-11984.004.patch, HADOOP-11984.005.patch,
> HADOOP-11984.006.patch, HADOOP-11984.007.patch, HADOOP-11984.008.patch,
> HADOOP-11984.009.patch, HADOOP-11984.010.patch, HADOOP-11984.011.patch,
> HADOOP-11984.013.patch
>
>
> HADOOP-9287 and related issues implemented the parallel-tests Maven profile
> for running JUnit tests in multiple concurrent processes. This issue
> proposes to activate that profile during pre-commit to speed up execution.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
