We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It looks like the unit tests for settings are prone to occasional lock-poisoning errors, as evidenced by this test run.
settings
Suggest that we wrap tests that affect global state in a mutex similar to what we did for OpenSSL in #516.
The text was updated successfully, but these errors were encountered:
FWIW the test run cited above succeeded when re-run.
Sorry, something went wrong.
gpeacock
No branches or pull requests
It looks like the unit tests for
settings
are prone to occasional lock-poisoning errors, as evidenced by this test run.Suggest that we wrap tests that affect global state in a mutex similar to what we did for OpenSSL in #516.
The text was updated successfully, but these errors were encountered: