| Age | Commit message (Collapse) | Author |
|
Should fix PR kern/56780.
|
|
value of EINVAL, print the actual value.
|
|
|
|
with PT_CONTINUE in this test.
|
|
The syscall only guarantees up to 256 bytes in a single go -- if
interrupted, it might return short, but if the caller requested at
least 256 bytes it will definitely return 256 bytes.
|
|
|
|
No binary change.
|
|
isQEMU_TCG() should return false. Fixes multiple test cases that were
failing with "Test case was expecting a failure but none were raised"
on that platform.
|
|
|
|
|
|
I also deduplicated some more code
|
|
|
|
needs to be the C source file (not the base name)
|
|
|
|
QEMU misses clock interrupts.
Always check values against [ lower, upper ] bounds and use "4 * upper"
when run under QEMU.
Now becomes part of PR kern/43997 "Kernel timer discrepancies".
|
|
|
|
with a reference to PR lib/55087. Marking it as an expected failure
would be more appropriate, but that doesn't work for test cases that
fail by timing out.
|
|
|
|
has read enough that exactly PIPE_BUF space is available that the FIFO
becomes writable again.
- When creating a FIFO, ensure that the receive low water mark is 1
(a FIFO must be readable when at least 1 byte is available); this
was already the case implicitly, but this makes it explicit.
- Similarly, set the send low water mark to PIPE_BUF to ensure that
the pipe is writable when at least PIPE_BUF bytes of space are available
in the send buffer. Without this change, the strengthened test case
above does not pass (the default send low water mark is larger than
PIPE_BUF; see soreserve()).
- Make the same low water mark changes to the PIPE_SOCKETPAIR case.
|
|
behavior for FIFOs:
- A FIFO is readable so long as at least 1 byte is available.
- A FIFO is writable so long as at least PIPE_BUF (obtained with _PC_PIPE_BUF)
space is avaiable.
This will be cloned for a forthcoming kevent test case.
|
|
new writer appears.
|
|
POLLHUP, per POSIX.
- fifo_close(): Use the new fifo_socantrcvmore(), which is like the
garden-variety socantrcvmore(), except it specifies POLL_HUP rather
than POLL_IN (so the correct code for SIGIO is sent).
- sowakeup(): Allow POLL_HUP as a code (notifies poll'ers with POLLHUP).
- Add test cases for correct POLLHUP behavior with FIFOs.
Fixes PR kern/56429.
|
|
the Linux interfaces of the same name.
|
|
|
|
This case is currently not handled correctly by fwrite/fflush, which
makes the test fail sometimes. The tests for _IONBF and _IOLBF are
pretty stable though.
|
|
In case of a test failure, this outputs a diff between the actual and
expected files.
Even with the smaller buffer size LMAX, the fully buffered test fails.
It does so after printing numbers up to 12773, which together take 65532
bytes. The next number, 12774, would cross the 65536 boundary, but
instead of that number, 12710730 was written.
|
|
Previously, the test output was:
FAILED: Test case body returned a non-ok exit code, but this is
not allowed
In many cases, the test now succeeds, but in some cases it fails:
h_testnumbers: bad line "1287185
", expected 12774
h_testnumbers: bad line "6186889
", expected 6154889
|
|
On amd64, the test stdio_intr_iofbf fails:
stdout: numbers.in...iw.ir.ir. OK
stderr: h_testnumbers: bad line 3914889
This information is not enough to get a complete picture of the
situation, so provide more details.
|
|
|
|
|
|
|
|
|
|
done for aarch64, arm, and powerpc. Otherwise, child is trapped to the
PTRACE_BREAKPOINT_ASM (== trapa) instruction indefinitely.
Fix tests/lib/libc/sys/t_ptrace_wait*:core_dump_procinfo.
|
|
|
|
|
|
|
|
|
|
the string it points to, it is never passed to a function not taking a
const char * arg, and this allows "" (or other literal strings if ever
needed) to be assigned to it - which should fix the build.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
during their allocation, which the test cannot handle properly.
2. Enable building the test without atf so that we can easily debug with
atf memory allocations interfering
3. Add memory tracing (disabled)
|
|
|
|
because it causes GXemul to exit rather than generating a trap. A bug
report has been sent to the GXemul author.
|
|
|
|
|
|
|