dombizita commented on PR #10570: URL: https://github.com/apache/ozone/pull/10570#issuecomment-5091417511
> can you check on [this](https://github.com/apache/ozone/actions/runs/30094128362/job/89490329328?pr=10570) CI failure? I don't _think_ it's related but anything NPE is concerning: The problem is that all three write tests grab the pipeline via a hard-coded first stream entry on line 375: https://github.com/apache/ozone/blob/2473ec54d33604929d3ff7983b40555f167ff481/hadoop-ozone/integration-test/src/test/java/org/apache/hadoop/ozone/client/rpc/TestClientRetryTimeout.java#L372-L381 With the help of Claude: > This assumes entry 0 still holds a live XceiverClient after the setup write/flush. But this is a shared, `@Ordered` PER_CLASS suite — the earlier tests kill/restart datanodes, and `waitForPipelineTobeReady(THREE)` only guarantees one healthy factor-3 pipeline exists, not that the specific pipeline this key lands on is ready. > > The shutdown "Found 2 leaked objects" error is a cascade: the NPE aborts before key.close(), so CodecBuffer.assertNoLeaks() flags the abandoned stream's buffers at teardown. Filed [HDDS-15996](https://issues.apache.org/jira/browse/HDDS-15996) to fix it on master, re-triggered the CI on this PR. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
