add YAML file to keep track of known issues in EESSI pilot 2023.06

[laraPPr]

No description provided.

[eessi-bot]

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

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

[boegel]

@laraPPr Nitpicking, but I would rename eessi-2023.06-known_issues.yml to eessi-2023.06-known-issues.yml, the mix of - and _ looks a bit weird.

Maybe we want an issue and info field for each entry, to avoid that you have to open the issue to know what the known issue is about?

Something like:

aarch64/generic:
    - OpenBLAS/0.3.21-GCC-12.2.0:
      - issue: https://github.com/EESSI/software-layer/issues/314
      - info: "Increased number of non-numerical failures in OpenBLAS test suite compared (345 vs max. 150 on x86_64/*)"

where 345 is replaced with the actual number observed, which can be extracted from the EasyBuild installation log?