e2e: allow for both v0 and v1 mempool implementations (#6752)

This commit is contained in:
Callum Waters
2021-07-22 17:59:02 +02:00
committed by GitHub
parent 84c15857e4
commit 97a8f125e0
4 changed files with 16 additions and 0 deletions
+3
View File
@@ -110,6 +110,9 @@ type ManifestNode struct {
// Defaults to disabled.
FastSync string `toml:"fast_sync"`
// Mempool specifies which version of mempool to use. Either "v0" or "v1"
Mempool string `toml:"mempool_version"`
// StateSync enables state sync. The runner automatically configures trusted
// block hashes and RPC servers. At least one node in the network must have
// SnapshotInterval set to non-zero, and the state syncing node must have
+7
View File
@@ -80,6 +80,7 @@ type Node struct {
ProxyPort uint32
StartAt int64
FastSync string
Mempool string
StateSync bool
Database string
ABCIProtocol Protocol
@@ -168,6 +169,7 @@ func LoadTestnet(file string) (*Testnet, error) {
PrivvalProtocol: ProtocolFile,
StartAt: nodeManifest.StartAt,
FastSync: nodeManifest.FastSync,
Mempool: nodeManifest.Mempool,
StateSync: nodeManifest.StateSync,
PersistInterval: 1,
SnapshotInterval: nodeManifest.SnapshotInterval,
@@ -331,6 +333,11 @@ func (n Node) Validate(testnet Testnet) error {
default:
return fmt.Errorf("invalid fast sync setting %q", n.FastSync)
}
switch n.Mempool {
case "", "v0", "v1":
default:
return fmt.Errorf("invalid mempool version %q", n.Mempool)
}
switch n.QueueType {
case "", "priority", "wdrr", "fifo":
default: