Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test failed from FairMQ at fresh O2 installation #1212

Closed
bovulpes opened this issue Jun 15, 2018 · 7 comments
Closed

Test failed from FairMQ at fresh O2 installation #1212

bovulpes opened this issue Jun 15, 2018 · 7 comments

Comments

@bovulpes
Copy link
Collaborator

Hello,

On a fresh CentOS 7.5 O2 installation it stops here:

1/9 Test #1: FairMQ.Protocols .................***Timeout 30.04 sec
89% tests passed, 1 tests failed out of 9

Any other experience like this?

@dennisklein
Copy link
Contributor

Could you temporarily modify alidist/fairmq.sh as follows, run aliBuild again with --debug and attach the ctest output here?

diff --git a/fairmq.sh b/fairmq.sh
index 9ab8bd1..a9a2699 100644
--- a/fairmq.sh
+++ b/fairmq.sh
@@ -48,7 +48,7 @@ cmake $SOURCEDIR                                                 \
       -DCMAKE_INSTALL_BINDIR=bin
 
 cmake --build . ${JOBS:+-- -j$JOBS}
-ctest ${JOBS:+-j$JOBS}
+ctest -V ${JOBS:+-j$JOBS}
 cmake --build . --target install ${JOBS:+-- -j$JOBS}
 
 # ModuleFile

Thanks!

@bovulpes
Copy link
Collaborator Author

log.txt

Hi Dennis,

This is the log.

@dennisklein
Copy link
Contributor

Thanks, the test is failing, because a device in a unit test tries to bind to port 6000, which is already in use on your machine. We encountered probably the same problem on one of @dberzano's build hosts recently. I will disable running this set of tests in fairmq.sh until we have a more robust test runner.

@dennisklein
Copy link
Contributor

I believe the problem is fixed with the most recent version of the fairmq.sh recipe. Reopen, if it is not the case.

@dennisklein
Copy link
Contributor

Can't even close^^

@dberzano
Copy link
Contributor

The problem should be fixed indeed. Thanks!

@bovulpes
Copy link
Collaborator Author

OK, thanks.

mikesas pushed a commit to mikesas/AliceO2 that referenced this issue Dec 13, 2022
* Adjusted timing thresholds for Run3

* FT0-collision matching tuned for 22f,m. QA updated

* clang-format fixes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants