-
Notifications
You must be signed in to change notification settings - Fork 464
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
use MessageRunMode struct #2779
base: ondemand-module-compile
Are you sure you want to change the base?
Conversation
@@ -1424,7 +1406,7 @@ func Create2ndNodeWithConfig( | |||
Require(t, err) | |||
wasmData, err := chainStack.OpenDatabaseWithExtraOptions("wasm", 0, 0, "wasm/", false, conf.PersistentConfigDefault.Pebble.ExtraOptions("wasm")) | |||
Require(t, err) | |||
chainDb := rawdb.WrapDatabaseWithWasm(chainData, wasmData, wasmCacheTag, execConfig.StylusTarget.WasmTargets()) | |||
chainDb := rawdb.WrapDatabaseWithWasm(chainData, wasmData) |
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.
as now the wasm tag is coupled with MessageRunContext
: are we ok with the all tests running with wasm long term cache enabled?
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.
The problem with tests using long-term cache is that multiple tests run in parallel, and in prallel with other tests initializing static vars etc. It's.. probably o.k. as long as the tests that do target long-term cache are not run in parallel with anything else.
Resolves NIT-2827
Pulls OffchainLabs/go-ethereum#373