-
Notifications
You must be signed in to change notification settings - Fork 183
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
[cepgen] Disable BoostWrapper addon #9323
Conversation
A new Pull Request was created by @smuzaffar for branch IB/CMSSW_14_1_X/master. @aandvalenzuela, @cmsbuild, @iarspider, @smuzaffar can you please review it and eventually sign? Thanks. |
cms-bot internal usage |
FYI @forthommel |
please test |
+externals |
This pull request is fully signed and it will be integrated in one of the next IB/CMSSW_14_1_X/master IBs after it passes the integration tests. This pull request will now be reviewed by the release team before it's merged. @sextonkennedy, @rappoccio, @antoniovilela, @mandrenguyen (and backports should be raised in the release meeting by the corresponding L2) |
-1 Failed Tests: UnitTests The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic:
You can see more details here: Unit TestsI found 1 errors in the following unit tests: ---> test TestIOPoolInputNoParentDictionary had ERRORS Comparison SummarySummary:
|
We were not building CepGen BoostWrapper as our containers (cmssw-elX) do not have boost installed on system (we always want to use boost from cms externals). But on systems with boost is installed (and where we can not use our containers e.g. riscv) cepgen picks up Boost from system and then packaging fail as it complains about wrong boost_system lib dependency.
Somehow I was not able to convince cepgen build system to use our boost (may be we are missing something in our boost?) so for now we explicitly disable cepgen BoostWrapper