Skip to content

test error recovery #3

@rbdannenberg

Description

@rbdannenberg

In particular, let's write a test that repeatedly calls o2 functions and where malloc fails after a random number of calls -- this can then be left running (I hope) in a loop that constantly reinitializes o2 and runs until failure and cleans up.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions