Hosting Operations
Read-only, can be slowFind Tests That Passed After Rerun
The pipeline passed after retry, but you need to identify tests that failed earlier in the same job.
Command
grep -RInE 'rerun|retry|flaky|passed on retry|failed attempt' artifacts logsBefore you run this
System impact: Read-only. Can create load on large logs, directories, filesystems, or process tables.
When not to use it: Do not label a test flaky from one run alone; compare with history when possible.
Expected output
Lines mentioning reruns, retries, flaky markers, or failed attempts.
System impact
Read-only, can be slow. Nothing changes. Retry and flaky-test markers are printed.
Scope this to the smallest useful path or service on busy systems.
Recovery / rollback: no state is changed.
When to use it
Use after a successful retry or when CI instability is suspected.
When not to use it
Do not label a test flaky from one run alone; compare with history when possible.
next steps
Related commands
Scan Every CI Log for Error Lines
One grep pass can turn a log pile into a failure list.
grep -RInE 'error|failed|failure|exception|traceback' artifacts logs | head -50
Find Coverage Regression Lines
Coverage failures usually say the threshold out loud.
grep -RInE 'coverage|threshold|minimum|below' artifacts logs
Detect Secret Leak Markers in Artifacts
Artifacts are public more often than you think.
grep -RInE 'AWS_ACCESS_KEY|SECRET|TOKEN|PRIVATE KEY|PASSWORD' artifacts logs | head -50
Tail the Failing CI Lines
Skip the full CI log and jump straight to lines that usually explain the failure.
grep -RInE 'error|failed|exception|traceback|fatal' logs/ | tail -50
List Failed Tests from JUnit XML
The XML report already knows which tests failed.
grep -RIn '<failure\|<error' artifacts/test/*.xml
Study mapping
Use this as independent command practice: read the notes, predict the output, then compare it with the example before using a real shell.
Independent study support only. No affiliation, endorsement, exam dumps, or real exam questions.