mvn package gets stuck after a test

[b-gauthier]

Hi,

I am trying to build jeromq on a Windows 11 computer with the latest versions of Java and Maven. Unfortunately, the build gets stuck after Test Run 13 showing "All options sync new hot".

I tried with a different computer on Windows 10, same behavior.

Thanks for you help.

[fbacchella]

Can you add: (timeout = 5000) after each @Test and rerun the tests ?

Please avoid screen shots. They are bloated and not searchable.

Are you trying it with the latest snapshot ?

[b-gauthier]

Where should I put the timeout?

Sorry for the screen shots, and yes I'm using the latest snapshot.

FYI: I'm trying to build it to get a jar file I could use in Matlab.

Thanks

[fbacchella]

Check in the failing class source: src/test/java/org/zeromq/TestZproxy.java

[b-gauthier]

I added a (timeout = 5000) after each @Test in src/test/java/org/zeromq/TestZproxy.java
It worked (I was able to go to the next test).

Unfortunately, same behavior with many other tests. I added (timeout = 5000) to more than 10 other files. I was finally able to got to the end of the build process but it ultimately failed. It does not seem that adding timeout everywhere is the good way to go.

[ERROR] Tests run: 693, Failures: 0, Errors: 17, Skipped: 16, Flakes: 6
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for JeroMQ 0.7.0-SNAPSHOT:
[INFO]
[INFO] JeroMQ ............................................. SUCCESS [  0.003 s]
[INFO] JeroMQ :: Core ..................................... FAILURE [09:53 min]
[INFO] JeroMQ ............................................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  09:53 min
[INFO] Finished at: 2024-08-27T15:13:06-04:00
[INFO] ------------------------------------------------------------------------

Should I try a different approach?

[fbacchella]

It’s a good starting point. That should be the default for many tests.
But you have way too many failures. I think you might have a network problem on your local machine. Perhaps a miss configuration with the way how localhost is resolved.
But any way, you can always find the latest build at https://oss.sonatype.org/content/repositories/snapshots/org/zeromq/jeromq/0.7.0-SNAPSHOT/
Can you share a stack of one failed test ?

[fbacchella]

I make a git clone, run the tests with mvn package:

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for JeroMQ 0.7.0-SNAPSHOT:
[INFO] 
[INFO] JeroMQ ............................................. SUCCESS [  0.001 s]
[INFO] JeroMQ :: Core ..................................... SUCCESS [03:03 min]
[INFO] JeroMQ ............................................. SUCCESS [  3.311 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  03:07 min
[INFO] Finished at: 2024-08-27T23:30:37+02:00
[INFO] ------------------------------------------------------------------------