Skip to content
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

storage: revert a test to starting with a single range #33486

Conversation

andreimatei
Copy link
Contributor

It appears to be a bit flaky otherwise.

Release note: None

It appears to be a bit flaky otherwise.

Release note: None
@andreimatei andreimatei requested review from tbg and a team January 4, 2019 00:20
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@tbg
Copy link
Member

tbg commented Jan 7, 2019

Do you know why it's flaky?

@tbg
Copy link
Member

tbg commented Jan 7, 2019

this is the NPE, right? Please add what we've found to the commit and, even better, to the line that makes the test use a single range.

tbg added a commit to tbg/cockroach that referenced this pull request Jan 9, 2019
This took me longer to track down than I'm comfortable admitting. The
test wasn't properly checking for full upreplication because it was only
looking at the first range. It still is, but that's now all the ranges
-- it's finicky to upgrade the check.

Fixes cockroachdb#33497.
Closes cockroachdb#33486.

Release note: None
craig bot pushed a commit that referenced this pull request Jan 9, 2019
33584: storage: deflake TestStoreRangeRemoveDead r=andreimatei a=tbg

This took me longer to track down than I'm comfortable admitting. The
test wasn't properly checking for full upreplication because it was only
looking at the first range. It still is, but that's now all the ranges
-- it's finicky to upgrade the check.

Fixes #33497.
Closes #33486.

Release note: None

Co-authored-by: Tobias Schottdorf <[email protected]>
@craig craig bot closed this in #33584 Jan 9, 2019
@andreimatei andreimatei deleted the fix-TestStoreRangeRemoveDead branch January 12, 2019 00:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants