Skip to content

test: align GraphQL health check retries with gRPC pattern#9752

Open
matthewmcneely wants to merge 1 commit into
mainfrom
matthewmcneely/fix-graphql-readiness-in-tests
Open

test: align GraphQL health check retries with gRPC pattern#9752
matthewmcneely wants to merge 1 commit into
mainfrom
matthewmcneely/fix-graphql-readiness-in-tests

Conversation

@matthewmcneely

Copy link
Copy Markdown
Contributor

Description

The waitUntilGraphqlHealthCheck function had a retry mismatch: it only retried login 5 times before failing, while waitUntilGrpcHealthCheck retries 10 times. This asymmetry caused flaky failures in TestNamespaceAwareRestoreOnMultipleGroups (and others) when the server wasn't fully ready within the 5-second window.

Changes:

  • Increase GraphQL login retry attempts from 5 to 10 (matching gRPC pattern)
  • Add warning logs for failed attempts after attempt 5 for visibility
  • Add logging to the DeleteUser health check loop for consistency

This gives the cluster more time to become ready without extending the total wait period beyond what gRPC health checks already do.

Checklist

  • The PR title follows the
    Conventional Commits syntax, leading
    with fix:, feat:, chore:, ci:, etc.
  • Code compiles correctly and linting (via trunk) passes locally

The waitUntilGraphqlHealthCheck function had a retry mismatch: it only
retried login 5 times before failing, while waitUntilGrpcHealthCheck
retries 10 times. This asymmetry caused flaky failures in
TestNamespaceAwareRestoreOnMultipleGroups when the server wasn't fully
ready within the 5-second window.

Changes:
- Increase GraphQL login retry attempts from 5 to 10 (matching gRPC pattern)
- Add warning logs for failed attempts after attempt 5 for visibility
- Add logging to the DeleteUser health check loop for consistency

This gives the cluster more time to become ready without extending the
total wait period beyond what gRPC health checks already do.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
@matthewmcneely matthewmcneely requested a review from a team as a code owner June 18, 2026 18:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant