-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix individual crate compilation issues & add script for running all tests #1444
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -26,8 +26,9 @@ use frame_support::{ | |
}; | ||
use frame_system::EnsureSigned; | ||
use orml_traits::{asset_registry::AssetMetadata, parameter_type_with_key}; | ||
#[cfg(feature = "runtime-benchmarks")] | ||
use pallet_pool_system::benchmarking::create_pool; | ||
use pallet_pool_system::{ | ||
benchmarking::create_pool, | ||
pool_types::{PoolChanges, PoolDetails, ScheduledUpdateDetails}, | ||
tranches::TrancheInput, | ||
}; | ||
|
@@ -222,6 +223,7 @@ impl< | |
_currency: <T as pallet_pool_registry::Config>::CurrencyId, | ||
_max_reserve: <T as pallet_pool_registry::Config>::Balance, | ||
) -> DispatchResult { | ||
#[cfg(feature = "runtime-benchmarks")] | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Are we sure the only code paths for this can be thru the runtime-benchmarks feature? I'm a little concerned about having the mocks behave differently between benches and tests... There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good point! It's true that it's used in tests even when Looking more deeply creating a pool seems to doesn't matter for the testing, but yes for the benchmarks because it adds a lot of weight to the call, |
||
create_pool::<T>(tranche_inputs.len() as u32, admin)?; | ||
Ok(()) | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This allows us to remove the stack limit increment in the CI scripts
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should remove this pallet all-together. We will not use it again.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good to know!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#1448