Skip to content

Performance Regression Detected on main (cacef0a) #3771

Description

@github-actions

Performance Regression Detected on main

Statistically significant benchmark regressions were detected by Bencher
using a Student's t-test (95% confidence interval, up to 64 sample history).

Detail Value
Commit cacef0a
Pushed by @justin808
Workflow run Run #4943
Bencher dashboard View history

What to do

  1. Check the workflow run for the full Bencher HTML report
  2. Review the Bencher dashboard to see which metrics regressed
  3. Investigate the commit; expected trade-off or unintended regression?
  4. If unintended, open a fix PR and reference this issue
  5. Close this issue once resolved; subsequent regressions will open a new one

This issue was created automatically by the benchmark CI workflow.

Metadata

Metadata

Assignees

No one assigned

    Labels

    performance-regressionAutomated: benchmark regression detected on main

    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