Conversation
|
I left a comment on ethereum/execution-specs#1109 but it looks like merging into edit: maybe the |
@fselmo thanks for this! The background is:
I'll need to double-check, but I think we only need to move EEST from I'll have go at moving EEST to ethereum-rlp. |
|
Thanks @danceratopz for the background. I knew there was an update needed somewhere, was just unsure which branch made sense here but that clears it up 👍🏼 |
|
once we have access to evm tracing, can we add expect verification type for a certain type of exception during vm exec? |
I think that's a different issue. Tracing is just to aid on debugging. |
- Always send ``trace``, and if it's set to ``True``, send a known temp ``output-basedir`` to the EELS server / daemon. The server will include the full trace, using the ``output-basedir`` to store the trace ``.jsonl`` files to be collected as expected by EEST.
4c096cb to
f333cae
Compare
marioevz
left a comment
There was a problem hiding this comment.
Locally tested and works great.
I've added a commit to bump the commit to the one where EELS merged the functionality on their side.
Thanks so much for this, it's such a nice feature to have when debugging :)
|
@marioevz sounds good. Thanks for picking up the commit hash update 👍🏼 |
* Turn on evm tracing for EELS: - Always send ``trace``, and if it's set to ``True``, send a known temp ``output-basedir`` to the EELS server / daemon. The server will include the full trace, using the ``output-basedir`` to store the trace ``.jsonl`` files to be collected as expected by EEST. * chore(tox,ci,uv.lock): Update EELS reference commit to support tracing --------- Co-authored-by: Mario Vega <marioevz@gmail.com>
🗒️ Description
trace, and if it's set toTrue, send a known temp directoryoutput-basedirto the EELS server / daemon. The server will include the full trace, using theoutput-basedirto store the trace.jsonlfiles to be collected as expected by EEST.🔗 Related Issues
ethereum/execution-specs#1109
✅ Checklist
mkdocs servelocally and verified the auto-generated docs for new tests in the Test Case Reference are correctly formatted.