Skip to content

Conversation

@dcapwell
Copy link
Contributor

No description provided.

@dcapwell
Copy link
Contributor Author

test this please

"""
self.fixture_dtest_setup.ignore_log_patterns = [
'Nothing to repair for'
]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you provide a bit of info when we see this case and why it is ok to ignore it, please?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the log we generate when we skip repair due to no data (or no tables, etc.); this test does not write data, so skipping repair is the expected behavior

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added docs explaining why; these tests do repairs for a token range, but doesn't put in effort to make sure that there are partitions in that range, so the repair aborts.

The test is checking logging, which is done after we parse arguments and print them... if repair doesn't happen these tests don't really care.

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.

4 participants