Failing tests under docker
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
Probably due to docker weirdness.
The following tests FAILED:
41 - chown (Failed)
42 - chown-no-syscallbuf (Failed)
67 - cwd_inaccessible (Failed)
68 - cwd_inaccessible-no-syscallbuf (Failed)
419 - setuid (Failed)
420 - setuid-no-syscallbuf (Failed)
547 - unshare (Failed)
548 - unshare-no-syscallbuf (Failed)
765 - ttyname (Failed)
989 - chown-32 (Failed)
990 - chown-32-no-syscallbuf (Failed)
1015 - cwd_inaccessible-32 (Failed)
1016 - cwd_inaccessible-32-no-syscallbuf (Failed)
1367 - setuid-32 (Failed)
1368 - setuid-32-no-syscallbuf (Failed)
1495 - unshare-32 (Failed)
1496 - unshare-32-no-syscallbuf (Failed)
1713 - ttyname-32 (Failed)
The chown one at least is due to the getgroups call failing. Didn't look at any others yet.
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 by reproducing the Docker test run and examining the failures for chown, cwd_inaccessible, setuid, unshare, and ttyname, including their -no-syscallbuf and -32 variants. Investigate the reported getgroups failure first, then determine the cause of the remaining failures. Done means the listed tests pass under Docker.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, docker, linux
- Domain
- operating-systems, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100