windows CI failure
Open
Nobody has claimed this yet.
area/testing
area/windows
- Dominant language
- Go
- Stars
- 10.3k
- Forks
- 1.5k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 50
Description
Saw this failure on my PR branch. https://github.com/tonistiigi/buildkit/runs/1119868274 @TBBle
2020-09-15T20:44:37.1037618Z --- FAIL: TestCacheMountLockedRefs (1.78s)
2020-09-15T20:44:37.1043819Z exec_test.go:343:
2020-09-15T20:44:37.1069539Z Error Trace: exec_test.go:343
2020-09-15T20:44:37.1071822Z Error: mount did not unlock
2020-09-15T20:44:37.1072621Z Test: TestCacheMountLockedRefs
2020-09-15T20:44:37.1073226Z === CONT TestMkdirMkfile
2020-09-15T20:44:37.1073729Z --- PASS: TestMkdirMkfile (0.00s)
2020-09-15T20:44:37.1074320Z --- PASS: TestCacheMountSharedRefs (1.62s)
2020-09-15T20:44:37.1074819Z FAIL
2020-09-15T20:44:37.1075296Z FAIL github.com/moby/buildkit/solver/llbsolver/ops 5.465s
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 the linked Windows CI run and the failure at exec_test.go:343 in TestCacheMountLockedRefs. Reproduce the test on Windows and investigate why the mount does not unlock, checking the related TestCacheMountSharedRefs behavior. Done means the failing test passes in Windows CI without regressing the cache-mount tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100