-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
RelVals 180.1, 181.1: crash on non-default architectures #44863
Comments
cms-bot internal usage |
A new Issue was created by @iarspider. @rappoccio, @smuzaffar, @Dr15Jones, @makortel, @sextonkennedy, @antoniovilela can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
assign core,generators,pdmv,upgrade |
New categories assigned: core,generators,pdmv,upgrade @Dr15Jones,@AdrianoDee,@alberto-sanchez,@bbilin,@GurpreetSinghChahal,@sunilUIET,@miquork,@makortel,@mkirsano,@menglu21,@SiewYan,@smuzaffar,@srimanob,@subirsarkar you have been requested to review this Pull request/Issue and eventually sign? Thanks |
Just to add here the error message from the log
|
On el9 release areas it fails because it can't find a shared library:
It appears to me like we need to consider changing the running of gridpacks to be done within containers in order to avoid OS incompatibilities. |
This issue should now be solved with #44900 . |
I'm not seeing these problems anymore. Thanks! |
+core |
+Upgrade |
+pdmv |
+1 |
This issue is fully signed and ready to be closed. |
RelVals 180.1, 181.1, modified in #44671, are failing on for non-default architectures (e.g. slc7_amd64_gcc12).
This is expected, since these relvals use gridpacks, which are only available for default architecture.
Should we add these two RelVals to the list of "known failures"?
The text was updated successfully, but these errors were encountered: