Skip to content

Sync meeting on EESSI Software layer (2023 09 20)

Jump to bottom
Kenneth Hoste edited this page Oct 5, 2023 · 1 revision

EESSI software layer sync meeting

Meeting (2023-09-20)

  • attending: Kenneth, Lara, Richard, Thomas, Caspar (bit late), Alan (bit late)

  • excused: Bob

  • bot

    • download failures are still annoying (see issue #213)
      • we can largely avoid these by using a shared source path across build jobs + only trigger a single build initially for each PR
    • bot job manager crashes every now and then, see issue #191
      • can work around this by running job manager in a loop in cron job, for now
    • update of README before tagging v0.1

  • merged PRs

    • {2023.06} EasyBuild v4.8.1 + re-install Java/11 with it (PR #333)

  • Open prs

    • R v4.2.0 w/ foss/2021 (PR #335)
      • problems with installation of Xvfb
        • Resolved with easyconfigs PR #18834
        • succesfull tarball for x86_64-generic - others targets are being built now
    • R v4.1.0 w/ foss/2021a (PR #328)
      • Xvfb problem fixed
      • build error for testthat extension in R
        • easy to fix in a pre_single_extension hook (WIP by Kenneth)
    • foss/2023a (PR #334)
      • 1 non-numerical failing test for OpenBLAS (only for x86_64-generic)
      • segfault in DGGES3
      • known issue in OpenBLAS (see issue #4032)
      • not serious enough to block foss/2023a for all targets?
    • WRF-dmpar V4.3 with foss/2021a (PR #290)
      • configure hook updated for recent WRF versions
      • missing build for aarch64/neoverse_v1 (running now)
    • RStudio-Server + R v4.1.0 with foss/2021a (PR #299)
      • should be synced with 2023.06 branch once PR # is merged
    • foss/2022a (PR #310) [Caspar + Kenneth]
      • workaround in place for flaky FFTW tests
      • trouble with building OpenBLAS on aarch64 - known/fixed issue in OpenBLAS?
    • TensorFlow v2.7.1 w/ foss/2021b (PR #321)
      • failing tests on aarch64/* - needs more patches? [Kenneth]
      • are tests also failing with official wheel of TensorFlow 2.7.1 for aarch64
      • should also try TensorFlow 2.8.4 with foss/2021b
    • ESPResSo w/ foss/2022a (PR #331)
      • should wait until PR #310 is merged
    • ESPResSo w/ foss/2021a (PR #332)
      • missing --from-pr since easyconfig is not included in EasyBuild v4.8.0 yet
      • or use EasyBuild v4.8.1 instead?

  • other

    • how will we keep track of which installs have known issues, and which are missing?
      • eessi-2023.06-known-issues.yml + eessi-2023.06-missing.yml in software-layer repo?
      • marking installations as missing could be specified in yml file that is used to generate easystack files fed into EasyBuild
        • input file eessi-2023.06-2023a.yml 
          easybuild:
    version: 4.8.0
        easyconfigs:
            - foss-2023a
        • generate eessi-2023.06-eb480-2023a-x86_64.yml 
          easyconfigs:
    foss-2023a:
      • for missing installations, we could generate a fake module file instead (based on eessi-2023.06-missing.yml) 
        aarch64/generic:
    foss-2022a:
        issue: 123
aarch64/neoverse-n1:
    foss-2022a:
        issue: 123
aarch64/neoverse-v1:
    foss-2022a:
        issue: 123
      • consolidate easystack files into a single one per toolchain generations
        • nice to have for now
      • we should somehow only use the easystack file that was changed
        • to help avoid hitting GitHub rate limit
        • based on git diff with target branch?
        • bot needs to provide some extra info, like target branch of PR
          • not really, info is already there (patch file used by bot to set up working directory)
        • in NESSI sometimes 'from-pr' options are commented out to help avoid this

Previous meetings

Clone this wiki locally