CMSSW multi microarch support: set env after sandbox extraction #8853
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Can one of the admins verify this patch? |
belforte
approved these changes
Dec 2, 2024
|
thanks @smuzaffar |
|
sorry for my confusion. This is already deployed in production now. |
|
great, thanks @belforte |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@belforte , for multi microarch enabled CMSSW, scram runtime env should be set after the sandbox extraction. This will allow scram to select the correct/best micro arch.
This change should not break existing cmssw. Setting up scram runtime just after scram project or after extracting the sandbox should behave the same way for non-multi microarch releases.