hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13514) Upgrade maven surefire plugin to 2.20.1
Date Mon, 20 Nov 2017 17:35:00 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-13514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259532#comment-16259532

Allen Wittenauer commented on HADOOP-13514:

https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/599/ is the first full run
with this (and only this) patch.

For future readers, some context as to the importance can be found in HDFS-12711.

A few interesting things:
* hadoop-hdfs-project ran significantly better than usual. In particular, it looks like surefire
mostly recovered only to get swamped again with stuck JVMs.
* Given the output, are there thread leaks in EC?
* hadoop-mapreduce-client-jobclient looks like it ran almost all of the tests until it couldn't
launch anymore.  Of those that did get run, they passed.  I'm not sure what to make of that
* There were zero unreaped processes after mvn unit.  That's a great sign.

> Upgrade maven surefire plugin to 2.20.1
> ---------------------------------------
>                 Key: HADOOP-13514
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13514
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 2.8.0
>            Reporter: Ewan Higgs
>            Assignee: Akira Ajisaka
>             Fix For: 3.1.0
>         Attachments: HADOOP-13514-addendum.01.patch, HADOOP-13514-testing.001.patch,
HADOOP-13514-testing.002.patch, HADOOP-13514-testing.003.patch, HADOOP-13514-testing.004.patch,
HADOOP-13514-testing.005.patch, HADOOP-13514.002.patch, HADOOP-13514.003.patch, HADOOP-13514.004.patch,
HADOOP-13514.005.patch, HADOOP-13514.006.patch, surefire-2.19.patch
> A lot of people working on Hadoop don't want to run all the tests when they develop;
only the bits they're working on. Surefire 2.19 introduced more useful test filters which
let us run a subset of the tests that brings the build time down from 'come back tomorrow'
to 'grab a coffee'.
> For instance, if I only care about the S3 adaptor, I might run:
> {code}
> mvn test -Dmaven.javadoc.skip=true -Pdist,native -Djava.awt.headless=true \"-Dtest=org.apache.hadoop.fs.*,
org.apache.hadoop.hdfs.*, org.apache.hadoop.fs.s3a.*\"
> {code}
> We can work around this by specifying the surefire version on the command line but it
would be better, imo, to just update the default surefire used.
> {code}
> mvn test -Dmaven.javadoc.skip=true -Pdist,native -Djava.awt.headless=true \"-Dtest=org.apache.hadoop.fs.*,
org.apache.hadoop.hdfs.*, org.apache.hadoop.fs.s3a.*\" -Dmaven-surefire-plugin.version=2.19.1
> {code}

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message