Skip to content

Syncing code-base and CVMFS repository with EESSI (April 2024) #294

@TopRichard

Description

@TopRichard

In January we synced the NESSI code-base with EESSI (see #223 and https://github.com/NorESSI/software-layer/issues?q=label%3Async-with-EESSI+is%3Aclosed). The last PR in that effort was #256 (merged Jan 28, 10:08 PM). Since then 49 PRs have been merged in EESSI, see https://github.com/EESSI/software-layer/pulls?q=is%3Apr+merged%3A%3E2024-01-27+sort%3Aupdated-asc+ The list includes PRs for adding software to EESSI as well as some for updating the code-base (or both). Below we list the PRs in the order in which they were merged (note, it seems some where updated after they got merged) and classify them as code, software and other. Then for each of the PRs to handle (primarily code and other) we describe the actions performed for syncing NESSI (TODO double-check PRs which require changes on CVMFS and mark them with cvmfs):

TO BE DONE

foss/2023a

foss/2023b

mixed


DONE


Notes

  • April 11: most code changes done
  • April 12/13:
    1. rebuild GCC ✅
    2. rebuild OpenMPI ✅
    • for rebuilding we use similar mechanism as in EESSI (rebuilds/eessi...), but we need to remove the software first from the CVMFS repo
  • April 14:
    1. do 529+532 ✅
  • afterwards missing softwares
    • most done by April 18
    • the last packages fail for different reasons on different architectures and by different bot instances
      • if possible split PRs or build some dependencies to make some progress towards completion of the builds
  • also check new PRs: https://github.com/EESSI/software-layer/pulls?q=is%3Apr+merged%3A%3E2024-04-07+sort%3Aupdated-asc
  • do a final file-by-file check for differences and document them

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