Bring back the RJUMPV_OVER_PUSH_AND_TO_START valid cases

ipsilon · Sep 27, 2024 · 2cfa4df · 2cfa4df
1 parent 4f3ce97
commit 2cfa4df
Showing 1 changed file with 10 additions and 3 deletions.
diff --git a/tests/prague/eip7692_eof_v1/eip5450_stack/test_code_validation.py b/tests/prague/eip7692_eof_v1/eip5450_stack/test_code_validation.py
@@ -182,7 +182,7 @@ def section_code_with(
     RjumpKind.__members__.values(),
 )
 # Parameter value fixed for first iteration, to cover the most important case.
-@pytest.mark.parametrize("rjump_section_idx", [1])
+@pytest.mark.parametrize("rjump_section_idx", [0, 1])
 @pytest.mark.parametrize(
     "rjump_spot",
     RjumpSpot.__members__.values(),
@@ -247,6 +247,13 @@ def test_eof_validity(
             sections.append(Section.Code(code))
     eof_test(
         data=bytes(Container(sections=sections)),
-        # `empty_rjump` acts as a sanity check, it is completely stack-neutral so
-        # should always validate.`
+        # Some RJUMP* snippets always validate successfully, so they act as sanity check
+        no_expectations_on_validity=rjump_kind
+        not in [
+            RjumpKind.EMPTY_RJUMP,
+            RjumpKind.EMPTY_RJUMPI,
+            RjumpKind.RJUMPI_OVER_NOOP,
+            RjumpKind.RJUMPI_OVER_STOP,
+            RjumpKind.RJUMPI_OVER_PUSH_POP,
+        ],
     )