-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
test: ovm context #522
test: ovm context #522
Conversation
🦋 Changeset detectedLatest commit: a02034d The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
// TODO: this is a bug and needs to be fixed | ||
//expect(info.ethContext.blockNumber).to.deep.equal(blockNumber.toNumber()) |
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.
Is this bug documented in an issue?
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.
Documented here: #524
* integration tests: ovm context * integration tests: add changeset
Description
Re-adds tests that were left behind as part of the monorepo migration.
These tests specifically cover
NUMBER
opcode which was fixed in ethereum-optimism/go-ethereum#280 as well as the returned values fromrollup_getInfo
. This RPC endpoint returns the current rollup context as well as the OVM context. There is a bug that requires an assertion to be fixed, this PR could either be rebased on top of a fix or merged with a ticket to fix the problem in the future. If #477 doesn't fix the bug then it should be easy to do so after #477