Skip to content

Remove explicit semaphore in tests #640

@lehins

Description

@lehins

Due to a recent switch to hspec from tasty we no longer need to create an explicit lock in tests, since hspec supports sequential test execution.
This task is about removing this ugly locking mechanism from cardano-crypto-class test suite:

-- This lock is used to prevent tests that use mlocking from running
-- concurrently. Concurrent execution of these tests can cause the testsuite
-- to exhaust mlock quota; but each individual test on its own should be
-- fine.
mlockLock <- mkLock

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    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