fix(tests): fixed test_push.py::test_stack_overflow test by reducing contract size to below allowed max

[felix314159]

🗒️ Description

Issue is described in #1699, ty for reporting!

How to run

First run reth via:
reth node --dev --chain dev --http --authrpc.addr 127.0.0.1 --http.port 8545
then run:
uv run execute remote -m state_test --fork=Shanghai --rpc-endpoint=http://127.0.0.1:8545 --rpc-seed-key=2a871d0798f97d79848a013d4936a73bf4cc922c825d33c1cf7073dff6d409c6 --rpc-chain-id=1337 --tx-wait-timeout 60 -vv -s tests/frontier/opcodes/test_push.py::test_stack_overflow

Before this PR it failed from PUSH23 onwards due to max contract size (24576) exceeded. After this PR everything passes. I also tried filling and consume direct with geth's evm and it all passes. Ty for the push0 idea @marioevz !

🔗 Related Issues or PRs

N/A.

✅ Checklist

• All: Ran fast tox checks to avoid unnecessary CI fails, see also Code Standards and Enabling Pre-commit Checks:

  uvx --with=tox-uv tox -e lint,typecheck,spellcheck,markdownlint

• All: PR title adheres to the repo standard - it will be used as the squash commit message and should start type(scope):.
• All: Considered adding an entry to CHANGELOG.md.
• All: Considered updating the online docs in the ./docs/ directory.
• All: Set appropriate labels for the changes (only maintainers can apply labels).
• Tests: Ran mkdocs serve locally and verified the auto-generated docs for new tests in the Test Case Reference are correctly formatted.
• Tests: For PRs implementing a missed test case, update the post-mortem document to add an entry the list.
• Ported Tests: All converted JSON/YML tests from ethereum/tests or tests/static have been assigned @ported_from marker.

[felix314159]

Noo another coverage report issue

[LouisTsai-Csie]

We are currently using the Frontier and Homestead forks, which do not support the PUSH0 opcode. Since PUSH0 was introduced in the Shanghai upgrade, you should use Op.PUSH1(0) instead.

Related EIP: https://eips.ethereum.org/EIPS/eip-3855

[felix314159]

True, ty! Coverage still fails tho :/

[LouisTsai-Csie]

I check the log, it seems all the cases are passing now. The error message is as follow, I do not know what happen, but maybe a second run will solve this XD

Run echo "=== Original BASE (main) test IDs ==="
=== Original BASE (main) test IDs ===
Traceback (most recent call last):
  File "<string>", line 1, in <module>
FileNotFoundError: [Errno 2] No such file or directory: '/home/runner/work/execution-spec-tests/execution-spec-tests/evmtest_coverage/coverage/BASE_TESTS/.meta/index.json'
Error: Process completed with exit code 1.

[felix314159]

I fixed those issues by making the coverage script more robust, now we unlocked a new error :D but this is the line coverage error that i expected in the first place, the thing that happens whenever you change anything of an existing test