From b69c2f5ba1c54760e24d3d18cc8406c9d531ba81 Mon Sep 17 00:00:00 2001 From: Pawan Dhananjay Date: Wed, 29 Oct 2025 00:00:25 -0700 Subject: [PATCH] Run CI tests only recent forks (#8271) Partially addresses #8248 Run the beacon chain, http and network tests only for recent forks instead of everything from phase 0. Also added gloas also to the recent forks list. I thought that would be a good way to know if changes in the current fork affect future forks. Not completely sure if we should run for future forks, but added it so that we can discuss here. Co-Authored-By: Pawan Dhananjay Co-Authored-By: Jimmy Chen --- Makefile | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-) diff --git a/Makefile b/Makefile index b9f93942f6..2edc9f8632 100644 --- a/Makefile +++ b/Makefile @@ -30,12 +30,8 @@ TEST_FEATURES ?= # Cargo profile for regular builds. PROFILE ?= release -# List of all hard forks. This list is used to set env variables for several tests so that -# they run for different forks. -FORKS=phase0 altair bellatrix capella deneb electra fulu gloas - # List of all recent hard forks. This list is used to set env variables for http_api tests -RECENT_FORKS=electra fulu +RECENT_FORKS=electra fulu gloas # Extra flags for Cargo CARGO_INSTALL_EXTRA_FLAGS?= @@ -170,8 +166,8 @@ run-ef-tests: cargo nextest run --release -p ef_tests --features "ef_tests,$(EF_TEST_FEATURES),fake_crypto" ./$(EF_TESTS)/check_all_files_accessed.py $(EF_TESTS)/.accessed_file_log.txt $(EF_TESTS)/consensus-spec-tests -# Run the tests in the `beacon_chain` crate for all known forks. -test-beacon-chain: $(patsubst %,test-beacon-chain-%,$(FORKS)) +# Run the tests in the `beacon_chain` crate for recent forks. +test-beacon-chain: $(patsubst %,test-beacon-chain-%,$(RECENT_FORKS)) test-beacon-chain-%: env FORK_NAME=$* cargo nextest run --release --features "fork_from_env,slasher/lmdb,$(TEST_FEATURES)" -p beacon_chain @@ -184,15 +180,15 @@ test-http-api-%: # Run the tests in the `operation_pool` crate for all known forks. -test-op-pool: $(patsubst %,test-op-pool-%,$(FORKS)) +test-op-pool: $(patsubst %,test-op-pool-%,$(RECENT_FORKS)) test-op-pool-%: env FORK_NAME=$* cargo nextest run --release \ --features "beacon_chain/fork_from_env,$(TEST_FEATURES)"\ -p operation_pool -# Run the tests in the `network` crate for all known forks. -test-network: $(patsubst %,test-network-%,$(FORKS)) +# Run the tests in the `network` crate for recent forks. +test-network: $(patsubst %,test-network-%,$(RECENT_FORKS)) test-network-%: env FORK_NAME=$* cargo nextest run --release \