Tests hang with "... is locked, waiting"
Nobody has claimed this yet.
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
If I don't delete the directory after every run, t/unicodable.t hangs writing repeatedly
/tmp/whateverable/rakudo-moar/c80ea2f28939875586d326ca1c63db2cdf7b8c8d is locked. Waiting…
after
ok 57 - \U lookup by code
I do have the "mesozoic" zstd, actually the one built from source.
zstd --version
*** zstd command line interface 64-bits v1.3.4, by Yann Collet ***
Also rakudo 2018.04.
(Also this happened only when I changed the code to be detected early). It's working now after I put the original Whateverable back. It probably means that zstd is working in some unexpected places, or that some test would be needed to check that it's correct and that it's working)
Contributor guide
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.
Research direction
Start with t/unicodable.t and reproduce the hang after a run without deleting its directory. Inspect the repeated lock message after the '\U lookup by code' test and compare behavior with the reported zstd 1.3.4 and Rakudo 2018.04 setup. Done means the test completes without manual directory deletion and the lock behavior is covered by an appropriate test.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100