Skip to content

Flaky "Invalid Missing Ancestor Syncing ReOrg" tests fail when payload contains no transactions #1351

@fgimenez

Description

@fgimenez

The "Invalid Missing Ancestor Syncing ReOrg" tests that use transaction-based invalid fields (InvalidTransactionSignature, InvalidTransactionNonce, InvalidTransactionGas, InvalidTransactionGasPrice, InvalidTransactionValue) are failing eventually with the error:

FAIL: Unable to customize payload: no transactions available for modification

AIUI this is not related to the client, the payload builder sometimes produces a payload with no transactions and the test seems to fail during setup here before even testing the client, is this correct?

This happened in this build for instance https://github.com/paradigmxyz/reth/actions/runs/18315677425 relevant logs attached

logs.tar.gz

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions