Don't print messages from hook in --terse mode

[Flamefire]

The output from the hook such as "Using custom configure options" makes the output not machine-readable which it should be in --terse mode.

Check the option in a hook-function before calling the original one

[ocaisa]

LGTM it will need a sync with the target branch (after #85 is merged)

[ocaisa]

@Flamefire Can you sync this now and I will get it deployed

[ocaisa]

bot: build repo:eessi.io-2025.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2
bot: build repo:eessi.io-2023.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2

[eessi-bot-aws]

New job on instance eessi-bot-mc-aws for repository eessi.io-2025.06-software
Building on: amd-zen2
Building for: x86_64/amd/zen2
Job dir: /project/def-users/SHARED/jobs/2025.09/pr_82/90780

date	job status	comment
Sep 18 13:25:30 UTC 2025	submitted	job id 90780 awaits release by job manager
Sep 18 13:26:03 UTC 2025	released	job awaits launch by Slurm scheduler
Sep 18 13:31:11 UTC 2025	running	job 90780 is running
Sep 18 13:32:12 UTC 2025	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file slurm-90780.out ✅ no message matching FATAL: ✅ no message matching ERROR: ✅ no message matching FAILED: ✅ no message matching required modules missing: ✅ found message(s) matching No missing installations ✅ found message matching .tar.gz created! Artefacts eessi-2025.06-software-linux-x86_64-amd-zen2-17582022740.tar.gz size: 0 MiB (20203 bytes) entries: 1 modules under 2025.06/software/linux/x86_64/amd/zen2/modules/all no module files in tarball software under 2025.06/software/linux/x86_64/amd/zen2/software no software packages in tarball reprod directories under 2025.06/software/linux/x86_64/amd/zen2/reprod no reprod directories in tarball other under 2025.06/software/linux/x86_64/amd/zen2 2025.06/init/easybuild/eb_hooks.py
Sep 18 13:32:12 UTC 2025	test result	😢 FAILURE (click triangle for details) Reason EESSI test suite was not run, test step itself failed to execute. Details ✅ job output file slurm-90780.out ❌ found message matching ERROR: ✅ no message matching [\s*FAILED\s*].*Ran .* test case
Sep 18 13:41:05 UTC 2025	uploaded	transfer of eessi-2025.06-software-linux-x86_64-amd-zen2-17582022740.tar.gz to S3 bucket succeeded

[eessi-bot-aws]

New job on instance eessi-bot-mc-aws for repository eessi.io-2023.06-software
Building on: amd-zen2
Building for: x86_64/amd/zen2
Job dir: /project/def-users/SHARED/jobs/2025.09/pr_82/90781

date	job status	comment
Sep 18 13:25:34 UTC 2025	submitted	job id 90781 awaits release by job manager
Sep 18 13:26:01 UTC 2025	released	job awaits launch by Slurm scheduler
Sep 18 13:27:05 UTC 2025	running	job 90781 is running
Sep 18 13:30:08 UTC 2025	finished	😁 SUCCESS (click triangle for details) Details ✅ job output file slurm-90781.out ✅ no message matching FATAL: ✅ no message matching ERROR: ✅ no message matching FAILED: ✅ no message matching required modules missing: ✅ found message(s) matching No missing installations ✅ found message matching .tar.gz created! Artefacts eessi-2023.06-software-linux-x86_64-amd-zen2-17582019970.tar.gz size: 0 MiB (20198 bytes) entries: 1 modules under 2023.06/software/linux/x86_64/amd/zen2/modules/all no module files in tarball software under 2023.06/software/linux/x86_64/amd/zen2/software no software packages in tarball reprod directories under 2023.06/software/linux/x86_64/amd/zen2/reprod no reprod directories in tarball other under 2023.06/software/linux/x86_64/amd/zen2 2023.06/init/easybuild/eb_hooks.py
Sep 18 13:30:08 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:x86_64_amd_zen2+default P: perf: 436.108 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:x86_64_amd_zen2+default P: perf: 263.665 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:x86_64_amd_zen2+default P: latency: 2.8 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:x86_64_amd_zen2+default P: latency: 2.92 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:x86_64_amd_zen2+default P: latency: 4.75 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:x86_64_amd_zen2+default P: latency: 4.24 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:x86_64_amd_zen2+default P: latency: 0.6 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:x86_64_amd_zen2+default P: latency: 0.58 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:x86_64_amd_zen2+default P: bandwidth: 7365.27 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:x86_64_amd_zen2+default P: bandwidth: 7239.8 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-90781.out ✅ no message matching ERROR: ✅ no message matching [\s*FAILED\s*].*Ran .* test case
Sep 18 13:41:13 UTC 2025	uploaded	transfer of eessi-2023.06-software-linux-x86_64-amd-zen2-17582019970.tar.gz to S3 bucket succeeded

[bedroge]

The builds in EESSI/software-layer#1177 (comment) (which use EB 4.8.2) are failing with:

    if not build_option('terse'):
           ^^^^^^^^^^^^^^^^^^^^^
  File "/cvmfs/software.eessi.io/versions/2023.06/software/linux/aarch64/a64fx/software/EasyBuild/4.8.2/lib/python3.11/site-packages/easybuild/tools/config.py", line 621, in build_option
    raise EasyBuildError(error_msg)
easybuild.tools.build_log.EasyBuildError: "Undefined build option: 'terse'. Make sure you have set up the EasyBuild configuration using set_up_configuration() (from easybuild.tools.options) in case you're not using EasyBuild via the 'eb' CLI."

I'm not sure when that option was added, but it looks like we need to be more careful here?

edit: this was added in EB 4.9.1, see easybuilders/easybuild-framework#4407.

another edit: #90 should fix this.