Update documentation related to reference tests (#4681)

Now that reference tests are available in release assets and we are no
longer pushing tests to the consensus-spec-tests repo, we can remove
documentation mentioning the consensus-spec-tests repo.

Author: jtraglia

.gitignore

@@ -11,8 +11,6 @@ build/
 output/
 dist/
 
-consensus-spec-tests/
-
 .pytest_cache
 .mypy_cache
 
@@ -25,10 +23,7 @@ tests/core/pyspec/eth2spec/deneb/
 tests/core/pyspec/eth2spec/electra/
 tests/core/pyspec/eth2spec/fulu/
 tests/core/pyspec/eth2spec/gloas/
-tests/core/pyspec/eth2spec/eip6800/
-tests/core/pyspec/eth2spec/eip7441/
-tests/core/pyspec/eth2spec/eip7805/
-tests/core/pyspec/eth2spec/eip7928/
+tests/core/pyspec/eth2spec/eip*/
 
 # coverage reports
 .htmlcov

Makefile

@@ -225,7 +225,7 @@ TEST_REPORT_DIR = $(PYSPEC_DIR)/test-reports
 
 # Run pyspec tests.
 test: MAYBE_TEST := $(if $(k),-k=$(k))
-# Disable parallelism which running a specific test.
+# Disable parallelism when running a specific test.
 # Parallelism makes debugging difficult (print doesn't work).
 test: MAYBE_PARALLEL := $(if $(k),,-n auto)
 test: MAYBE_FORK := $(if $(fork),--fork=$(fork))

README.md

@@ -52,11 +52,9 @@ functionality can be found in the following repositories:
 
 ### Reference tests
 
-Reference tests built from the executable Python spec are available in the
-[Ethereum Proof-of-Stake Consensus Spec Tests](https://github.com/ethereum/consensus-spec-tests)
-repository. Compressed tarballs are available for each release
-[here](https://github.com/ethereum/consensus-spec-tests/releases). Nightly
-reference tests are available
+Reference tests built from the executable Python specifications are available in
+the release assets for each release in this repository. There are also *nightly*
+reference tests which are built from the latest version of the specifications
 [here](https://github.com/ethereum/consensus-specs/actions/workflows/generate_vectors.yml).
 
 ## Contributors

docs/docs/release.md

@@ -43,8 +43,8 @@ git tag <version>
 git push origin <version>
 ```
 
-Approximately 12 hours later, the releases for consensus-specs and
-consensus-spec-tests will be available on GitHub.
+Several hours later, the consensus-specs release will be automatically published
+on GitHub.
 
 ## Make an Announcement
 
@@ -62,6 +62,4 @@ Use the following template for your announcement:
 Consensus layer specs <version> -- <release-name> -- released!
 
 https://github.com/ethereum/consensus-specs/releases/tag/<version>
-
-Test vectors: https://github.com/ethereum/consensus-spec-tests/releases/tag/<version>
 ```

tests/README.md

@@ -447,13 +447,9 @@ ignore it)
 
 So far we've ran tests against the formal specifications. This is a way to check
 the specifications are what we expect, but it doesn't actually check the beacon
-chain clients. The way these tests get applied by clients is that every few
-weeks
-[new test specifications are released](https://github.com/ethereum/consensus-spec-tests/releases),
-in a format
-[documented here](https://github.com/ethereum/consensus-specs/tree/master/tests/formats).
-All the consensus layer clients implement test-runners that consume the test
-vectors in this standard format.
+chain clients. Consensus layer clients implement test-runners that
+consume/execute these reference tests to ensure they have implemented the
+specifications properly.
 
 ______________________________________________________________________