-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
USER_SCRAM_TARGET
does not work in a development area
#44947
Comments
assign core |
New categories assigned: core @Dr15Jones,@makortel,@smuzaffar you have been requested to review this Pull request/Issue and eventually sign? Thanks |
FYI @VinInn |
cms-bot internal usage |
A new Issue was created by @fwyzard. @rappoccio, @antoniovilela, @smuzaffar, @sextonkennedy, @makortel, @Dr15Jones can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
@fwyzard , CMSSW_14_1_X IBs are configured to not change the micro-archs in dev area. As mentioned in the core sw meeting, you need to run the following to force change this behaviour
In |
I see, thanks. Why do we need to do both
and
? Can we make the first imply the second ? |
just to not have user accidently pick up x86-64-v3 micro-arch when switching between dev areas (MULTIARCHS and Default IBs's dev area). Note that |
Sure. What I meant is, can we make |
Setting
USER_SCRAM_TARGET=x86-64-v3
works if used directly within an IB, but it does not work if used with a development area.base IB
development area
x86-64-v3
does not show up.The text was updated successfully, but these errors were encountered: