-
Notifications
You must be signed in to change notification settings - Fork 58
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
test: Add retries to increase reliability of test #1319
test: Add retries to increase reliability of test #1319
Conversation
This test needs to be skipped as it is causing P1 issues to appear. We need a formal plan for reproducing this issue.
🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use -- conventional-commit-lint bot |
This block of code is an after hook that will not work anymore now that the test is skipped because the test creates an instance and the after hook tries to delete it
system-test/read-rows.ts
Outdated
@@ -85,7 +85,7 @@ describe('Bigtable/Table', () => { | |||
const TABLE = INSTANCE.table('table'); | |||
|
|||
describe('close', () => { | |||
it('should fail when invoking readRows with closed client', async () => { | |||
it.skip('should fail when invoking readRows with closed client', async () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we add retries to this test instead? I would prefer not to skip it, unless it is consistently failing (in which case we should investigate an alternate solution there too).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. I added a change which will still allow the test to run and retry in the appropriate circumstances.
Add retry options to create table to ensure that there is enough time for the instance to get created in order to avoid flakey tests
This PR adds retries to the create table function in a test in order to reduce the risk of a flakey test in the case where the table cannot be created. This will solve some of the flakey test issues that we have been having.
Fixes #1292
Fixes #1291