-
Notifications
You must be signed in to change notification settings - Fork 146
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
Constantinople #267
Constantinople #267
Conversation
a04b51e
to
89b8d82
Compare
@daejunpark I need your help figuring out how to update the specifications so that they will be correct for constantinople. |
89b8d82
to
b7c87cd
Compare
d5dc178
to
452f5b7
Compare
a4b066d
to
ecbe1d6
Compare
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.
Looks pretty good, thanks for the clean commit history.
A couple minor changes, and then I want to review Rsstore
one more time on the cleaned up version.
ecbe1d6
to
7bbfeca
Compare
Jenkins: test mantis |
Jenkins: test this please |
Looks good, not sure why tests are failing. |
Jenkins: test this please |
Jenkins: test mantis |
Jenkins: test mantis |
1 similar comment
Jenkins: test mantis |
For context, the mantis build failed because of a bug in an updated package on rvwork2 and the standalone build failed because of an intermittent bug involving serialization that we may need to investigate further at some point, but I fixed the former and the latter doesn't have anything to do with this PR, so I just reran everything. It's gotten past the points where it crashed before, so I think it's going to succeed now. I will merge when the tests pass. |
EXTCODEHASH hasn't been fully tested yet because those tests haven't been merged upstream yet, but I will make a followup PR updating the tests submodule and fixing any bugs when it does. The rest have been fully tested and seem to pass, with the exception of two tests that expend more memory than we have on the machine, and two tests that seem to have incorrectly filled result information (which I have filed as a bug on the test repo)