-
-
Notifications
You must be signed in to change notification settings - Fork 311
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
Add fork choice tests #1472
Comments
waiting for the tests to be merged to the official eth2.0-spec-tests npm package |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
unstale |
@tuyennhv have those been merged already? |
@dapplion it's not officially merged yet, still in some personal branches |
@tuyennhv Could you link those branches here to track them? |
Thanks! Are other clients using this tests? |
I'm not sure but guess they not yet to do since it hasn't become official yet |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 15 days if no further activity occurs. Thank you for your contributions. |
unstale |
@tuyennhv What's the current status? |
it's still not merged to the official spec tests |
so after ethereum/consensus-specs#2202 , still don't see the tests in |
fork choice tests should now be available in our downloaded tests with the update to v1.1.0-alpha.3 💯 |
Close after adding specs for Altair. Are those ready @tuyennhv ? |
@dapplion I think we do have forkchoice spec for |
altair and phase0 fork choice tests are currently merged 👍 |
Is your feature request related to a problem? Please describe.
A more rigorous fork choice test suite may uncover lurking bugs and provide us more confidence of the correctness of our code.
Describe the solution you'd like
Add the tests found here: ethereum/consensus-spec-tests#17
to the spec-tests package so they may be run along with other spec tests in CI
The text was updated successfully, but these errors were encountered: