Skip to content

consensus: TestByzantinePrevoteEquivocation is flaky #1917

@faddat

Description

@faddat

Bug Report

TestByzantinePrevoteEquivocation is flaky

Setup

CI

Config

CI

What happened?

Sometimes TestByzantinePrevoteEquivocation works. Sometimes TestByzantinePrevoteEquivocation does not work.

In flaky test cases we don't know if it is the code or the test, by the way. This means that ByzantinePrevoteEquivocation could be malfunctioning.

What did you expect to happen?

I expect tests to work consistently.

How to reproduce it

Work on Comet

Logs

Fail Log

Looking at the surrounding commits in:

#1907 it is quite clear no relevant changes were made.

Magic Success 1 commit later with no relevant code changes:

Anything else we need to know

While we call these flaky tests, the name doesn't do reality justice. They're ambiguity as to weather or not one function or another actually works as designed, and they greatly slow development on comet, while making it more expensive.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P:tech-debtPriority: Technical debt that needs to be paid off to enable us to move faster, reliablybugSomething isn't workingconsensusevidencetestingrelated to unit testing in general

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions