[jira] [Updated] (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:all-tabpanel ] Steve Loughran updated HADOOP-16633: Parent: HADOOP-18067 (was: HADOOP-17566) > 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.20.1#820001) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (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:all-tabpanel ] Steve Loughran updated HADOOP-16633: Description: 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 was: Maven failsafe and surefire parallel runners support a runorder attribute which determines how parallel runs are chosen [http://maven.apache.org/surefire/maven-failsafe-plugin/integration-test-mojo.html] > 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-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (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:all-tabpanel ] Steve Loughran updated HADOOP-16633: Summary: Tune hadoop-aws parallel test surefire/failsafe settings (was: Tunehadoop-aws parallel tests to use balanced runorder for parallel tests) > 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 > > Maven failsafe and surefire parallel runners support a runorder attribute > which determines how parallel runs are chosen > [http://maven.apache.org/surefire/maven-failsafe-plugin/integration-test-mojo.html] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
