-
Notifications
You must be signed in to change notification settings - Fork 52
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
Add functionality for rebuilding software: try it on OpenMPI 4.1.x to fix smcuda
issue
#488
Add functionality for rebuilding software: try it on OpenMPI 4.1.x to fix smcuda
issue
#488
Conversation
Instance
|
bot: build repo:eessi.io-2023.06-software arch:aarch64/neoverse_v1 |
Updates by the bot instance
|
New job on instance
|
bot: build repo:eessi.io-2023.06-software arch:aarch64/neoverse_v1 |
Updates by the bot instance
|
New job on instance
|
bot: build repo:eessi.io-2023.06-software arch:aarch64/neoverse_v1 |
Updates by the bot instance
|
New job on instance
|
bot: build repo:eessi.io-2023.06-software arch:aarch64/neoverse_v1 |
Updates by the bot instance
|
New job on instance
|
Ah, this doesn't work, we're changing back to |
…op back to regular user and do installations
bot: build repo:eessi.io-2023.06-software arch:aarch64/neoverse_v1 |
bot: build repo:eessi.io-2023.06-software arch:aarch64/generic |
Updates by the bot instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
Before closing/merging the staging PRs, I will manually open a transaction on the Stratum and remove the following directories:
In the same transaction, I'll then extract the 8 tarballs from this PRs, and update the Lmod caches. Finally, I'll publish the transaction. The staging PRs can then be either closed (in that case they'll be rejected/ignored) or even merged (then the tarballs will just be ingested again, which should be harmless). |
Just to log the full procedure: we decided to do this manually, so we can first remove the current OpenMPI installations. If we would deploy this PR automatically, the new files would be ingested (and overwrite existing ones), but old files that are not overwritten would remain in those prefixes. Not a huge deal, but this time, we figured to do a clean install manually. The steps we are taking for that are:
|
This is the manually created script that I used to remove the old versions, extract the tarballs containing the new versions, and update the Lmod caches:
|
All tarballs have been published. 🎉 |
Ok, now we only need #513 to fix our CI, and then we can merge this... |
…-layer into software_rebuilds
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Attempt to implement a solution for #312 with
--fakeroot
.