Skip to content

False positives in benchmark alerts #1526

Description

@tsmbland

I'm getting a lot of benchmarking alerts for PRs that very clearly should not impact performance (e.g. documentation-only changes such as #1524). I think very likely running time for benchmarks can just vary naturally on different runs (different machines, different loads), so the current approach of caching results to compare later is probably flawed

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    • Status
      📋 Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions