-
Notifications
You must be signed in to change notification settings - Fork 2.6k
try-runtime: Use configured wasm execution method #13694
Conversation
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.
Thanks, was just about to pull out the debugger before I saw that issue 😆
@kianenigma was there a good reason to prefer Interpreted here? |
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.
I think it (edit: the shared.wasm_method
) needs to be converted first
Good point! I didn't compile the crate with the |
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 hardcoded interpreted was indeed an oversight, thanks for fixing!
Now that it is using the wasm compiler, I can do the debugging , but unfortunately, it crashes (which is not the case when debugging the runtime when running the node (not try-runtime)) Here is the panic. I'm digging into it:
|
Oh I think it is because of the StripDrawf from the wasm-builder :/ I'll work on that |
bot merge |
Waiting for commit status. |
* try-runtime: Use configured wasm execution method * Fix compilation
* try-runtime: Use configured wasm execution method * Fix compilation (cherry picked from commit d0449fd)
* try-runtime: Use configured wasm execution method * Fix compilation
Closes: #13692