You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
jax-toolbox-triage: minor usability/doc improvements (#1125)
- 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.
will not immediately abort, because the tool is **expecting** the command to fail in
99
+
the early stages of the triage:
100
+
```
101
+
[INFO] 2024-10-29 01:49:01 Verbose output, including stdout/err of triage commands, will be written to /home/olupton/JAX-Toolbox/triage-2024-10-29-01-49-01/debug.log
102
+
[INFO] 2024-10-29 01:49:05 Checking end-of-range failure in 2024-10-27
103
+
[INFO] 2024-10-29 01:49:05 Ran test case in 2024-10-27 in 0.4s, pass=False
104
+
[INFO] 2024-10-29 01:49:05 stdout: OCI runtime exec failed: exec failed: unable to start container process: exec: "command-you-forgot-to-install": executable file not found in $PATH: unknown
105
+
106
+
[INFO] 2024-10-29 01:49:05 stderr:
107
+
[INFO] 2024-10-29 01:49:05 IMPORTANT: you should check that the test output above shows the *expected* failure of your test case in the 2024-10-27 container. It is very easy to accidentally provide a test case that fails for the wrong reason, which will not triage the correct issue!
108
+
[INFO] 2024-10-29 01:49:06 Starting coarse search with 2024-10-26 based on end_date=2024-10-27
109
+
[INFO] 2024-10-29 01:49:06 Ran test case in 2024-10-26 in 0.4s, pass=False
0 commit comments