O2 build failing on Mojave in FairMQ

Dear experts,

I have currently problems to build o2 on macOS Mojave due to failing ctests in FairMQ for the shared memory transport, which all go in timeout, see

DEBUG:O2:FairMQ:ali-master:
DEBUG:O2:FairMQ:ali-master: 78% tests passed, 6 tests failed out of 27
DEBUG:O2:FairMQ:ali-master:
DEBUG:O2:FairMQ:ali-master: Total Test time (real) = 173.89 sec
DEBUG:O2:FairMQ:ali-master:
DEBUG:O2:FairMQ:ali-master: The following tests FAILED:
DEBUG:O2:FairMQ:ali-master: 6 - FairMQ.PluginServices (Timeout)
DEBUG:O2:FairMQ:ali-master: 11 - Example-1-1-shmem (Timeout)
DEBUG:O2:FairMQ:ali-master: 14 - Example-1-n-1-shmem (Timeout)
DEBUG:O2:FairMQ:ali-master: 17 - Example-CopyPush-shmem (Timeout)
DEBUG:O2:FairMQ:ali-master: 20 - Example-Multipart-shmem (Timeout)
DEBUG:O2:FairMQ:ali-master: 27 - Example-ReqRep-shmem (Timeout)
DEBUG:O2:FairMQ:ali-master: Errors while running CTest

Only the shmem tests fail, all others pass. Does anyone have an idea how to fix/circumvent this?

Thanks in advance!

Cheers

Markus

I got something similar. A restart of the machine should solve it. Alexey and Dennis have already fixed the problem in an upcoming version of fairmq.

This being said, i am not sure we should run the tests when building fairmq as it is only a dependency.

Hi Barthelemy,

Thanks a lot for the help! Restarting the machine solved it for most of the tests, but still two fail due to timeout issues:

DEBUG:O2:FairMQ:ali-master: The following tests FAILED:
DEBUG:O2:FairMQ:ali-master: 6 - FairMQ.PluginServices (Timeout)
DEBUG:O2:FairMQ:ali-master: 20 - Example-Multipart-shmem (Timeout)

For the moment I assume I have to disable the ctests until the issue gets fixed.

Cheers

Markus

As a workaround you can modify the recipe to skip ctest.

Maybe it is a problem with a port that is not available.

Calling @deklein in case he has an idea.

Hi,

where can I find this ali-master version of the alidist? (so I can see which versions are compiled)

For the remaining timeouts, I would need more information, could you run ctest -R "FairMQ.PluginServices|Example-Multipart-shmem" -VV?

Best,
Dennis

Either that, or, you are welcome to have any user, that has failing FairMQ tests create a bug report at https://github.com/FairRootGroup/FairMQ/issues/new?template=bug_report.md. This will give us valuable information, which platforms/environments have problems and of course we are happy to help resolving them.

Hi Dennis,

I use the default build recipe for FairMQ (fairmq.sh) from the master branch of alidist, and I was using the standard o2 defaults (defaults-o2.sh). ali-master is just the name assigned to the built.

OK, I will try to build FairMQ again with line you mentioned and add the debug output to this thread.

Thanks a lot for your help!

Cheers

Markus

I just noticed even on a normal ctest invocation without -VV, a file is generated in the build directory Testing/Temporary/LastTest.log which contains the verbose ctest log output.