← Back to rankings

Synthetic test history

payment_retry_settles

tests.payments::PaymentRetry payments.yml · test (node-22, postgres-17) · ubuntu
Observed nonpass rate · reversal cohorts16.7%
95% Wilson interval · reversal cohorts12.0–22.7%
Conflict groups14
Estimated CI impact / 30d184 min

The evidence

Same-input reversals

Demo mode · synthetic data

Representative rows from the synthetic history; the summary metric includes all 14 conflict groups.

Representative same-input run history for payment_retry_settles
CommitAttemptOutcomeJob durationObserved
a18f03c 1 fail 7m 42s 2h ago
a18f03c 2 pass 7m 31s 2h ago
84c9f51 1 pass 7m 18s 1d ago
84c9f51 2 fail 7m 55s 1d ago
3d447ce 1 fail 8m 01s 3d ago
3d447ce 2 pass 7m 36s 3d ago

Rows are paired because both the commit SHA and execution fingerprint match. Different SHAs or runtime matrices are never compared.

Before you connect

Public repositories only

Quarantine uses GitHub OAuth to identify you and list public repositories. This prototype requests no private-repository or write scope.

Retention and revocation: signing out invalidates active Quarantine sessions. Revoking the OAuth grant in GitHub invalidates the credential but does not delete its encrypted database record. Only operator database cleanup deletes that record; this prototype has no self-service account deletion. Use the synthetic demo if you do not want to connect an account.

For private repositories, the safer production path is a GitHub App with repository-level Actions: read access.