Skip to content
New issue

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

Change the mutex tests to reduce dependence on clock time as a means … #2

Merged
merged 1 commit into from
Jun 12, 2020
Merged

Change the mutex tests to reduce dependence on clock time as a means … #2

merged 1 commit into from
Jun 12, 2020

Conversation

creativepsyco
Copy link
Contributor

…of verifying locking functionality.

Tested with:

for i in `seq 100`; do pub run test; done

fixes #1

…of verifying locking functionality.

Tested with:
```
for i in `seq 100`; do pub run test; done
```
@hoylen hoylen merged commit e126af8 into hoylen:master Jun 12, 2020
@hoylen
Copy link
Owner

hoylen commented Jun 12, 2020

That looks great. Thank you for contributing it.

The "multiple write locks" test assumes locks are acquired in "first-in-first out order", which is an implementation feature rather than a guarantee. But it is fine for now, since there's no plans at this stage to change the scheduling algorithm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

flaky mutex read write test
2 participants