Skip to content

Conversation

@olupton
Copy link
Collaborator

@olupton olupton commented Oct 29, 2024

  • Print the stdout/stderr of the first execution of the test case, which is supposed to fail, at INFO level along with a message encouraging the user to check that it is the correct failure.
  • Print the path to the DEBUG log file at INFO level and, therefore, to the console.
  • Expand the documentation.
  • Add --passing-container and --failing-container arguments, which allow the container-level search to be skipped and non-dated containers to be triaged.

- Print the stdout/stderr of the first execution of the test case, which
  is supposed to fail, at INFO level along with a message encouraging
  the user to check that it is the correct failure.
- Print the path to the DEBUG log file at INFO level and, therefore, to
  the console.
- Expand the documentation.
@olupton olupton force-pushed the olupton/triage-tweaks branch from 1e95fa5 to 3ad9cc2 Compare October 29, 2024 08:59
@olupton olupton requested a review from nouiz October 29, 2024 08:59
@olupton olupton force-pushed the olupton/triage-tweaks branch from 54a1772 to ee796e4 Compare October 29, 2024 10:05
These allow the container-level search to be skipped entirely, which
enables bisecting at the commit level on containers not from the
ghcr.io/nvidia/jax:CONTAINER-YYYY-MM-DD series.
@olupton olupton force-pushed the olupton/triage-tweaks branch from ee796e4 to 0fb73cc Compare October 29, 2024 10:11
@olupton olupton requested a review from nouiz October 29, 2024 15:34
@olupton olupton merged commit 0e4e245 into main Oct 29, 2024
56 of 57 checks passed
@olupton olupton deleted the olupton/triage-tweaks branch October 29, 2024 16:00
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.

3 participants