Fallback to default flags if rxcache initialization fails #3087
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.
Description
Fallback to default flags if randomx cache allocation fails.
This should allow platforms with limited resources to validate blocks.
Similar to how xmrig falls back:
https://github.com/xmrig/xmrig/blob/02b2b87bb685ab83b132267aa3c2de0766f16b8b/src/crypto/rx/RxCache.cpp#L88
Adds some basic unit tests
Motivation and Context
A user reported "Unable to allocate randomx cache". Since this is used for block validation (not mining), falling
back to the slowest but lightest randomx profile is acceptable.
How Has This Been Tested?
Basic unit tests. Tested on weatherwax base node
Checklist:
development
branch.