challenger: Switch output_cannon to use the new contract type.#8379
challenger: Switch output_cannon to use the new contract type.#8379
Conversation
|
Note Reviews PausedUse the following commands to manage reviews:
WalkthroughThe changes involve a significant update to the game types and contract interactions within an application, likely related to blockchain or a similar distributed ledger technology. The error for conflicting trace types has been removed, indicating a change in the application's logic to allow simultaneous use of Changes
TipsChat with CodeRabbit Bot (
|
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## develop #8379 +/- ##
============================================
+ Coverage 40.09% 63.48% +23.39%
============================================
Files 164 16 -148
Lines 6175 1427 -4748
Branches 1002 0 -1002
============================================
- Hits 2476 906 -1570
+ Misses 3623 475 -3148
+ Partials 76 46 -30
Flags with carried forward coverage won't be shown. Click here to find out more. |
|
@coderabbitai pause Go home, you're drunk. |
|
This is an invalid command. Please refer to the list of valid keywords below. CodeRabbit Commands
|
|
@coderabbitai pause |
|
@ajsutton We are researching this and will suppress this noise. |
8137dee to
34f512a
Compare
34f512a to
72956da
Compare
refcell
left a comment
There was a problem hiding this comment.
Small comments, otherwise looks good to me
Description
Switches the
output_cannontrace type to use game type 253 and the newOutputBisectionGamecontract. Enhanced the e2e test for it a little to check it progresses into the cannon trace. The e2e is still a fairly basic sanity check - we'll review and update e2e tests further in https://github.com/ethereum-optimism/client-pod/issues/262Also we can now support
cannonandoutput_cannongames in the same instance.Tests
Updated e2e tests.
Metadata