-
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
Using consistent Eigen alignment settings #9060
Conversation
A new Pull Request was created by @smuzaffar for branch IB/CMSSW_14_1_X/master. @iarspider, @aandvalenzuela, @cmsbuild, @smuzaffar can you please review it and eventually sign? Thanks. |
cms-bot internal usage |
please test |
please test for CMSSW_14_1_MULTIARCHS_X/el8_amd64_gcc12 |
Thanks @smuzaffar. I have two questions
|
Pull request #9060 was updated. |
ah my bad @makortel , yes |
please test |
please test for CMSSW_14_1_MULTIARCHS_X/el8_amd64_gcc12 |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-aaee32/38036/summary.html Comparison SummarySummary:
|
+externals |
lets get this in for next 14.1.X IB. |
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, @antoniovilela, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
@smuzaffar it looks like those packages are still using only |
Yes @fwyzard , for default (non multiarch build) IBs these packages will still use
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-aaee32/38040/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:
|
OK, thanks. I see that the default build has
while the v3 build has
but, looking at the spec files, I don't see what makes the change between the two ! |
@fwyzard , to avoid maintaining two spec files (e.g. lwtnn.spec and lwtnn_x86-64-v3.spec) |
Ah... I see, thanks. |
This is follow up on #9043. This change allows
lwtnn, opencv and pytorch
packages