Skip to content

Syncing code-base and CVMFS repository with EESSI (January 2024) #223

Description

@TopRichard

NESSI and EESSI have diverted, so in the attempt of syncing them back as close as possible, the following PRs have been merged:

NOTE: CUDA/NVIDIA MODIFICATIONS ARE NOT TESTED!!!

Test PRs

For now (EESSI Merged PR#454) there exist differences within 74 files as listed below, must carry out resolving those differences carefully:

  • .github/workflows/test-software.eessi.io.yml
  • .github/workflows/test_eessi_container_script.yml
  • .github/workflows/test_licenses.yml
  • .github/workflows/tests_archdetect.yml
  • .github/workflows/tests_scripts.yml
  • EESSI-install-software.sh
  • README.md --> differences are because of NESSI vs EESSI
  • bot/build.sh
  • bot/check-result.sh
  • bot/check-test.sh
  • bot/test.sh
  • bot/inspect.sh
  • build_container.sh
  • check_missing_installations.sh --> differences are because of NESSI vs EESSI
  • configure_easybuild --> addressed in PR#225, requires rebuild of gnuplot as a test(after the removal of Lua)which we already don't have
  • create_directory_tarballs.sh --> addressed in PR#225
  • create_lmodrc.py --> addressed in PR#232 requires some naming changes but will carry that on while testing CUDA modifications
  • create_tarball.sh --> addressed in PR#225
  • easystacks/pilot.nessi.no/2023.06/eessi-2023.06-eb-4.7.2-2021a.yml --> moved to easystacks/pilot.nessi.no/2023.06
  • easystacks/pilot.nessi.no/2023.06/eessi-2023.06-eb-4.7.2-2021b.yml --> moved to easystacks/pilot.nessi.no/2023.06
  • easystacks/pilot.nessi.no/2023.06/eessi-2023.06-eb-4.7.2-2022a.yml --> moved to easystacks/pilot.nessi.no/2023.06
  • easystacks/pilot.nessi.no/2023.06/eessi-2023.06-eb-4.7.2-2022b.yml --> moved to easystacks/pilot.nessi.no/2023.06
  • easystacks/pilot.nessi.no/2023.06/eessi-2023.06-eb-4.7.2-system.yml --> moved to easystacks/pilot.nessi.no/2023.06
  • easystacks/pilot.nessi.no/2023.06/eessi-2023.06-eb-4.8.0-system.yml --> moved to easystacks/pilot.nessi.no/2023.06
  • easystacks/pilot.nessi.no/2023.06/eessi-2023.06-eb-4.8.1-2022a.yml --> moved to easystacks/pilot.nessi.no/2023.06
  • easystacks/pilot.nessi.no/2023.06/eessi-2023.06-eb-4.8.2-2022a.yml --> moved to easystacks/pilot.nessi.no/2023.06
  • easystacks/software.eessi.io/2023.06/README.md
  • easystacks/software.eessi.io/2023.06/eessi-2023.06-eb-4.8.2-001-system.yml --> moved here
  • (LATER) easystacks/software.eessi.io/2023.06/eessi-2023.06-eb-4.8.2-010-CUDA.yml --> Will be handled later
  • easystacks/software.eessi.io/2023.06/eessi-2023.06-eb-4.8.2-2022b.yml --> moved here
  • easystacks/software.eessi.io/2023.06/eessi-2023.06-eb-4.8.2-2023a.yml --> moved here
  • (LATER) easystacks/software.eessi.io/2023.06/eessi-2023.06-eb-4.9.0-001-system.yml --> Will be handled later
  • (LATER) easystacks/software.eessi.io/2023.06/eessi-2023.06-eb-4.9.0-2022b.yml --> Will be handled later
  • (LATER) easystacks/software.eessi.io/2023.06/eessi-2023.06-eb-4.9.0-2023a.yml --> Will be handled later
  • (LATER) easystacks/software.eessi.io/2023.06/eessi-2023.06-eb-4.9.0-2023b.yml --> Will be handled later
  • eb_hooks.py --> addressed in PR#232
  • eessi-2021.06.yml
  • eessi-2021.12.yml
  • eessi_container.sh --> addressed in PR#225, also addresses
    some GPU modifications, check the note in the PR
  • init/Magic_Castle/bash --> addressed in PR#222
  • init/Magic_Castle/eessi_python3 --> addressed in PR#222
  • init/README.md --> addressed in PR#222
  • init/arch_specs/eessi_arch_arm.spec --> addressed in PR#224
  • init/bash --> addressed in PR#224
  • init/eessi_archdetect.sh --> addressed in PR#224
  • init/eessi_defaults --> addressed in PR#218
    difference in EESSI_CVMFS_REPO_OVERRIDE and using archspec instead of archdetect
  • init/eessi_environment_variables --> addressed in PR#224
  • init/eessi_software_subdir_for_host.py --> addressed in PR#222
  • init/minimal_eessi_env --> addressed in PR#222
  • install_scripts.sh --> addressed in PR#232
  • licenses/README.md --> addressed in PR#231
  • licenses/licenses.json --> addressed in PR#231
  • licenses/spdx.py --> addressed in PR#231
  • load_easybuild_module.sh --> addressed in PR#232
  • scripts/gpu_support/nvidia/install_cuda_host_injections.sh --> addressed in PR#232
  • scripts/gpu_support/nvidia/link_nvidia_host_libraries.sh --> addressed in PR#232
  • scripts/utils.sh --> addressed in PR#232
  • tests/archdetect/aarch64/arm/neoverse-n1/AWS-awslinux-graviton2.output --> addressed in PR#231
  • tests/archdetect/aarch64/arm/neoverse-n1/Azure-Ubuntu20-Altra.output --> addressed in PR#231
  • tests/archdetect/aarch64/arm/neoverse-v1/AWS-awslinux-graviton3.output --> addressed in PR#231
  • tests/archdetect/aarch64/neoverse_n1/AWS-awslinux-graviton2.all.output --> addressed in PR#231
  • tests/archdetect/aarch64/neoverse_n1/AWS-awslinux-graviton2.cpuinfo --> addressed in PR#231
  • tests/archdetect/aarch64/neoverse_n1/AWS-awslinux-graviton2.output --> addressed in PR#231
  • tests/archdetect/aarch64/neoverse_n1/Azure-Ubuntu20-Altra.all.output --> addressed in PR#231
  • tests/archdetect/aarch64/neoverse_n1/Azure-Ubuntu20-Altra.cpuinfo --> addressed in PR#231
  • tests/archdetect/aarch64/neoverse_n1/Azure-Ubuntu20-Altra.output --> addressed in PR#231
  • tests/archdetect/aarch64/neoverse_v1/AWS-awslinux-graviton3.all.output --> addressed in PR#231
  • tests/archdetect/aarch64/neoverse_v1/AWS-awslinux-graviton3.cpuinfo --> addressed in PR#231
  • tests/archdetect/aarch64/neoverse_v1/AWS-awslinux-graviton3.output --> addressed in PR#231
  • tests/archdetect/ppc64le/power9le/unknown-power9le.all.output --> addressed in PR#231
  • tests/archdetect/x86_64/amd/zen2/Azure-CentOS7-7V12.all.output --> addressed in PR#231
  • tests/archdetect/x86_64/amd/zen3/Azure-CentOS7-7V73X.all.output --> addressed in PR#231
  • tests/archdetect/x86_64/intel/haswell/archspec-linux-E5-2680-v3.all.output --> addressed in PR#231
  • tests/archdetect/x86_64/intel/skylake_avx512/archspec-linux-6132.all.output --> addressed in PR#231

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions