-
Notifications
You must be signed in to change notification settings - Fork 1
functionality for rebuilding software #312
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
functionality for rebuilding software #312
Conversation
|
Instance
|
|
Instance
|
|
Instance
|
|
Instance
|
|
bot: build inst:Fram-NESSI repo:nessi-2023.06-swl-deb11 arch:x86_64/intel/broadwell |
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
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
|
|
Despite the seemingly failed builds everything is fine. The FAILURE was only reported because there was no software built at all and hence the architecture specific directory from which a tarball would be created did not exist. For example, for Broadwell we have the following in the slurm output: |
poksumdo
left a comment
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.
Not fully satisfactory, but we need to move on. Should keep #311 updated with nessi.no-2023.06 branch.
This PR is a stripped-down version of #311. It only contains the code we can retain (removed changes to
create_lmodsitepackage.pywhich would create a newSitePackage.lua). It also doesn't rebuild OpenMPI because rebuilding currently does not work as envisioned in #311.This PR syncs NESSI with EESSI. Particularly it combines most of EESSI#488 and EESSI#518.
We test only if the build procedure still works after adding rebuild capabilities. Nothing should be put into a tarball that requires ingesting.