Skip to content

Result parser / error signature matching #8

Description

@bhcopeland

Work out pass/fail from test output and check it's the same failure
across bisection steps.

This matters because you can hit a different bug mid-bisect and end
up chasing the wrong thing. Logspec already generates SHA1 error
signatures — we should use those to confirm we're still seeing the
original regression at each step.

Also need to handle non-monotonic pass/fail along the history, which
is more common than you'd hope.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions