Skip to content

Conversation

@Flamefire
Copy link
Contributor

This is disabled by default and hides the output of the module command.
That is usually just "noise" hiding the relevant part of the log.

With it disabled the output looks like:

== 2025-11-14 10:58:31,197 run.py:511 INFO Running shell command '/opt/lmod/lmod/libexec/lmod python load GCC/4.6.3' in /git/easybuild-framework
== 2025-11-14 10:58:31,261 run.py:625 INFO Shell command completed successfully: /opt/lmod/lmod/libexec/lmod python load GCC/4.6.3

I added small refactorings and fixes I've seen:

@boegel
Copy link
Member

boegel commented Dec 7, 2025

@Flamefire merge conflict to resolve...

@Flamefire
Copy link
Contributor Author

Looks like I identified and fixed the same bug in the tests in multiple occasions.

Rebased

This is disabled by default and hides the output of the module command.
That is usually just "noise" hiding the relevant part of the log.

With it disabled the output looks like:
> == 2025-11-14 10:58:31,197 run.py:511 INFO Running shell command '/opt/lmod/lmod/libexec/lmod python load GCC/4.6.3' in /git/easybuild-framework
> == 2025-11-14 10:58:31,261 run.py:625 INFO Shell command completed successfully: /opt/lmod/lmod/libexec/lmod python load GCC/4.6.3
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants