add zen4 / AMD Genoa

[hmeiland]

updated tests and config files;

[eessi-bot]

Instance eessi-bot-mc-aws is configured to build:

• arch x86_64/generic for repo eessi-hpc.org-2023.06-compat
• arch x86_64/generic for repo eessi-hpc.org-2023.06-software
• arch x86_64/generic for repo eessi.io-2023.06-compat
• arch x86_64/generic for repo eessi.io-2023.06-software
• arch x86_64/intel/haswell for repo eessi-hpc.org-2023.06-compat
• arch x86_64/intel/haswell for repo eessi-hpc.org-2023.06-software
• arch x86_64/intel/haswell for repo eessi.io-2023.06-compat
• arch x86_64/intel/haswell for repo eessi.io-2023.06-software
• arch x86_64/intel/skylake_avx512 for repo eessi-hpc.org-2023.06-compat
• arch x86_64/intel/skylake_avx512 for repo eessi-hpc.org-2023.06-software
• arch x86_64/intel/skylake_avx512 for repo eessi.io-2023.06-compat
• arch x86_64/intel/skylake_avx512 for repo eessi.io-2023.06-software
• arch x86_64/amd/zen2 for repo eessi-hpc.org-2023.06-compat
• arch x86_64/amd/zen2 for repo eessi-hpc.org-2023.06-software
• arch x86_64/amd/zen2 for repo eessi.io-2023.06-compat
• arch x86_64/amd/zen2 for repo eessi.io-2023.06-software
• arch x86_64/amd/zen3 for repo eessi-hpc.org-2023.06-compat
• arch x86_64/amd/zen3 for repo eessi-hpc.org-2023.06-software
• arch x86_64/amd/zen3 for repo eessi.io-2023.06-compat
• arch x86_64/amd/zen3 for repo eessi.io-2023.06-software
• arch aarch64/generic for repo eessi-hpc.org-2023.06-compat
• arch aarch64/generic for repo eessi-hpc.org-2023.06-software
• arch aarch64/generic for repo eessi.io-2023.06-compat
• arch aarch64/generic for repo eessi.io-2023.06-software
• arch aarch64/neoverse_n1 for repo eessi-hpc.org-2023.06-compat
• arch aarch64/neoverse_n1 for repo eessi-hpc.org-2023.06-software
• arch aarch64/neoverse_n1 for repo eessi.io-2023.06-compat
• arch aarch64/neoverse_n1 for repo eessi.io-2023.06-software
• arch aarch64/neoverse_v1 for repo eessi-hpc.org-2023.06-compat
• arch aarch64/neoverse_v1 for repo eessi-hpc.org-2023.06-software
• arch aarch64/neoverse_v1 for repo eessi.io-2023.06-compat
• arch aarch64/neoverse_v1 for repo eessi.io-2023.06-software

[ocaisa]

I don't think we've actually thought about what to do if someone wants to introduce a new architecture into EESSI production. This is another use case for a development repo that sits on top of production EESSI, you figure out how far you can get there and then when things are mature you can rebuild them into production.

[boegel]

@hmeiland Somehow there's a merge conflict now here...

[boegel]

I don't think we've actually thought about what to do if someone wants to introduce a new architecture into EESSI production. This is another use case for a development repo that sits on top of production EESSI, you figure out how far you can get there and then when things are mature you can rebuild them into production.

That's totally orthogonal to this PR, no?

Let's follow up on that in https://gitlab.com/eessi/support/-/issues/37

[ocaisa]

That's totally orthogonal to this PR, no?

Let's follow up on that in https://gitlab.com/eessi/support/-/issues/37

Almost orthogonal but not quite, current CI assumes that if something is supported (in CI) by archdetect, then there should be a corresponding software directory. It was a bit looser before (checking that it had to be available in some EESSI version, which was to accommodate the deprecation of Power).

[hmeiland]

moved to #451

[eessi-bot]

Updates by the bot instance eessi-bot-mc-aws (click for details)

• account hmeiland has NO permission to send commands to the bot