jduo commented on PR #38876:
URL: https://github.com/apache/arrow/pull/38876#issuecomment-1826967158

   > I'm not sure what's happening in this CI failure after the Netty 
refactoring.
   > This test was in TestBaseAllocator before, but that test class got moved 
to memory-core. This test got separated into its own test class, moved back to 
Netty core (because it has Netty dependencies and wouldn't build in 
memory-core), and now throws a ConcurrentModificationException.
   > 
   > > Error:  org.apache.arrow.memory.netty.TestNettyAllocator.testMemoryUsage 
 Time elapsed: 0.317 s  <<< ERROR!
   > java.util.ConcurrentModificationException
   >    at 
java.base/java.util.ArrayList$ArrayListSpliterator.tryAdvance(ArrayList.java:1604)
   >    at 
java.base/java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:129)
   >    at 
java.base/java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:527)
   >    at 
java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:513)
   >    at 
java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499)
   >    at 
java.base/java.util.stream.MatchOps$MatchOp.evaluateSequential(MatchOps.java:230)
   >    at 
java.base/java.util.stream.MatchOps$MatchOp.evaluateSequential(MatchOps.java:196)
   >    at 
java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
   >    at 
java.base/java.util.stream.ReferencePipeline.anyMatch(ReferencePipeline.java:632)
   >    at 
org.apache.arrow.memory.netty.TestNettyAllocator.testMemoryUsage(TestNettyAllocator.java:56)
   
   This didn't happen in my last test run and all I did was change the module 
info computer plugin to inherit its version. So this is probably a threading 
issue. Maybe extracting this test from other TestBaseAllocator tests is causing 
them to run in parallel when they weren't before.


-- 
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]

Reply via email to