-
Notifications
You must be signed in to change notification settings - Fork 180
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
Ensure the same runtime config is used #3768
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3768 +/- ##
=======================================
Coverage 55.36% 55.37%
=======================================
Files 768 768
Lines 70191 70194 +3
=======================================
+ Hits 38861 38868 +7
+ Misses 28148 28145 -3
+ Partials 3182 3181 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
FVM Benchstat comparisonThis branch with compared with the base branch onflow:master commit 8ff3253 The command Collapsed results for better readability
|
bors merge |
4126: Add an extra parameter for runtime config in `NewCustomReusableCadenceRuntimePool` constructor r=janezpodhostnik a=m-Peter Prior to this change, an empty `runtime.Config{}` was used and there was no way to set a custom config. A similar improvement was done in this PR #3768 Co-authored-by: Ardit Marku <markoupetr@gmail.com>
Various places create Cadence
runtime.Config
s, e.g.NewReusableCadenceRuntime
creates an empty one, even when the runtime was potentially created using a different one (e.g. byReusableCadenceRuntimePool.newCustomRuntime
).Propagate the runtime configuration, so it is consistently the same everywhere in
ReusableCadenceRuntimePool
andReusableCadenceRuntime
.