-
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
{2023.06,zen4} foss/2022b #567
base: 2023.06-software.eessi.io
Are you sure you want to change the base?
{2023.06,zen4} foss/2022b #567
Conversation
Instance
|
Instance
|
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen4 |
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
I expect the OpenBLAS tests to fail here, see also notes available in https://gitlab.com/eessi/support/-/issues/37 |
GCC build failed with |
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen4 |
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
5167efa
to
09cacc2
Compare
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen4 |
Updates by the bot instance
|
bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen4 |
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
Problem fixed by #573, so time to try again... bot: build repo:eessi.io-2023.06-software arch:x86_64/amd/zen4 |
Updates by the bot instance
|
Updates by the bot instance
|
New job on instance
|
@boegel Should we close this? I thought we'd decided not to support |
I guess we could (unless we want to figure out how to fix the broken tests for older OpenBLAS versions, which is the main issue here), but shouldn't we then also come up with a way to generate fake module files that clearly mention that the |
Is OpenBLAS the only problem? We can sidestep the issue by forcing a Zen3 build (with a |
Another options is to symlink in the entire set of Zen3 modules for |
No description provided.