cerc-io/lighthouse
15
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity
1d4f90e2eb
lighthouse/testing/ef_tests
History
Michael Sproul 1d4f90e2eb Bump tests to v1.1.0-beta.2 (#2481) 
## Proposed Changes

Bump spec tests to v1.1.0-beta.2, for conformance with the latest spec release: https://github.com/ethereum/eth2.0-specs/releases/tag/v1.1.0-beta.2

## Additional Info

We already happen to be compatible with the latest spec change that requires sync contributions to have at least one bit set. I'm gonna call it foresight on @realbigsean's part 😎

6e3ca48cb9/beacon_node/beacon_chain/src/sync_committee_verification.rs (L285-L288)
2021-07-29 02:16:54 +00:00
..
src Use bulk verification for sync_aggregate signature (#2415) 2021-07-28 05:40:21 +00:00
tests [Altair] Sync committee pools (#2321) 2021-07-15 00:52:02 +00:00
.gitignore Altair consensus changes and refactors (#2279) 2021-07-09 06:15:32 +00:00
Cargo.toml Altair consensus changes and refactors (#2279) 2021-07-09 06:15:32 +00:00
check_all_files_accessed.py [Altair] Sync committee pools (#2321) 2021-07-15 00:52:02 +00:00
Makefile Bump tests to v1.1.0-beta.2 (#2481) 2021-07-29 02:16:54 +00:00
README.md Directory Restructure (#1163) 2020-05-18 21:24:23 +10:00

README.md

Ethereum 2.0 Specification Tests

This crate parses and executes the test vectors at ethereum/eth2.0-spec-tests.

Functionality is achieved only via the $ cargo test --features ef_tests command.

Running the Tests

Because the test vectors are very large, we do not download or run them by default. To download them, run (in this directory):

$ make

Note: this may download hundreds of MB of compressed archives from the ethereum/eth2.0-spec-tests, which may expand into several GB of files.

If successful, you should now have the extracted tests in ./eth2.0-spec-tests.

Run them with:

$ cargo test --features ef_tests

The tests won't run without the ef_tests feature enabled (this is to ensure that a top-level cargo test --all won't fail on missing files).

Saving Space

When you download the tests, the downloaded archives will be kept in addition to the extracted files. You have several options for saving space:

  1. Delete the archives (make clean-archives), and keep the extracted files. Suitable for everyday use, just don't re-run make or it will redownload the archives.
  2. Delete the extracted files (make clean-test-files), and keep the archives. Suitable for CI, or temporarily saving space. If you re-run make it will extract the archives rather than redownloading them.
  3. Delete everything (make clean). Good for updating to a new version, or if you no longer wish to run the EF tests.