Skip to content

spar-integration: retry transient 5xx on client delete in re-auth test#5314

Draft
blackheaven wants to merge 2 commits into
developfrom
gdifolco/fix-flaky-tests-spar-brig
Draft

spar-integration: retry transient 5xx on client delete in re-auth test#5314
blackheaven wants to merge 2 commits into
developfrom
gdifolco/fix-flaky-tests-spar-brig

Conversation

@blackheaven

Copy link
Copy Markdown
Contributor

Checklist

  • Add a new entry in an appropriate subdirectory of changelog.d
  • Read and follow the PR guidelines

The "password user that was upgraded to SCIM has to provide password" test
hit an intermittent brig 500 on DELETE /clients/:cid (an opaque transient,
likely a backend read under load).  Reuse the existing retryNUntil helper
(Control.Retry) to retry the idempotent delete on transient 5xx, then assert
the expected status -- so a transient 500 no longer fails the test, while
genuine failures still surface.
@blackheaven blackheaven requested a review from a team as a code owner July 3, 2026 11:20
@zebot zebot added the ok-to-test Approved for running tests in CI, overrides not-ok-to-test if both labels exist label Jul 3, 2026
payload =
RequestBodyLBS . encode . object . maybeToList $
fmap ("password" .=) pw
transientStatuses = [500, 502, 503, 504]

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we shouldn't retry here, but find out why brig is failing with 5xx and fix that.

@blackheaven blackheaven marked this pull request as draft July 7, 2026 17:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ok-to-test Approved for running tests in CI, overrides not-ok-to-test if both labels exist

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants