-
Notifications
You must be signed in to change notification settings - Fork 998
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
phase restricted generators #1165
Conversation
Getting an error when writing state to yaml file. Looks like it's having trouble writing an embedded object within state.
Gotta switch gears for evening. This the last thing we need to do before v0.7.0 release |
3a0b8e0
to
46d8422
Compare
sorry, fixed typo 😅 |
Ok, ran all generators, and it runs within ~16 minutes, and produces 400MB worth of yaml test vectors. However, I had excluded the mainnet attestation operation tests, as there are single test cases in there, that take over 12 minutes to run with the mainnet configuration. (tried, profiled, created call-graphs, compared ssz-implementations, but to no avail: the tests are just running insane amounts of hash-tree-root calls (incl recursive, in the tens of millions of calls....) # create_suite('attestation', 'mainnet', lambda: generate_from_tests(test_process_attestation, 'phase0')), Instead, we can release without them, and re-enable when we have SSZ caching, instead of just a small zero-hash optimization. Or someone has to invest some serious time in changing those tests, while still keeping them compatible with the original test intentions. |
phase
explicitly intogenerate_from_tests
'phase0'