2023-12-04 23:49:50 +00:00
|
|
|
TESTS_TAG := v5.3.0
|
2020-10-02 01:42:27 +00:00
|
|
|
GENERATE_DIR := generated-tests
|
|
|
|
|
OUTPUT_DIR := interchange-tests
|
|
|
|
|
TARBALL := $(OUTPUT_DIR)-$(TESTS_TAG).tar.gz
|
2022-01-07 05:32:34 +00:00
|
|
|
ARCHIVE_URL := https://github.com/eth-clients/slashing-protection-interchange-tests/tarball/$(TESTS_TAG)
|
2020-10-02 01:42:27 +00:00
|
|
|
|
2021-05-19 23:05:16 +00:00
|
|
|
ifeq ($(OS),Windows_NT)
|
|
|
|
|
ifeq (, $(shell where rm))
|
Ultra Fast Super Slick CI (#4755)
Attempting to improve our CI speeds as its recently been a pain point.
Major changes:
- Use a github action to pull stable/nightly rust rather than building it each run
- Shift test suite to `nexttest` https://github.com/nextest-rs/nextest for CI
UPDATE:
So I've iterated on some changes, and although I think its still not optimal I think this is a good base to start from. Some extra things in this PR:
- Shifted where we pull rust from. We're now using this thing: https://github.com/moonrepo/setup-rust . It's got some interesting cache's built in, but was not seeing the gains that Jimmy managed to get. In either case tho, it can pull rust, cargofmt, clippy, cargo nexttest all in < 5s. So I think it's worthwhile.
- I've grouped a few of the check-like tests into a single test called `code-test`. Although we were using github runners in parallel which may be faster, it just seems wasteful. There were like 4-5 tests, where we would pull lighthouse, compile it, then run an action, like clippy, cargo-audit or fmt. I've grouped these into a single action, so we only compile lighthouse once, then in each step we run the checks. This avoids compiling lighthouse like 5 times.
- Ive made doppelganger tests run on our local machines to avoid pulling foundry, building and making lcli which are all now baked into the images.
- We have sccache and do not incremental compile lighthouse
Misc bonus things:
- Cargo update
- Fix web3 signer openssl keys which is required after a cargo update
- Use mock_instant in an LRU cache test to avoid non-deterministic test
- Remove race condition in building web3signer tests
There's still some things we could improve on. Such as downloading the EF tests every run and the web3-signer binary, but I've left these to be out of scope of this PR. I think the above are meaningful improvements.
Co-authored-by: Paul Hauner <paul@paulhauner.com>
Co-authored-by: realbigsean <seananderson33@gmail.com>
Co-authored-by: antondlr <anton@delaruelle.net>
2023-10-03 06:33:15 +00:00
|
|
|
rmfile = if exist $(1) (del /F /Q $(1))
|
|
|
|
|
rmdir = if exist $(1) (rmdir /Q /S $(1))
|
|
|
|
|
makedir = if not exist $(1) (mkdir $(1))
|
2021-05-19 23:05:16 +00:00
|
|
|
else
|
Ultra Fast Super Slick CI (#4755)
Attempting to improve our CI speeds as its recently been a pain point.
Major changes:
- Use a github action to pull stable/nightly rust rather than building it each run
- Shift test suite to `nexttest` https://github.com/nextest-rs/nextest for CI
UPDATE:
So I've iterated on some changes, and although I think its still not optimal I think this is a good base to start from. Some extra things in this PR:
- Shifted where we pull rust from. We're now using this thing: https://github.com/moonrepo/setup-rust . It's got some interesting cache's built in, but was not seeing the gains that Jimmy managed to get. In either case tho, it can pull rust, cargofmt, clippy, cargo nexttest all in < 5s. So I think it's worthwhile.
- I've grouped a few of the check-like tests into a single test called `code-test`. Although we were using github runners in parallel which may be faster, it just seems wasteful. There were like 4-5 tests, where we would pull lighthouse, compile it, then run an action, like clippy, cargo-audit or fmt. I've grouped these into a single action, so we only compile lighthouse once, then in each step we run the checks. This avoids compiling lighthouse like 5 times.
- Ive made doppelganger tests run on our local machines to avoid pulling foundry, building and making lcli which are all now baked into the images.
- We have sccache and do not incremental compile lighthouse
Misc bonus things:
- Cargo update
- Fix web3 signer openssl keys which is required after a cargo update
- Use mock_instant in an LRU cache test to avoid non-deterministic test
- Remove race condition in building web3signer tests
There's still some things we could improve on. Such as downloading the EF tests every run and the web3-signer binary, but I've left these to be out of scope of this PR. I think the above are meaningful improvements.
Co-authored-by: Paul Hauner <paul@paulhauner.com>
Co-authored-by: realbigsean <seananderson33@gmail.com>
Co-authored-by: antondlr <anton@delaruelle.net>
2023-10-03 06:33:15 +00:00
|
|
|
rmfile = rm -f $(1)
|
|
|
|
|
rmdir = rm -rf $(1)
|
|
|
|
|
makedir = mkdir -p $(1)
|
2021-05-19 23:05:16 +00:00
|
|
|
endif
|
|
|
|
|
else
|
Ultra Fast Super Slick CI (#4755)
Attempting to improve our CI speeds as its recently been a pain point.
Major changes:
- Use a github action to pull stable/nightly rust rather than building it each run
- Shift test suite to `nexttest` https://github.com/nextest-rs/nextest for CI
UPDATE:
So I've iterated on some changes, and although I think its still not optimal I think this is a good base to start from. Some extra things in this PR:
- Shifted where we pull rust from. We're now using this thing: https://github.com/moonrepo/setup-rust . It's got some interesting cache's built in, but was not seeing the gains that Jimmy managed to get. In either case tho, it can pull rust, cargofmt, clippy, cargo nexttest all in < 5s. So I think it's worthwhile.
- I've grouped a few of the check-like tests into a single test called `code-test`. Although we were using github runners in parallel which may be faster, it just seems wasteful. There were like 4-5 tests, where we would pull lighthouse, compile it, then run an action, like clippy, cargo-audit or fmt. I've grouped these into a single action, so we only compile lighthouse once, then in each step we run the checks. This avoids compiling lighthouse like 5 times.
- Ive made doppelganger tests run on our local machines to avoid pulling foundry, building and making lcli which are all now baked into the images.
- We have sccache and do not incremental compile lighthouse
Misc bonus things:
- Cargo update
- Fix web3 signer openssl keys which is required after a cargo update
- Use mock_instant in an LRU cache test to avoid non-deterministic test
- Remove race condition in building web3signer tests
There's still some things we could improve on. Such as downloading the EF tests every run and the web3-signer binary, but I've left these to be out of scope of this PR. I think the above are meaningful improvements.
Co-authored-by: Paul Hauner <paul@paulhauner.com>
Co-authored-by: realbigsean <seananderson33@gmail.com>
Co-authored-by: antondlr <anton@delaruelle.net>
2023-10-03 06:33:15 +00:00
|
|
|
rmfile = rm -f $(1)
|
|
|
|
|
rmdir = rm -rf $(1)
|
|
|
|
|
makedir = mkdir -p $(1)
|
2021-05-19 23:05:16 +00:00
|
|
|
endif
|
|
|
|
|
|
2020-10-02 01:42:27 +00:00
|
|
|
$(OUTPUT_DIR): $(TARBALL)
|
2021-05-19 23:05:16 +00:00
|
|
|
$(call rmdir,$@)
|
Ultra Fast Super Slick CI (#4755)
Attempting to improve our CI speeds as its recently been a pain point.
Major changes:
- Use a github action to pull stable/nightly rust rather than building it each run
- Shift test suite to `nexttest` https://github.com/nextest-rs/nextest for CI
UPDATE:
So I've iterated on some changes, and although I think its still not optimal I think this is a good base to start from. Some extra things in this PR:
- Shifted where we pull rust from. We're now using this thing: https://github.com/moonrepo/setup-rust . It's got some interesting cache's built in, but was not seeing the gains that Jimmy managed to get. In either case tho, it can pull rust, cargofmt, clippy, cargo nexttest all in < 5s. So I think it's worthwhile.
- I've grouped a few of the check-like tests into a single test called `code-test`. Although we were using github runners in parallel which may be faster, it just seems wasteful. There were like 4-5 tests, where we would pull lighthouse, compile it, then run an action, like clippy, cargo-audit or fmt. I've grouped these into a single action, so we only compile lighthouse once, then in each step we run the checks. This avoids compiling lighthouse like 5 times.
- Ive made doppelganger tests run on our local machines to avoid pulling foundry, building and making lcli which are all now baked into the images.
- We have sccache and do not incremental compile lighthouse
Misc bonus things:
- Cargo update
- Fix web3 signer openssl keys which is required after a cargo update
- Use mock_instant in an LRU cache test to avoid non-deterministic test
- Remove race condition in building web3signer tests
There's still some things we could improve on. Such as downloading the EF tests every run and the web3-signer binary, but I've left these to be out of scope of this PR. I think the above are meaningful improvements.
Co-authored-by: Paul Hauner <paul@paulhauner.com>
Co-authored-by: realbigsean <seananderson33@gmail.com>
Co-authored-by: antondlr <anton@delaruelle.net>
2023-10-03 06:33:15 +00:00
|
|
|
$(call makedir,$@)
|
2020-10-02 01:42:27 +00:00
|
|
|
tar --strip-components=1 -xzf $^ -C $@
|
|
|
|
|
|
|
|
|
|
$(TARBALL):
|
2020-12-03 22:07:12 +00:00
|
|
|
curl --fail -L -o $@ $(ARCHIVE_URL)
|
2020-10-02 01:42:27 +00:00
|
|
|
|
|
|
|
|
clean-test-files:
|
2021-05-19 23:05:16 +00:00
|
|
|
$(call rmdir,$(OUTPUT_DIR))
|
2020-10-02 01:42:27 +00:00
|
|
|
|
|
|
|
|
clean-archives:
|
2021-05-19 23:05:16 +00:00
|
|
|
$(call rmfile,$(TARBALL))
|
2020-10-02 01:42:27 +00:00
|
|
|
|
|
|
|
|
generate:
|
2021-05-19 23:05:16 +00:00
|
|
|
$(call rmdir,$(GENERATE_DIR))
|
2020-10-02 01:42:27 +00:00
|
|
|
cargo run --release --bin test_generator -- $(GENERATE_DIR)
|
|
|
|
|
|
|
|
|
|
clean: clean-test-files clean-archives
|
|
|
|
|
|
|
|
|
|
.PHONY: clean clean-archives clean-test-files generate
|
|
|
|
|
|
