[
https://issues.apache.org/jira/browse/HDFS-17224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17775027#comment-17775027
]
Steve Loughran commented on HDFS-17224:
---------------------------------------
is hdfs doing its tests in the same process? aws module parallel tests have a
pool of jvms but then execute each junit suite sequentially within the pool, so
contamination is generally limited to cached fs instances or again, some other
static state.
doing pre-emptive cleanup is good. had to do one with the latest aws uploads
test where it didn't clean up pending uploads from the previous run if that
stopped partway through, which then broke the next....
> TestRollingUpgrade.testDFSAdminRollingUpgradeCommands failing intermittently
> ----------------------------------------------------------------------------
>
> Key: HDFS-17224
> URL: https://issues.apache.org/jira/browse/HDFS-17224
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: dfsadmin, test
> Affects Versions: 3.4.0
> Reporter: Steve Loughran
> Priority: Major
>
> TestRollingUpgrade.testDFSAdminRollingUpgradeCommands failing because the
> static mbean isn't null. This is inevitably related to the fact that in test
> runs, the jvm is reused and so the mbean may be present from a previous test
> -maybe one which didn't clean up.
> it does not fail standalone
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
