Skip to content

docs: open with what --tmp-logdir and eb --last-log already keep - #39

Merged
HaoZeke merged 5 commits into
mainfrom
docs/what-eb-already-keeps
Nov 18, 2026
Merged

HaoZeke merged 5 commits into
mainfrom
docs/what-eb-already-keeps

Conversation

@HaoZeke

@HaoZeke HaoZeke commented Nov 18, 2026

Copy link
Copy Markdown
Collaborator

The old opening said the EasyBuild log is lost with the job, then the example set a durable --tmp-logdir, which keeps it. The README now says the log alone needs no tool (EESSI's install script copies it), and that this tool keeps the failing command's run-shell-cmd-output files and a failed meson test log, which EasyBuild 5 leaves in its tmpdir. Also syncs the stackhands table.

The EasyBuild log alone needs no tool; EESSI's install script copies it.
The tool's part is the failing command's run-shell-cmd output and a
failed meson test log, which go with the node-local disk.
…lost

EasyBuild 5 logs a failed command's full output (tools/run.py). What
goes with the node-local disk is a failed meson test log; the tool also
keeps the run-shell-cmd output as plain files and closes them to others.
@HaoZeke
HaoZeke merged commit 4e0a760 into main Nov 18, 2026
8 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