You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (Jira)" <ji...@apache.org> on 2019/10/04 19:28:00 UTC
[jira] [Commented] (HADOOP-16633) Tune hadoop-aws parallel test
surefire/failsafe settings
[ https://issues.apache.org/jira/browse/HADOOP-16633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16944779#comment-16944779 ]
Steve Loughran commented on HADOOP-16633:
-----------------------------------------
bq. alphabetical, reversealphabetical, random, hourly (alphabetical on even hours, reverse alphabetical on odd hours), failedfirst, balanced and filesystem.
> Tune hadoop-aws parallel test surefire/failsafe settings
> --------------------------------------------------------
>
> Key: HADOOP-16633
> URL: https://issues.apache.org/jira/browse/HADOOP-16633
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: build, fs/s3, test
> Affects Versions: 3.2.1
> Reporter: Steve Loughran
> Priority: Major
>
> We can do more to improve our test runs by looking at the failsafe docs
> [http://maven.apache.org/surefire/maven-failsafe-plugin/integration-test-mojo.html]
>
> * default value to be by core, eg. 2C
> * use the runorder attribute which determines how parallel runs are chosen; random for better nondeterminism
> We'd need to experiment first, which can be done by setting failsafe.runOrder
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org