thread local chain type vs global chain type (#3327)
* Introduce GLOBAL_CHAIN_TYPE and make CHAIN_TYPE thread_local. This makes testing more explicit and significantly more robust. * set_local_chain_type() in tests * cleanup - weird * get pool tests working with explicit local chain_type config * core tests working with explicit local chain_type * p2p tests working with explicit local chain_type * store tests working * cleanup, feedback
This commit is contained in:
+2
-2
@@ -17,12 +17,12 @@
|
||||
|
||||
use chrono::prelude::{DateTime, Utc};
|
||||
|
||||
use self::core::consensus;
|
||||
use self::core::core::block;
|
||||
use self::core::core::committed;
|
||||
use self::core::core::hash::Hash;
|
||||
use self::core::core::transaction::{self, Transaction};
|
||||
use self::core::core::{BlockHeader, BlockSums};
|
||||
use self::core::{consensus, global};
|
||||
use failure::Fail;
|
||||
use grin_core as core;
|
||||
use grin_keychain as keychain;
|
||||
@@ -144,7 +144,7 @@ fn default_max_stempool_size() -> usize {
|
||||
50_000
|
||||
}
|
||||
fn default_mineable_max_weight() -> usize {
|
||||
global::max_block_weight()
|
||||
consensus::MAX_BLOCK_WEIGHT
|
||||
}
|
||||
|
||||
/// Represents a single entry in the pool.
|
||||
|
||||
Reference in New Issue
Block a user