-
Notifications
You must be signed in to change notification settings - Fork 50
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
Allow EESSI-extend to work even when LMOD_EXACT_MATCH is set #747
Allow EESSI-extend to work even when LMOD_EXACT_MATCH is set #747
Conversation
Instance
|
Instance
|
Instance
|
bot: build repo:eessi.io-2023.06-software arch:zen4 |
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
bot: build repo:eessi.io-2023.06-software arch:zen3 |
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
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.
Tested this locally, it works. First, installed a new EESSI-extend with the old EESSI-extend:
module load EasyBuild/4.9.3
module load EESSI-extend/2023.06-easybuild
unset EBROOTEESSIMINEXTEND
eb ./EESSI-extend-2023.06-easybuild.eb --force
Note that my current dir was this feature branch.
Then:
module purge
module use /home/casparl/eessi/versions/2023.06/software/linux/x86_64/amd/zen2/modules/all/
module load EESSI-extend/2023.06-easybuild
Works like a charm :)
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
|
bot: build repo:eessi.io-2023.06-software arch:zen4 |
Updates by the bot instance
|
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
bot: build repo:eessi.io-2023.06-software arch:zen3 |
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
That one also failed. I don't know what's going on here. I've added write permissions (for everyone), changed the ownership to first the eessi user and later the user id of the bot, but nothing seems to work. Usually this does solve those issues... |
If we want to get this ingested/merged soon, the only other workaround that I can think of is removing the entire |
@bedroge as in: you'd do that manually, right? Maybe make a tarball first, so we can restore it if we want (or can you undo such a transaction in some way?). Then, go right ahead. I haven't seen this issue before, I really don't understand what's special about this case that we see it here. But if we can apply a workaround, I would. (if it pops up once more in another PR, we should investigate further and solve the root cause) |
bot: build repo:eessi.io-2023.06-software arch:aarch64/generic |
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
|
New job on instance
|
New job on instance
|
New job on instance
|
New job on instance
|
Yes, it's a manual operation and we can easily roll back if necessary. I've just done this, hopefully the rebuilds will succeed this time... It definitely happened before, so I'd really like to have this fixed, but I've been looking into this before and I really have no clue what's going on and why it's only happening in some cases. See #556. While just going through that issue again, I actually found that we hit the same issue before with EESSI-extend, and I also had to remove some files manually. For Python bundles, just changing the permissions is usually sufficient. |
Label |
PR merged! Moved |
PR merged! Moved |
PR merged! Moved |
Fixes #746