Skip to content

Conversation

@pdobacz
Copy link
Contributor

@pdobacz pdobacz commented Nov 5, 2025

🗒️ Description

Opening as draft, as I am not sure this makes sense (also CI fails for a mysterious reason and I should port from this test. EDIT: done, marked ready for review

The goal is to have specifically a state test, where not only tx type being not supported is tested, but additionally that no unexpected changes got through to the state, this comes up as uncovered in evmone.

So my question is: do we want a test like this? If yes I'll fix the issues and also add the same thing for other missed types.

🔗 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 tox -e static
  • 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: Set appropriate labels for the changes (only maintainers can apply labels).
  • Ported Tests: All converted JSON/YML tests from ethereum/tests or tests/static have been assigned @ported_from marker.

@pdobacz pdobacz force-pushed the tests/tx-types branch 3 times, most recently from ed3503d to bd14c29 Compare November 6, 2025 10:02
@pdobacz pdobacz marked this pull request as ready for review November 6, 2025 10:02
Copy link
Member

@marioevz marioevz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, I'll push some changes and we can merge.

"""
Transaction's initcode for a contract-creating transaction is too large.
"""
TYPE_1_TX_PRE_FORK = auto()
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't catch on to this being duplicate in two files. This might be an artifact of the weld, I'll open an issue.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Created #1816.

"""
Tests that an EIP-2930 tx has no effect before Berlin.
"""
eip2930_tx_validity_test()
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can be accomplished via parametrize_by_fork. I'll push a change in a bit.

@codecov
Copy link

codecov bot commented Nov 27, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.08%. Comparing base (fa1a2bb) to head (56dd98b).
⚠️ Report is 9 commits behind head on forks/osaka.

Additional details and impacted files
@@               Coverage Diff               @@
##           forks/osaka    #1754      +/-   ##
===============================================
- Coverage        86.08%   86.08%   -0.01%     
===============================================
  Files              743      743              
  Lines            44072    44076       +4     
  Branches          3891     3891              
===============================================
+ Hits             37938    37941       +3     
- Misses            5656     5657       +1     
  Partials           478      478              
Flag Coverage Δ
unittests 86.08% <ø> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@marioevz marioevz merged commit ddf5842 into ethereum:forks/osaka Nov 27, 2025
14 checks passed
@pdobacz pdobacz deleted the tests/tx-types branch November 28, 2025 17:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants