Skip to content

update eb_hooks.py for memory expensive builds of jax #25

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

update eb_hooks.py for memory expensive builds of jax #25

wants to merge 2 commits into from

Conversation

laraPPr
Copy link
Contributor

@laraPPr laraPPr commented Jun 27, 2025

No description provided.

@laraPPr
update eb_hooks.py for memory expensive builds of jax
b42a7a2 
Signed-off-by: laraPPr <lara.peeters@ugent.be>
@laraPPr laraPPr added the 2023.06-software.eessi.io 2023.06 version of software.eessi.io label Jun 27, 2025
This was referenced Jun 27, 2025
Closed
Open
@laraPPr
test eb_hooks.py with test easystack
7769117 
Signed-off-by: laraPPr <lara.peeters@ugent.be>
@laraPPr
Copy link
Contributor Author

laraPPr commented Jun 27, 2025

bot: help

@eessi-bot-aws
Copy link

eessi-bot-aws bot commented Jun 27, 2025 •
edited
Loading

Updates by the bot instance eessi-bot-mc-aws (click for details)

  • received bot command help from laraPPr

    • expanded format: help

  • handling command help resulted in:
    How to send commands to bot instances

    • Commands must be sent with a new comment (edits of existing comments are ignored).
    • A comment may contain multiple commands, one per line.
    • Every command begins at the start of a line and has the syntax bot: COMMAND [ARGUMENTS]*
    • Currently supported COMMANDs are: help, build, show_config, status

    For more information, see https://www.eessi.io/docs/bot

@eessi-bot-deucalion
Copy link

eessi-bot-deucalion bot commented Jun 27, 2025 •
edited
Loading

Updates by the bot instance eessi-bot-deucalion (click for details)

  • received bot command help from laraPPr

    • expanded format: help

  • handling command help resulted in:
    How to send commands to bot instances

    • Commands must be sent with a new comment (edits of existing comments are ignored).
    • A comment may contain multiple commands, one per line.
    • Every command begins at the start of a line and has the syntax bot: COMMAND [ARGUMENTS]*
    • Currently supported COMMANDs are: help, build, show_config, status

    For more information, see https://www.eessi.io/docs/bot

@eessi-bot-surf
Copy link

eessi-bot-surf bot commented Jun 27, 2025 •
edited
Loading

Updates by the bot instance eessi-bot-surf (click for details)

  • received bot command help from laraPPr

    • expanded format: help

  • handling command help resulted in:
    How to send commands to bot instances

    • Commands must be sent with a new comment (edits of existing comments are ignored).
    • A comment may contain multiple commands, one per line.
    • Every command begins at the start of a line and has the syntax bot: COMMAND [ARGUMENTS]*
    • Currently supported COMMANDs are: help, build, show_config, status

    For more information, see https://www.eessi.io/docs/bot

@eessi-bot-jsc
Copy link

eessi-bot-jsc bot commented Jun 27, 2025 •
edited
Loading

Updates by the bot instance eessi-bot-jsc (click for details)

  • received bot command help from laraPPr

    • expanded format: help

  • handling command help resulted in:
    How to send commands to bot instances

    • Commands must be sent with a new comment (edits of existing comments are ignored).
    • A comment may contain multiple commands, one per line.
    • Every command begins at the start of a line and has the syntax bot: COMMAND [ARGUMENTS]*
    • Currently supported COMMANDs are: help, build, show_config, status

    For more information, see https://www.eessi.io/docs/bot

@laraPPr
Copy link
Contributor Author

laraPPr commented Jun 27, 2025

bot: build repo:eessi.io-2023.06-software arch:aarch64/neoverse_v1 instance:eessi-bot-mc-aws
bot: build repo:eessi.io-2023.06-software arch:zen4 instance:eessi-bot-mc-azure

@eessi-bot-aws
Copy link

eessi-bot-aws bot commented Jun 27, 2025 •
edited
Loading

New job on instance eessi-bot-mc-aws for CPU micro-architecture aarch64-neoverse_v1 for repository eessi.io-2023.06-software in job dir /project/def-users/SHARED/jobs/2025.06/pr_25/72376

date job status comment
Jun 27 14:52:41 UTC 2025 submitted job id 72376 awaits release by job manager
Jun 27 14:53:15 UTC 2025 released job awaits launch by Slurm scheduler
Jun 27 14:59:23 UTC 2025 running job 72376 is running
Jun 27 15:05:33 UTC 2025 finished
😢 FAILURE (click triangle for details)
Details
✅ job output file slurm-72376.out
✅ no message matching FATAL:
❌ found message matching ERROR:
✅ no message matching FAILED:
✅ no message matching required modules missing:
❌ no message matching No missing installations
✅ found message matching .tar.gz created!
Artefacts
eessi-2023.06-software-linux-aarch64-neoverse_v1-17510363870.tar.gzsize: 0 MiB (17444 bytes)
entries: 1
modules under 2023.06/software/linux/aarch64/neoverse_v1/modules/all
no module files in tarball
software under 2023.06/software/linux/aarch64/neoverse_v1/software
no software packages in tarball
other under 2023.06/software/linux/aarch64/neoverse_v1
2023.06/init/easybuild/eb_hooks.py
Jun 27 15:05:33 UTC 2025 test result
😁 SUCCESS (click triangle for details)
ReFrame Summary
[ OK ] ( 1/10) EESSI_LAMMPS_lj %device_type=cpu %module_name=LAMMPS/29Aug2024-foss-2023b-kokkos %scale=1_node /aeb2d9df @BotBuildTests:aarch64_neoverse_v1+default
P: perf: 985.161 timesteps/s (r:0, l:None, u:None)
[ OK ] ( 2/10) EESSI_LAMMPS_lj %device_type=cpu %module_name=LAMMPS/2Aug2023_update2-foss-2023a-kokkos %scale=1_node /04ff9ece @BotBuildTests:aarch64_neoverse_v1+default
P: perf: 978.355 timesteps/s (r:0, l:None, u:None)
[ OK ] ( 3/10) EESSI_OSU_coll %benchmark_info=mpi.collective.osu_allreduce %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023b %scale=1_node %device_type=cpu /775175bf @BotBuildTests:aarch64_neoverse_v1+default
P: latency: 3.12 us (r:0, l:None, u:None)
[ OK ] ( 4/10) EESSI_OSU_coll %benchmark_info=mpi.collective.osu_allreduce %module_name=OSU-Micro-Benchmarks/7.1-1-gompi-2023a %scale=1_node %device_type=cpu /52707c40 @BotBuildTests:aarch64_neoverse_v1+default
P: latency: 3.16 us (r:0, l:None, u:None)
[ OK ] ( 5/10) EESSI_OSU_coll %benchmark_info=mpi.collective.osu_alltoall %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023b %scale=1_node %device_type=cpu /b1aacda9 @BotBuildTests:aarch64_neoverse_v1+default
P: latency: 4.3 us (r:0, l:None, u:None)
[ OK ] ( 6/10) EESSI_OSU_coll %benchmark_info=mpi.collective.osu_alltoall %module_name=OSU-Micro-Benchmarks/7.1-1-gompi-2023a %scale=1_node %device_type=cpu /c6bad193 @BotBuildTests:aarch64_neoverse_v1+default
P: latency: 4.41 us (r:0, l:None, u:None)
[ OK ] ( 7/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_latency %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023b %scale=1_node /15cad6c4 @BotBuildTests:aarch64_neoverse_v1+default
P: latency: 0.42 us (r:0, l:None, u:None)
[ OK ] ( 8/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_latency %module_name=OSU-Micro-Benchmarks/7.1-1-gompi-2023a %scale=1_node /6672deda @BotBuildTests:aarch64_neoverse_v1+default
P: latency: 0.39 us (r:0, l:None, u:None)
[ OK ] ( 9/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_bw %module_name=OSU-Micro-Benchmarks/7.2-gompi-2023b %scale=1_node /2a9a47b1 @BotBuildTests:aarch64_neoverse_v1+default
P: bandwidth: 36419.58 MB/s (r:0, l:None, u:None)
[ OK ] (10/10) EESSI_OSU_pt2pt_CPU %benchmark_info=mpi.pt2pt.osu_bw %module_name=OSU-Micro-Benchmarks/7.1-1-gompi-2023a %scale=1_node /1b24ab8e @BotBuildTests:aarch64_neoverse_v1+default
P: bandwidth: 33671.4 MB/s (r:0, l:None, u:None)
[ PASSED ] Ran 10/10 test case(s) from 10 check(s) (0 failure(s), 0 skipped, 0 aborted)
Details
✅ job output file slurm-72376.out
❌ found message matching ERROR:
✅ no message matching [\s*FAILED\s*].*Ran .* test case

@laraPPr
Copy link
Contributor Author

laraPPr commented Jun 27, 2025

@ocaisa why is that eb_hooks check failing?

@ocaisa
Copy link
Member

ocaisa commented Jun 27, 2025

The check will only pass once the hooks have been ingested (similar to how missing installations works)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
2023.06-software.eessi.io 2023.06 version of software.eessi.io
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@laraPPr @ocaisa