[
https://issues.apache.org/jira/browse/HADOOP-12149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14608833#comment-14608833
]
Allen Wittenauer commented on HADOOP-12149:
-------------------------------------------
FYI, confirming that hadoop personality is now getting picked up. Hooray!
Prior to this patch, the initial mvn install ran with:
{code}
/home/jenkins/tools/maven/latest/bin/mvn --batch-mode -fae clean install
-Dmaven.javadoc.skip=true -Ptest-patch >
/home/jenkins/jenkins-slave/workspace/PreCommit-HADOOP-Build/patchprocess/branch-mvninstall-root.txt
2>&1
{code}
post-this patch, it now runs with:
{code}
/home/jenkins/tools/maven/latest/bin/mvn --batch-mode -fae clean install
-Dmaven.javadoc.skip=true -DskipTests -Pnative -Drequire.snappy
-Drequire.openssl -Drequire.fuse -Drequire.test.libhadoop -Ptest-patch >
/home/jenkins/jenkins-slave/workspace/PreCommit-HADOOP-Build/patchprocess/branch-mvninstall-root.txt
2>&1
{code}
Needless to say, skipping the unit tests is a huge speed up. ;)
> copy all of test-patch BINDIR prior to re-exec
> ----------------------------------------------
>
> Key: HADOOP-12149
> URL: https://issues.apache.org/jira/browse/HADOOP-12149
> Project: Hadoop Common
> Issue Type: Improvement
> Components: yetus
> Affects Versions: 3.0.0, HADOOP-12111
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Blocker
> Fix For: 3.0.0
>
> Attachments: HADOOP-12149.00.patch
>
>
> During some tests (e.g.,
> https://builds.apache.org/job/PreCommit-HADOOP-Build/7090 ), initial mvn
> install triggered a full test suite run when Jenkins switches from old
> test-patch to new test-patch. This is bad.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
