fix(verify): -rs replaced pytest's -rfE and stopped listing failures

[stranske]

Follow-up to #3, found by pointing the new instrument at a real red.

#3 added "print EVERY pytest failure, not the last 12 lines" — and in the same breath passed -rs to get skip reasons. pytest's default is -rfE, and passing -r replaces that set rather than adding to it. So FAILED/ERROR lines left the short summary, and run_pytest — which harvests failures from exactly those lines — found none.

Observed on a tree with one genuine failure:

    - 1 pytest failure(s)/error(s)
    pytest failures (0):

An instrument reporting less, introduced by the change that existed to make it report more. Same defect class this repo is named for, shipped inside its own countermeasure.

-rfEs restores failures and errors alongside skip reasons.

The selftest now asserts on the flag itself rather than on behaviour, because the symptom only appears on a red run: a green suite has no FAILED lines to lose, so no amount of local verification would have caught it. Deliberate break → revert: restoring -rs fails with -rs omits 'f': failures would not be listed; reverted byte-identical.

Verified: 330 passed / 0 failed / 0 of 24 skipped / 81 of 81 selftests / 5 of 5 gates.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your current included review allowance is based on your included PR review attempts over the past 7 days.

Next review available in: 24 minutes

Limit details: You’ve used the included review currently available. Your 64 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 2ef323e7-a02d-4a11-a43f-5176e95413f4

📥 Commits

Reviewing files that changed from the base of the PR and between 10b5ccf and 37699f1.

📒 Files selected for processing (1)

• verify.py

---

_{Comment @coderabbitai help to get the list of available commands.}