Hi Andriy, Good catch - this is due to a switch to use SecureRandom.getInstanceStrong() by default in Santuario in 3.0.1. I guess this is causing major blocking issues on the build machines as it's not getting enough entropy. I've merged a fix to switch the Surefire config to use a non-blocking algorithm instead for the tests - can you confirm if it's OK now?
Colm. On Mon, Oct 10, 2022 at 10:18 PM Andriy Redko <[email protected]> wrote: > > Hey Colm, > > Interesting side effect after updating main to WSS4J 3.0.0: the > cxf-rt-ws-security tests are > started to take very long time (not all, but some, for example > DOMToStaxEncryptionIdentifierTest, 930.104 s): > > [INFO] Running > org.apache.cxf.ws.security.wss4j.DOMToStaxEncryptionIdentifierTest > [INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: > 930.104 s - in > org.apache.cxf.ws.security.wss4j.DOMToStaxEncryptionIdentifierTest > > The builds are aborted right now [1] because of long time of inactivity. If > you have time to > look at it, would be great, I will try to find out what is going on as well. > > Thank you. > > [1] https://ci-builds.apache.org/job/CXF/job/CXF-JDK17/ > > Best Regards, > Andriy Redko >
