Add testgen badge to readme (#3933)

This commit is contained in:
Justin Traglia 2024-09-26 09:35:36 -05:00 committed by GitHub
parent 3162c91aff
commit 3196f3270f
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 11 additions and 1 deletions

View File

@ -52,6 +52,16 @@ jobs:
cp -r presets/ ../consensus-spec-tests/presets cp -r presets/ ../consensus-spec-tests/presets
cp -r configs/ ../consensus-spec-tests/configs cp -r configs/ ../consensus-spec-tests/configs
find . -type d -empty -delete find . -type d -empty -delete
- name: Check for errors
run: |
if grep -q "\[ERROR\]" consensustestgen.log; then
echo "There is an error in the log"
exit 1
fi
if find . -type f -name "INCOMPLETE" | grep -q "INCOMPLETE"; then
echo "There is an INCOMPLETE file"
exit 1
fi
- name: Archive configurations - name: Archive configurations
run: | run: |
cd consensus-spec-tests cd consensus-spec-tests

View File

@ -8,7 +8,7 @@ This repository hosts the current Ethereum proof-of-stake specifications. Discus
## Specs ## Specs
[![GitHub release](https://img.shields.io/github/v/release/ethereum/consensus-specs)](https://github.com/ethereum/consensus-specs/releases/) [![PyPI version](https://badge.fury.io/py/eth2spec.svg)](https://badge.fury.io/py/eth2spec) [![GitHub release](https://img.shields.io/github/v/release/ethereum/consensus-specs)](https://github.com/ethereum/consensus-specs/releases/) [![PyPI version](https://badge.fury.io/py/eth2spec.svg)](https://badge.fury.io/py/eth2spec) [![testgen](https://github.com/ethereum/consensus-specs/actions/workflows/generate_vectors.yml/badge.svg?branch=dev&event=schedule)](https://github.com/ethereum/consensus-specs/actions/workflows/generate_vectors.yml)
Core specifications for Ethereum proof-of-stake clients can be found in [specs](specs/). These are divided into features. Core specifications for Ethereum proof-of-stake clients can be found in [specs](specs/). These are divided into features.
Features are researched and developed in parallel, and then consolidated into sequential upgrades when ready. Features are researched and developed in parallel, and then consolidated into sequential upgrades when ready.