Repository navigation
test(bigtable): fix flaky backup system tests #9717
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
Closed
danieljbruce
wants to merge
7
commits into
googleapis:main
from
danieljbruce:fix/bigtable-flaky-backup-system-tests
Closed
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
08362cf
test(bigtable): fix flaky backup system tests
danieljbruce d57cbd1
[Style Maintenance] align changes with CONTRIBUTING.md and gts coding…
danieljbruce c6ddbd2
[Independent review follow-ups] address independent Gemini review com…
danieljbruce 1cf29f8
[Independent review follow-ups] address independent Gemini review com…
danieljbruce c058424
[Address CI errors] check restored table existence on DIFF_INSTANCE i…
danieljbruce 04d2692
[Address CI errors] fix circular require in mutateInternal and client…
danieljbruce fd56037
[Address CI errors] restore waitForReplication fake timer spies via s…
danieljbruce File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
Modifying the timestamps for our metrics does not seem like something we should do.
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.
Looking at this again, I can see we already made changes in danieljbruce@1ea27c9 to artificially change the end and start nanos and it seems the problem with that change is that it is setting the endNanos to the startNanos which is still causing errors. In other words, setting endNanos to startNanos didn't really solve the flakey tests.
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.
danieljbruce@1ea27c9#diff-39c2f3c691ce7c9e2f54ab8c9020dff4aef632d80a11aa13fe19074c889aaad5R54-R56 is the link to the exact changes from the other commit.
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.
If it is possible, we should really try to revert the change from the previous PR and fix the tests only with test changes if possible.