-
Notifications
You must be signed in to change notification settings - Fork 248
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
Instead of using release name to enable multiarch use MULTIARCH_OPTS config option #2219
Conversation
A new Pull Request was created by @smuzaffar for branch master. @smuzaffar, @aandvalenzuela, @iarspider, @cmsbuild can you please review it and eventually sign? Thanks. |
cms-bot internal usage |
Pull request #2219 was updated. |
Pull request #2219 was updated. |
please test with cms-sw/cmsdist#9161 |
Pull request #2219 was updated. |
Pull request #2219 was updated. |
please test with cms-sw/cmsdist#9161 for CMSSW_14_1_MULTIARCHS_X |
please test with cms-sw/cmsdist#9161 for CMSSW_14_1_NONLTO_X |
Pull request #2219 was updated. |
please test with cms-sw/cmsdist#9161 for CMSSW_14_1_NONLTO_X |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-668cd8/39100/summary.html Comparison SummaryThere are some workflows for which there are errors in the baseline: Summary:
|
Currently bot was using the release name to enable multi-arch builds. In order to support multi-arch in default builds (e.g 14.1.X), this PR adds
MULTIARCH_OPTS
config flag. This can be set to enable multi-arch builds for any IB. For nowconfig.map
is updated to enable MULTIARCH_OPTS for special MULTIARCH, SKYLAKE IBs