fix: set kestrel block time to 1 second #896
Closed
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.
The kestrel block time was set to 6s on the level of the aura config, which apparently was overridden by the
MinimumPeriodof the timestamp pallets though.Now the aura config takes precedence as it looks like, and block time (even when using the --dev flag) is 6 seconds.
This means that tests take much longer and sometimes time out.
Reducing the aura config to 1s helps. Not sure we have any other contexts in which this runtime was used, and where we maybe expected a 6s block time?
Metadata Diff to Develop Branch
Peregrine Diff
None.
Spiritnet Diff
None
Checklist:
array[3]useget(3), ...)