Skip to content

Deterministic runs? #568

Open
Open

Description

@el-yawd

Hey! Awesome project!

I'm building a small storage engine and compio seems the best fit for it, however, the project is built from the ground up with Deterministic Simulation Testing (DST) and in order to it use compio I need to have sure that, given the same key, every run goes exactly the same (or at least exactly enough). Idk, if it's in the roadmap but it would be quite useful.

Edit: "given the same seed"

Activity

  1. George-Miao commented on Dec 12, 2025

    @George-Miao
    Member

    By key, do you mean Key in compio_driver?

  2. Berrysoft commented on Dec 14, 2025

    @Berrysoft
    Member

    No kernel ensures the completion order when there are more than one tasks awaiting. It's not a psedo random, but a real random event if you take the IO devices into account.

  3. el-yawd commented on Dec 14, 2025

    @el-yawd
    Author

    Yeah I know, that's why the simulator doesn't do any real kernel completion, I'm building it with a IO trait which the simulator implements. My question about non-determinism is for cases like this one.

    I'm not familiar with compio internals so that's why I asked

  4. Berrysoft commented on Dec 15, 2025

    @Berrysoft
    Member

    Well, yes. compio uses select macro in some cases (time and quic, etc.).

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

    enhancementNew feature or requesthelp wantedExtra attention is needed

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions