fix: add dummy BtcAddress to benchmarks, enable xcm dep on standalone #635
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.
Signed-off-by: Gregory Hill [email protected]
We can remove
xcm-builder
from the standalone direct dependencies when we next update ORML.See: open-web3-stack/open-runtime-module-library@2a7183f
Aligns benchmarking structure with Substrate, tests now need the
runtime-benchmarks
feature to compile the benchmark test suites. This means thatBtcAddress:dummy()
andBtcPublicKey::dummy()
can be compiled conditionally as withEnsureOrigin::successful_origin()
.