-
Notifications
You must be signed in to change notification settings - Fork 7
Test permissions in a64fx tarball #37
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
Conversation
Instance
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-deucalion architecture:aarch64/a64fx |
Updates by the bot instance
|
New job on instance
|
This looks fine... |
One more attempt to reproduce the issue by copying some files to a completely new dir (as that's a better representation of the state where the issue popped up in #30). bot: build repo:eessi.io-2025.06-software instance:eessi-bot-deucalion architecture:aarch64/a64fx |
Updates by the bot instance
|
New job on instance
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-deucalion architecture:aarch64/a64fx |
Updates by the bot instance
|
New job on instance
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-deucalion architecture:aarch64/a64fx |
Updates by the bot instance
|
New job on instance
|
bot: build repo:eessi.io-2025.06-software instance:eessi-bot-deucalion architecture:aarch64/a64fx |
Updates by the bot instance
|
New job on instance
|
So, by using the same approach as we use elsewhere in the script (by using |
Solved this issue in #38, closing this PR. |
PR merged! Moved |
The a64fx tarbal produced in #30 had weird permissions on some files; see https://gitlab.com/eessi/support/-/issues/56#note_3 for more details. In order to test if it's because of outdated build scripts or for instance an umask issue, I'm doing another build here.