Skip to content

Conference call notes 20240717

Jump to bottom
Alex Domingo edited this page Jul 17, 2024 · 1 revision

(back to Conference calls)

Notes on the 250th EasyBuild conference call, Wednesday 17 July 2024 (08:00 UTC)

Attendees

List of attendees (10):

  • Alex Domingo (Vrije Universiteit Brussel, Belgium)
  • Alan O'Cais (CECAM)
  • Simon Branford (Univ. of Birmingham, UK)
  • Jasper Grimm (University of York, UK)
  • Alexander Grund
  • Thomas Hoffmann (EMBL)
  • Kurt Lust (UAntwerpen, Belgium + LUMI User Support Team)
  • Davide Grassano
  • Cintia Willemyns (Vrije Universiteit Brussel, Belgium)
  • Alexander Strube

Agenda

  • overview of recent developments
  • outlook to EasyBuild 5.0 release
  • 2024a update of common toolchains
  • Q&A

Recent developments

  • latest EasyBuild release: 4.9.2 (12 June 2024)
  • next EasyBuild release: hoping to make that EasyBuild 5.0.0 (but not before Aug'24, at best)
  • EasyBuild v5.0.0
    • detailed notes on latest developments in https://hackmd.io/tZtz6vMmRfGL6N9Rf__OEA
    • to test development version of EasyBuild 5.0: 
      # set up Python virtual environment, and jump into it
python3 -m venv eb5
source eb5/bin/activate

# install EasyBuild 5.0 development version into it
pip install https://github.com/easybuilders/easybuild-framework/archive/5.0.x.tar.gz
pip install https://github.com/easybuilders/easybuild-easyblocks/archive/5.0.x.tar.gz
pip install https://github.com/easybuilders/easybuild-easyconfigs/archive/5.0.x.tar.gz

# go!
eb --version

Merged PRs

  • docs (merged PRs)

    • ...

  • framework (merged PRs)

    • bug fixes
      • ...
    • enhancements
      • reuse pre-computed checksums (PR #4569)
    • changes
      • ...
    • code cleanup
      • ...
    • EasyBuild 5.0 (5.0.x branch)
      • ...

  • easyblocks (merged PRs)

    • bug fixes
      • ...
    • changes
      • ...
    • new easyblocks
      • ...
    • EasyBuild 5.0
      • ...

  • easyconfigs (merged PRs)

    • over 50 easyconfig PRs were merged since last conf call
    • we reached PR 21000! 🎉
    • bug fixes/reports
      • disable auto-vectorizer (-ftree-vectorize) for OpenFOAM v10 + v11 when using toolchain that with GCC >= 11 (PR #20958)
    • enhancements
      • ...
    • (noteworthy) new software
    • noteworthy software updates
      • Progress popullating 2024a:
        • {lib}[GCCcore/13.3.0] LLVM v18.1.8, Mesa v24.1.3, ... (PR #21000)
        • {devel,math}[GCCcore/13.3.0] Doxygen v1.11.0, Eigen v3.4.0, GDRCopy v2.4.1, ... (PR #20633)
        • {devel,vis}[GCCcore/13.3.0] X11 v20240607, intltool v0.51.0 (PR #20977)
        • {lang,tools}[GCCcore/13.3.0] Perl-bundle-CPAN v5.38.2, groff v1.23.0 (PR #20975)
    • changes
      • ...

Open (active) PRs

  • docs (open PRs + issues)

    • ...

  • framework (open PRs + issues)

    • bug fixes
      • ...
    • enhancements
      • ...
    • changes
      • ...
    • EasyBuild 5.0
      • ...

  • easyblocks (open PRs + issues)

    • bug fixes
      • ...
    • enhancements
      • ...
    • updates
      • ...
    • changes
      • ...
    • new
      • ...
    • EasyBuild 5.0
      • ...

  • easyconfigs (open PRs + issues)

    • bug fixes/reports
      • ...
    • enhancements
      • ...
    • (noteworthy) new software
      • ...
    • software updates
      • jax 0.4.25 w/ CUDA (PR #20119)
        • do we just need to accept that the jax test suite requires a substantial amount of GPU memory?
        • we could emit a build info message that mentions that test suite may fail (and suggest --ignore-test-failure)
      • ...
    • changes
      • ...

2024a common toolchains

  • GCC 13.3 as a base
  • latest version of all components (except GCC, not using 14.1):
    • foss/2024a (candidate toolchain foss/2024.05 merged: PR #20646)
      • GCC 13.3 (20240521) + binutils 2.42 (20240129)
      • OpenMPI 5.0.3 (20240408)
        • PMIx 5.0.2 (20240321), UCX 1.16.0 (20240415), libfabric 1.21.0 (20240329)
      • FlexiBLAS 3.4.3 (20240521) + OpenBLAS 0.3.27 (20240404) + BLIS 1.0 (20240506)
      • FFTW 3.3.10 (20210914)
      • ScaLAPACK 2.2.0 (20220202)
    • intel/2024a
      • GCCcore 13.3 + binutils 2.42
      • Intel C/C++/Fortran compilers 2024.1.0 (20240327)
        • some trouble arose when combining C/C++ 2024.1.2 with Fortran 2024.1.0
        • bundle provided by Intel sticks to 2024.1.0 for both
        • we should take a look at the release notes
      • Intel MPI 2021.12.1 (20240424)
      • Intel MKL 2024.1.0 (20240327)
      • easyconfig PRs towards candidate for intel/2024a: PR #20919 + PR #20926

Q&A / others

  • Alan, Davide: developing a new more powerfull easyblock to install LLVM. What support should we provide for older LLVM versions and variants in this new one?

    • we currently have the following related easyblocks: clang, clang_aoc and llvm
    • they are not related between (no inheritance)
    • llvm easyblock is quite minimal, just configure step to configure compilation of llvm compiler
    • new easyblock can easily overhaul the llvm easyblock maintain current functionality
    • maybe add option to switch from a minimal build to the full LLVM project

  • Alexander: PR to make builds of PyTorch more reliable by explicitly setting the build type

  • Alexander: old PR that needs some love from maintainers

  • Alexander: having None as value of some checksum is currently broken for definitions of checksums as dictionaries

  • Alex: what do we do the develop branch? merge 5.0 into it already?

    • Alan: seems the right to do to put pressure on development of 5.0
    • Simon: we need to consider --from-pr-*** options, so that they keep working. In 4.9.2 we already put safeguards for those.
    • Simon: we should get closer to publishing an RC before merging 5.0.x into develop. That will make it easier for users to transition if they want/need to use code from develop.
    • Alan: what will happen to old open PRs?
    • Alex: good opportunity to reset and archive them with a v4 label
    • Simon: for framework is a good opportunity to go through open PRs and see if anything is worth salvaging
    • Alex: we should try to make RC and move 5.0.x into develop after summer break; that will help with development of 5.0 and reduce overhead from all those fixes that land into develop (for v4)
Clone this wiki locally