TestError_SystemErrno fails with "The segment is already unlocked"
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 9.2k
- Forks
- 1.2k
- Avg merge
- 19m
- Merged PRs (30d)
- 4
Description
Our CI is showing this error when we run the unit tests:
build 12-Feb-2020 19:50:14 --- FAIL: TestError_SystemErrno (0.00s)
build 12-Feb-2020 19:50:14 error_test.go:273: expected SystemErrno to be a not exists error, but got The segment is already unlocked.
OS: Windows 10.0.17763.1
Go: 1.13.4
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.
Research direction
Start with the failing assertion at error_test.go:273 and run the unit tests on Windows 10 with Go 1.13.4 to reproduce TestError_SystemErrno. Investigate why the expected not-exists error becomes "The segment is already unlocked"; done means the test passes without regressing the reported error behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, sqlite
- Domain
- databases, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100