Skip to content

fix: show Lmod's reason when a build cannot load a module - #67

Merged
HaoZeke merged 1 commit into
mainfrom
fix/module-load-reason
Nov 17, 2026
Merged

HaoZeke merged 1 commit into
mainfrom
fix/module-load-reason

Conversation

@HaoZeke

@HaoZeke HaoZeke commented Nov 17, 2026

Copy link
Copy Markdown
Collaborator

A build loaded the stack module and EESSI-extend with stdout and stderr sent to /dev/null, which kept Lmod's reason out of a load that failed: a module missing from MODULEPATH, or a load hook that failed, read only eb-local: could not load EESSI/2026.06.

A build keeps a load's stderr in the workspace and prints it, indented, under that line when the load fails. A load that works stays quiet.

A build loaded the stack module and EESSI-extend with stdout and
stderr sent to /dev/null, which keeps the modules' messages out of a
build that works, and Lmod's reason out of one that does not: a module
missing from MODULEPATH, or a load hook that failed, read only
"eb-local: could not load EESSI/2026.06".

A build keeps a load's stderr in the workspace and prints it, indented,
under that line when the load fails. A load that works stays quiet.
@HaoZeke
HaoZeke merged commit 68d738d into main Nov 17, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant