LArSoft CI builds are not properly registered in the LArSoft CI DB
Looking as an example at the CI build lar_ci/3616, this is running on three OS in parallel (SLF6, SLF7 and macOS).
From the log I see that the SLF7 initialization happened properly: I got the message "Added lar_ci/3616.", this has a timestamp: 01 Oct 2018 09:34:18 GMT,
i.e. 01 Oct 2018 04:34:18 CDT.
Then the registration for SLF6 failed with the message in attach report.build_1_LArSoft_3616_SLF6.html, it happened at 1 Oct 2018 04:34:50 CDT.
This is a new error message that I never saw before.
Finally the registration for macOS failed with the message in attach report.build_1_LArSoft_3616_macOS.html, it happened at 1 Oct 2018 04:34:52 CDT.
This is an error message that we already so before.
Please, can you have a look at this issue?
#2 Updated by Vito Di Benedetto almost 2 years ago
- Assignee changed from Vladimir Podstavkov to Vito Di Benedetto
This issue can be avoided by using a platform dependent delay on the CI code, this will avoid that concurrent builds from the same CI build and running on different platforms will interfere each other.