Hi William, In my PR (https://github.com/apache/iotdb/pull/10789), there was an NPE (NullPointerException) error in the test for 'oneMemberGroupChange' (https://github.com/apache/iotdb/actions/runs/5764037692/job/15640048487?pr=10789). You may want to investigate the cause of this issue.
Thanks ---------------------- Xinyu Tan On 2023/08/04 14:59:51 William Song wrote: > Hi Chris, > > I will take a look at RatisConsensusTest. In case the tests fail next time, > feel free to mention me directly in the PR. This way, I can view the complete > error stack. > > William > > > 2023年8月4日 17:13，Christofer Dutz <christofer.d...@c-ware.de> 写道： > > > > Hi all, > > > > So, in the past days I‘ve been building IoTDB on several OSes and have > > noticed some tests to repeatedly failing the build, but succeeding as soon > > as I run them again. > > To sum it up it’s mostly these tests: > > > > ————— IoTDB: Core: Consensus > > > > RatisConsensusTest.removeMemberFromGroup:148->doConsensus:258 NullPointer > > Cann… > > > > > > RatisConsensusTest.addMemberToGroup:116->doConsensus:258 NullPointer Cannot > > in... > > > > > > > > ReplicateTest.replicateUsingWALTest:257->initServer:147 » IO > > org.apache.iotdb.... > > > > > > ————— IoTDB: Core: Node Commons > > > > Keeps on failing because of left-over iotdb server instances. > > > > I would be happy to tackle the Node Commons tests regularly failing by > > implementing the Test-Runner, that I mentioned before, which will start and > > run IoTDB inside the VM running the tests, so the instance will be shut > > down as soon as the test is finished. This should eliminate that problem. > > However I have no idea if anyone is working on the RatisConsensusTest and > > the ReplicateTest. > > > > Chris > >
