Skip to content

Regression in RandomScheduler / fuzz testing #113

Open
@colin-scott

Description

Something seems to be wrong with RandomScheduler -- it's no longer able to trigger bugs during fuzz testing after several hours of execution, in cases where it was previously able to find bugs within <10 minute.

I'm guessing the root cause is related to the recent changes I made for InteractiveScheduler. (Although, strangely, ReplayScheduler and InteractiveScheduler are both able to reproduce existing recordings correctly, so this regression only seems to be affecting RandomScheduler?)

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions