HBASE-29544: Assertion errors in BackupAndRestoreThread are not causing IntegrationTestBackupRestore to fail #7249
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.
Summary
https://issues.apache.org/jira/browse/HBASE-29544
This is a cherry-pick from PR #7243.
IntegrationTestBackupRestoreruns the backup and restore processes in a separate thread (or threads). PR #7203 (HBASE-29503) fixed an issue where the test would still pass even if an exception occurred in one of the threads. However, that fix only handles exceptions. It does not handle other throwables, such asAssertionError. This pull request extends the functionality implemented in PR #7203 to handle all throwables instead of just exceptions.Manual Testing of Errors
Exceptions
I added a
RuntimeExceptiontoBackupAndRestoreThread.run()to test exception handling:Error message (note the
Caused by...):AssertionErrors
I forced an
AssertionErrorby modifying theassertEquals()inrestoreVerifyTable():Error message (note the
Caused by...):