Add a test for Mutex_m#try_lock
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 85/100
Research direction
Start by locating the current tests for Mutex_m#try_lock and run the existing test suite. Add coverage showing that the first call succeeds and a second call while the mutex remains locked returns false; done means both behaviors are asserted.
Written by the indexing model from the issue text.
Description
The current tests check that try_lock exists, but they do not verify how it behaves.
It would be useful to test that the first call succeeds and a second call returns false while the mutex is already locked.
- Dominant language
- Ruby
- Stars
- 78
- Forks
- 12
- Avg merge
- 3d 21h
- Merged PRs (30d)
- 2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ruby/mutex_m
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
riscv/riscv-unified-db#2626 ·
-
Component: GLib
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
ds-drift
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
we-promise/sure#3693 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
simp/pupmod-simp-simp#395 ·