test(evm): un-ignore Trace_invalid_jump{,i}_exception#11799
Conversation
Both tests were `[Ignore]`d pointing at NethermindEth#140, which was closed long ago ("Review and refactor JUMP validation code"). The validation refactor landed, so the tests pass cleanly today. Verified locally: 15 consecutive standalone runs and the full `VirtualMachineTests` fixture (35 tests) all green. Drop the `[Ignore]` attribute so the trace-error coverage for invalid `JUMP` / `JUMPI` runs in CI again.
|
@claude review |
|
Claude finished @batrr's task in 1m 48s —— View job Review: test(evm): un-ignore Trace_invalid_jump{,i}_exception
Clean and correct. The two removed EVM implementation correctness — Test bytecodes are correct:
Assertion style — No findings. This restores long-missing CI coverage of the Geth |
Changes
Trace_invalid_jump_exceptionandTrace_invalid_jumpi_exceptioninNethermind.Evm.Test.VirtualMachineTestswere[Ignore]d with the reason"// https://github.com/NethermindEth/nethermind/issues/140". Issue Review and refactor JUMP validation code #140 (Review and refactor JUMP validation code) has been closed for years and the refactor landed — but the tests stayed skipped, so we have had zero coverage of theGeth-traceerrorfield on invalidJUMP/JUMPIinstructions.[Ignore]attribute so the tests run again.Types of changes
What types of changes does your code introduce?
Testing
Requires testing
If yes, did you write tests?
Notes on testing
PR is the test re-enablement; no new test added. Verified locally with 15 consecutive standalone runs (all pass) and the full
VirtualMachineTestsfixture (35 tests) green. CI on this branch will exercise the same.Documentation
Requires documentation update
Requires explanation in Release Notes