-
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
Rivet: use eigen flags; update rivet analysis path for multi-arch #9141
Conversation
A new Pull Request was created by @smuzaffar for branch IB/CMSSW_14_1_X/master. @cmsbuild, @smuzaffar, @iarspider, @aandvalenzuela can you please review it and eventually sign? Thanks. |
cms-bot internal usage |
test parameters:
|
please test |
please test for CMSSW_14_1_MULTIARCHS_X |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-5d4bab/38887/summary.html 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: Comparison SummarySummary:
|
+externals unit tests for MULTIARCHS IB passed |
This pull request is fully signed and it will be integrated in one of the next IB/CMSSW_14_1_X/master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @sextonkennedy, @rappoccio, @antoniovilela (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 runtestPhysicsToolsPatAlgos had ERRORS Comparison SummarySummary:
|
Rivet tests are failing in multi-arch build. Looks like rivet internally has a copyif eigen but in
RivetEigen
namespace. Just to make sure that we use consistent egien flags I have updated river spec to useCMS_EIGEN_CXX_FLAGS
build flags.Rivet tool sets
RIVET_ANALYSIS_PATH
pointing torivet/lib/Rivet
. This causes runtime errors for multu-arch builds. Looks like rivet already knows this path. so no need to set it forrivet
itself[a]