Skip to content

test_worst_calldatasize()

Documentation for tests/benchmark/test_worst_compute.py::test_worst_calldatasize@88e9fb8f.

Generate fixtures for these test cases for Osaka with:

fill -v tests/benchmark/test_worst_compute.py::test_worst_calldatasize -m benchmark

Test running a block with as many CALLDATASIZE as possible.

Source code in tests/benchmark/test_worst_compute.py 
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
@pytest.mark.parametrize("calldata_length", [0, 1_000, 10_000])
def test_worst_calldatasize(
    benchmark_test: BenchmarkTestFiller,
    calldata_length: int,
) -> None:
    """Test running a block with as many CALLDATASIZE as possible."""
    benchmark_test(
        code_generator=JumpLoopGenerator(
            attack_block=Op.POP(Op.CALLDATASIZE),
            tx_kwargs={"data": b"\x00" * calldata_length},
        ),
    )

Parametrized Test Cases

This test case is only parametrized by fork.

Test ID (Abbreviated) calldata_length
...fork_Prague-blockchain_test-calldata_length_0 0
...fork_Prague-blockchain_test-calldata_length_1000 1000
...fork_Prague-blockchain_test-calldata_length_10000 10000
...fork_Osaka-blockchain_test-calldata_length_0 0
...fork_Osaka-blockchain_test-calldata_length_1000 1000
...fork_Osaka-blockchain_test-calldata_length_10000 10000