Add retries to GraphQL test suite runner#8476
Merged
aljazerzen merged 2 commits intomasterfrom Mar 22, 2025
Merged
Conversation
Make our test suite runner for GraphQL retry queries on TransactionConflictError. We are getting serilization errors in some test runs. (Tests on PostgreSQL Versions, remote compiler)
aljazerzen
force-pushed
the
tests-graphql-retry
branch
from
28c6012 to
91ab7cf
Compare
fantix
approved these changes
Mar 21, 2025
aljazerzen
added a commit
that referenced
this pull request
Apr 5, 2025
Followup for #8476 I was catching the wrong exception (from server-side errors), while I should be catching the error from the bindings. Also, I used a nonexistant function, which would fail if it ever got to there.
aljazerzen
added a commit
that referenced
this pull request
Apr 5, 2025
Followup for #8476 I was catching the wrong exception (from server-side errors), while I should be catching the error from the bindings. Also, I used a nonexistant function, which would fail if it ever got to there.
aljazerzen
added a commit
that referenced
this pull request
Apr 7, 2025
Followup for #8476 I was catching the wrong exception (from server-side errors), while I should be catching the error from the bindings. Also, I used a nonexistent function, which would fail if it ever got to there.
msullivan
pushed a commit
that referenced
this pull request
Apr 8, 2025
Make our test suite runner for GraphQL retry queries on TransactionConflictError. We are getting serilization errors in some test runs. (Tests on PostgreSQL Versions, remote compiler)
msullivan
pushed a commit
that referenced
this pull request
Apr 8, 2025
Followup for #8476 I was catching the wrong exception (from server-side errors), while I should be catching the error from the bindings. Also, I used a nonexistent function, which would fail if it ever got to there.
msullivan
pushed a commit
that referenced
this pull request
Apr 8, 2025
Make our test suite runner for GraphQL retry queries on TransactionConflictError. We are getting serilization errors in some test runs. (Tests on PostgreSQL Versions, remote compiler)
msullivan
pushed a commit
that referenced
this pull request
Apr 8, 2025
Followup for #8476 I was catching the wrong exception (from server-side errors), while I should be catching the error from the bindings. Also, I used a nonexistent function, which would fail if it ever got to there.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Make our test suite runner for GraphQL retry queries on
TransactionConflictError.
We are getting serilization errors in some test runs.
(Tests on PostgreSQL Versions, remote compiler)