Find 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 logs

Before 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.

Watch this command run

Command transcript

This sanitized transcript shows the commands and output shape without exposing host details.

demo@lab:~$

$ cd /work/ci-artifacts && grep -RInE 'rerun|retry|flaky|passed on retry|failed attempt' artifacts logs

artifacts/test/pytest.log:6:tests/test_billing.py::test_invoice passed on retry after failed attempt 1
artifacts/test/pytest.log:7:1 failed, 2 passed, 1 rerun

artifacts/test/pytest.log

$ cd /work/ci-artifacts && sed -n '1,120p' artifacts/test/pytest.log

============================= test session starts =============================
tests/test_api.py::test_health PASSED
tests/test_api.py::test_create_user FAILED
Traceback (most recent call last):
  AssertionError: expected 201 got 500
tests/test_billing.py::test_invoice passed on retry after failed attempt 1
1 failed, 2 passed, 1 rerun

View commands shown

These are the commands shown in the sanitized transcript.