You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/11/15 13:27:00 UTC
[jira] [Updated] (HDDS-2507) Remove the hard-coded exclusion of
TestMiniChaosOzoneCluster
[ https://issues.apache.org/jira/browse/HDDS-2507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HDDS-2507:
---------------------------------
Labels: pull-request-available (was: )
> Remove the hard-coded exclusion of TestMiniChaosOzoneCluster
> ------------------------------------------------------------
>
> Key: HDDS-2507
> URL: https://issues.apache.org/jira/browse/HDDS-2507
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Reporter: Marton Elek
> Assignee: Marton Elek
> Priority: Major
> Labels: pull-request-available
>
> We excluded the execution of TestMiniChaosOzoneCluster from the hadoop-ozone/dev-support/checks/integration.sh because it was not stable enough.
> Unfortunately this exclusion makes it impossible to use custom exclusion lists (-Dsurefire.excludesFile=....) as excludesFile can't be used if -Dtest=!... is already used.
> I propose to remove this exclusion to make it possible to use different exclusion for different runs (pr check, daily, etc.)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org