-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flaky MySQL tests #1401
Labels
Comments
miparnisari
added
enhancement
New feature or request
help wanted
Extra attention is needed
labels
Feb 26, 2024
It appears this issue has been stale for at least 14 days 🗓️. If no action is taken the maintainer team may consider closing the issue. Please reach out if you need feedback or follow up actions from the maintainer team. |
4 tasks
00chorch
added a commit
to 00chorch/openfga
that referenced
this issue
May 21, 2024
Pushing remaining test files of pkg server. There's a known issue with some flaky tests (see openfga#1401) that might make github workflow "pull requests / tests" fail
00chorch
added a commit
to 00chorch/openfga
that referenced
this issue
May 24, 2024
Hypothesis is that will prevent race conditions in tests while running GRPC+healthz and MySQL container + ready to serve check. Must say can't reproduce locally so will use draft PR to test hypothesis. Related to issue openfga#1401
4 tasks
00chorch
added a commit
to 00chorch/openfga
that referenced
this issue
May 31, 2024
Pushing remaining test files of pkg server. There's a known issue with some flaky tests (see openfga#1401) that might make github workflow "pull requests / tests" fail
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist
Describe the problem you'd like to have solved
https://github.com/openfga/openfga/actions/runs/8052034021/job/21991285655
Describe the ideal solution
It looks like MySQL connections are dropped mid-way of test execution. We'd like to prevent this.
It could also be that we are not waiting long enough for MySQL connections to be healthy before proceeding with tests.
Alternatives and current workarounds
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: