op-e2e: Action testing L2 Engine Block building#3613
Conversation
|
|
This PR changes implementation code, but doesn't include a changeset. Did you forget to add one? |
7e69f0f to
fceff73
Compare
|
Hey @protolambda! This PR has merge conflicts. Please fix them before continuing review. |
c0c1a64 to
1b5b5a2
Compare
fceff73 to
ede3063
Compare
|
Hey @protolambda! This PR has merge conflicts. Please fix them before continuing review. |
1b5b5a2 to
ae485a3
Compare
ede3063 to
f7a274d
Compare
|
Hey @protolambda! This PR has merge conflicts. Please fix them before continuing review. |
ae485a3 to
f8e9469
Compare
f7a274d to
f917b00
Compare
|
Hey @protolambda! This PR has merge conflicts. Please fix them before continuing review. |
f8e9469 to
14c0229
Compare
|
Rebased to clean up the diff. The target branch is another PR (#3612) which is about ready. We should merge that first (can use mergify there). I'll then rebase this once more, and then mergify can pick this one up after I remove the label. |
Description
This adds block building functionality to the L2 engine actor in action testing.
This will help us write specific test cases where we include certain L2 transactions in specific order, while also running the driver and derivation pipeline (when L2 verifier actor is implemented).
The actual action tests will be less verbose. The testing here is verbose because it tests the implementation of the test utils. If that's tested, we can compose and repeat things.
Depends on #3612
Tests
Test that the L2 engine can build blocks, and that we can instrument the tx inclusion.
Metadata
Fix ENG-2850