Skip to content

Fill Command-Line Options

Fill is a pytest-based command. This page lists custom options that the fill command provides. To see the full list of options that is available to fill (including the standard pytest and plugin command-line options) use fill --pytest-help.

This page is automatically generated from the current fill --help output.

Command Help Output

usage: fill [-h] [--strict-alloc] [--ca-start CA_START] [--ca-incr CA_INCR]
            [--evm-code-type EVM_CODE_TYPE] [--solc-bin SOLC_BIN]
            [--solc-version SOLC_VERSION] [--evm-bin EVM_BIN] [--traces]
            [--verify-fixtures] [--verify-fixtures-bin VERIFY_FIXTURES_BIN]
            [--filler-path FILLER_PATH] [--output OUTPUT] [--clean]
            [--flat-output] [--single-fixture-per-file] [--no-html]
            [--build-name BUILD_NAME] [--skip-index SKIP_INDEX]
            [--block-gas-limit BLOCK_GAS_LIMIT] [--generate-pre-alloc-groups]
            [--use-pre-alloc-groups] [--evm-dump-dir EVM_DUMP_DIR]
            [--skip-evm-dump] [--show-ported-from [SHOW_PORTED_FROM]]
            [--skip-coverage-missed-reason]
            [--ported-from-output-file PORTED_FROM_OUTPUT_FILE]
            [--links-as-filled] [--forks] [--fork FORK] [--from FROM]
            [--until UNTIL]

options:
  -h, --help            show this help message and exit

Arguments defining pre-allocation behavior during test filling.:
  --strict-alloc        [DEBUG ONLY] Disallows deploying a contract in a
                        predefined address.
  --ca-start CA_START, --contract-address-start CA_START
                        The starting address from which tests will deploy
                        contracts.
  --ca-incr CA_INCR, --contract-address-increment CA_INCR
                        The address increment value to each deployed contract
                        by a test.
  --evm-code-type EVM_CODE_TYPE
                        Type of EVM code to deploy in each test by default.

Arguments defining the solc executable:
  --solc-bin SOLC_BIN   Path to a solc executable (for Yul source
                        compilation). No default; if unspecified `--solc-
                        version` is used.
  --solc-version SOLC_VERSION
                        Version of the solc compiler to use. Default: 0.8.24.

Arguments defining evm executable behavior:
  --evm-bin EVM_BIN     Path to an evm executable (or name of an executable in
                        the PATH) that provides `t8n`. Default: `ethereum-
                        spec-evm-resolver`.
  --traces              Collect traces of the execution information from the
                        transition tool.
  --verify-fixtures     Verify generated fixture JSON files using geth's evm
                        blocktest command. By default, the same evm binary as
                        for the t8n tool is used. A different (geth) evm
                        binary may be specified via --verify-fixtures-bin,
                        this must be specified if filling with a non-geth t8n
                        tool that does not support blocktest.
  --verify-fixtures-bin VERIFY_FIXTURES_BIN
                        Path to an evm executable that provides the
                        `blocktest` command. Default: The first (geth) 'evm'
                        entry in PATH.

Arguments defining filler location and output:
  --filler-path FILLER_PATH
                        Path to filler directives
  --output OUTPUT       Directory path to store the generated test fixtures.
                        Must be empty if it exists. If the specified path ends
                        in '.tar.gz', then the specified tarball is
                        additionally created (the fixtures are still written
                        to the specified path without the '.tar.gz' suffix).
                        Can be deleted. Default: './fixtures'.
  --clean               Clean (remove) the output directory before filling
                        fixtures.
  --flat-output         Output each test case in the directory without the
                        folder structure.
  --single-fixture-per-file
                        Don't group fixtures in JSON files by test function;
                        write each fixture to its own file. This can be used
                        to increase the granularity of --verify-fixtures.
  --no-html             Don't generate an HTML test report (in the output
                        directory). The --html flag can be used to specify a
                        different path.
  --build-name BUILD_NAME
                        Specify a build name for the fixtures.ini file, e.g.,
                        'stable'.
  --skip-index SKIP_INDEX
                        Skip generating an index file for all produced
                        fixtures.
  --block-gas-limit BLOCK_GAS_LIMIT
                        Default gas limit used ceiling used for blocks and
                        tests that attempt to consume an entire block's gas.
                        (Default: 72000000)
  --generate-pre-alloc-groups
                        Generate pre-allocation groups (phase 1 only).
  --use-pre-alloc-groups
                        Fill tests using existing pre-allocation groups (phase
                        2 only).

Arguments defining debug behavior:
  --evm-dump-dir EVM_DUMP_DIR, --t8n-dump-dir EVM_DUMP_DIR
                        Path to dump the transition tool debug output.
                        (Default: /home/runner/work/execution-spec-
                        tests/execution-spec-tests/logs/evm)
  --skip-evm-dump, --skip-t8n-dump
                        Skip dumping the the transition tool debug output.

Arguments for showing ported_from marker information:
  --show-ported-from [SHOW_PORTED_FROM]
                        Show information from @pytest.mark.ported_from
                        markers. Use '--show-ported-from' or '--show-ported-
                        from=paths' to show static filler paths. Use '--show-
                        ported-from=prs' to show PR URLs.
  --skip-coverage-missed-reason
                        When using --show-ported-from, exclude tests that have
                        coverage_missed_reason in their
                        @pytest.mark.ported_from marker. These are tests that
                        were intentionally not ported from the original static
                        filler files, typically because they are redundant or
                        obsolete. This helps filter out accepted coverage gaps
                        when analyzing test coverage.
  --ported-from-output-file PORTED_FROM_OUTPUT_FILE
                        Output file for ported_from information.
  --links-as-filled     Convert URLs or paths to filled test file paths for
                        coverage script. Used in combination with --show-
                        ported-from.

Specify the fork range to generate fixtures for:
  --forks               Display forks supported by the test framework and
                        exit.
  --fork FORK           Only fill tests for the specified fork.
  --from FROM           Fill tests from and including the specified fork.
  --until UNTIL         Fill tests until and including the specified fork.

This page was automatically generated from fill --help output.