Refactor assert in scan_snapshot_stores() #34162
Merged
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.
Problem
In #34118 we are upgrading Rust. The way Rust nightly displays panic messages has changed. This can cause
should_panic
tests to fail if they specify anexpected
message. We're seeing that in theaccounts_db::tests::test_accountsdb_scan_snapshot_stores_illegal_range_xxx
tests.Here's what the error looks like:
Here's the build log: https://buildkite.com/solana-labs/solana/builds/104653#018be0ac-278d-4621-9fd4-629956045713
Since the newlines seem to be an issue, we can split up the assert so that the panic message doesn't have any newlines. There will be no functional difference.
Summary of Changes
Split the assert.