Skip to content

Flaky Tests Tracker #3012

Open
Open
@prasannavl

Description

@prasannavl

Documenting flaky tests

  • Most flaky tests are related to concurrency and how soon the node gets running, system resources and minor timing effects due to it. However, documenting them as we can aim to fix it and not ensure we don't end up adding new ones to it.
  • Majority of them can be re-created with varying concurrency with MAKE_JOBS=32/64/128/256 etc, and also selecting different numbers or tests at random, and/or limiting resources with cgroups.

Wide spectrum

Localized

  • wallet_txn_doublespend.py
    • This checks for initial block download and fails. If we loop through it to wait for longer, this should be fixed.
  • feature_token_merge.py
    • This seems to be something in test that's out of sync
test_framework.authproxy.JSONRPCException: Test AddPoolLiquidityTx execution failed:                                           
tx must have at least one input from account owner (-32600)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions