coop-threads: The open-posix-test-suite conformance tests take a long time to run
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- c
- Domain
- operating-systems, testing
Research direction
Start with the open-posix-test-suite conformance tests used by coop-threads and identify where tests sleep internally. Replace unnecessary waiting with synchronization mechanisms, then run the conformance suite in CI and locally to confirm it completes faster without losing coverage.
Written by the indexing model from the issue text.
Description
It looks like there's probably tests that sleep internally but this would ideally be replaced with other synchronization mechanisms to avoid wasting time in CI and when testing locally.
- Dominant language
- C
- Stars
- 1k
- Forks
- 268
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 20
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 WebAssembly/wasi-libc
-
wasip2: enabling O_APPEND with fcntl reuses the old positional output stream and overwrites the fileOpen
Difficulty 3/5 1-2 days Newbie friendliness 70/100
WebAssembly/wasi-libc#919 ·
Maintainers usually reply within 1 day
-
wasip2/wasip3: reads never see data appended to a file after reaching EOFPossibly taken @libsmol claimed this 24 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 61/100
WebAssembly/wasi-libc#889 ·
Maintainers usually reply within 1 day
-
Contradicting `SOL_TCP` and `SOL_UDP` definition for p1May be free again A pull request for this issue was closed without being merged. Open
Difficulty 3/5 1-2 days Newbie friendliness 45/100
WebAssembly/wasi-libc#855 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
WebAssembly/wasi-libc#815 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
WebAssembly/wasi-libc#778 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
All issues in WebAssembly/wasi-libc
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
389ds/389-ds-base#8152 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
isolation2 lockmodes fails on cassert builds: extra AccessShareLock on partition rootPossibly taken @tuhaihe claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/cloudberry#2356 ·
Maintainers usually reply within 2 days
-
windows-artifacts: the win-arm64 job uses a Visual Studio generator missing from windows-11-armOpen
Difficulty 1/5 Under an hour Newbie friendliness 86/100
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 91/100