[
https://issues.apache.org/jira/browse/IOTDB-5423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17677624#comment-17677624
]
Eric Pai commented on IOTDB-5423:
---------------------------------
I have debugged out this issue. As WALManger will init the
NodeAllocationStrategy in the constructor, which is only called in a singleton
mode. If a previous test inits this with FiristCreateStrategy, the test wil be
failed, as it tests as depending on ElasticStrategy.
The issue may be happened in other test cases, as long as they depend on the
same singleton instance in one JVM.
Two solution:
# Disable reuseForks in surefie plugin. Each test class will use a new JVM
process, so the singleton instance will be a new one.
# Enable running test cases in a random order, so we can reproduce the
failures casued by test order.
> Unit test failures of WALManager
> --------------------------------
>
> Key: IOTDB-5423
> URL: https://issues.apache.org/jira/browse/IOTDB-5423
> Project: Apache IoTDB
> Issue Type: Improvement
> Components: Core/WAL
> Reporter: Eric Pai
> Assignee: Haiming Zhu
> Priority: Major
>
> This is the only error outout
> (14:42:03) [ERROR] Failures:
> (14:42:03) [ERROR] WALManagerTest.testDeleteOutdatedWALFiles:84
> expected:<org.apache.iotdb.db.wal.node.WALNode@56e8b606> but
> was:<org.apache.iotdb.db.wal.node.WALNode@2dd29a59>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
