Repository navigation
feat: filter failed runs by recipe or date - #36
Merged
Merged
Conversation
Add `eb-keep-logs failures` to list failed builds across `YYYYMMDD_HHMMSS` runs under `--root`, filtered by `--package`, `--target`, `--since` and `--until`, with JSON schema output and a text table showing each failed EasyBuild step and duration. Also add opt-in `--package`, `--since` and `--until` filters to `why`, and `--since`, `--until` and `--failed` filters to `history`. Existing default command outputs, stderr and exit statuses remain unchanged.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I added
eb-keep-logs failuresand opt-in recipe and date filters onwhyandhistoryso site operators can filter failed EasyBuild runs without grepping full log trees.whypreviously inspected only one run at a time with no package filter or date bounds, andhistoryrequired a package argument and scanned everyYYYYMMDD_HHMMSSdirectory regardless of date or outcome. When a pipeline run fails across multiple targets or across a multi-week log tree, isolating failures for a specific recipe or date window required ad-hoc scripting.The new
failuressubcommand scansYYYYMMDD_HHMMSSruns under--rootoldest first, filters runs by--sinceand--until(YYYY-MM-DD,YYYYMMDD, orYYYYMMDD_HHMMSS), filters builds by--package(matching the existingPACKAGEprefix andNAME/VERSIONconventions) and--target, and reads each failed build's kept session log or stdout log to report its failed EasyBuild step, duration, and log path. With--json, it emits one schema-validated JSON line (schema_version1).whygains opt-in--package,--since, and--until(narrowing--latestselection by date and filtering builds within the run), andhistorygains opt-in--since,--until, and--failed.All additions are opt-in and implemented in the Zig build only (
COMPAT.mdand the reference shell script record the deliberate difference). Existing default stdout, stderr and exit statuses stay the same as onmain, verified bytests/test_output_stability.sh,tests/differential.sh,tests/test_failures.sh, andtests/test_json_schemas.sh. I also updated the Org CLI and JSON schema references, the how-to guide for diagnosing failed builds,README.md, and added a changelog fragment.