lighthouse/tests/ef_tests
Michael Sproul 26bdc2927b
Update to spec v0.11 (#959)
* Update process_final_updates() hysteresis computation

* Update core to v0.11.1

* Bump tags to v0.11.1

* Update docs and deposit contract

* Add compute_fork_digest

* Address review comments

Co-authored-by: Herman Alonso Junge <alonso.junge@gmail.com>
2020-04-01 22:03:03 +11:00
..
src Update to spec v0.11 (#959) 2020-04-01 22:03:03 +11:00
tests Update to spec v0.11 (#959) 2020-04-01 22:03:03 +11:00
.gitignore Replace EF tests submodule with a makefile 2019-09-08 04:19:54 +10:00
Cargo.toml Implement tree hash caching (#584) 2019-11-05 15:46:52 +11:00
Makefile Update to spec v0.11 (#959) 2020-04-01 22:03:03 +11:00
README.md Run EF tests on GitLab (#562) 2019-10-22 12:35:35 +09:00

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.