llvm / llvm/llvm-project

[libc] Revisit syscall tests that have different behaviors under QEMU.

Open
#209,273 1 comment 0 reactions 0 assignees View on GitHub
libc
Dominant language
LLVM
Stars
40.5k
Forks
18.7k
PR merge metrics
PR metrics pending

Description

The following tests have different behaviors under qemu-riscv64:
```
sys/mman/linux/madvise_test
sys/mman/linux/mincore_test
sys/mman/linux/mlock_test
sys/mman/linux/mremap_test
sys/mman/linux/posix_madvise_test
socket/linux/sendrecvmmsg_test
socket/linux/socketopt_test
socket/linux/socketpair_test
unistd/pread_pwrite_test
unistd/read_write_test
```
They are accommodated in #208920 .

Review these tests again after June 2028 to see if those exceptions are still needed.

Contributor guide

Open the contributing guide

Research direction

After June 2028, start with the listed sys/mman/linux, socket/linux, and unistd tests and review their behavior under qemu-riscv64. Compare the existing exceptions accommodated in #208920 with current results; done means determining whether each exception is still needed and updating the tests accordingly.

Written by the indexing model from the issue text.

Assessment

Domain
operating-systems, testing-qa
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.