Hi Bruno,
On 5/17/24 2:10 PM, Bruno Haible wrote:
> On NetBSD 9.0 and 10.0, I always see the same tests fail:
>
> FAIL: test-dup3
> ===
>
> ../../gltests/test-dup3.c:113: assertion 'dup3 (fd, fd, o_flags) == -1' failed
> FAIL test-dup3 (exit status: 134)
It looks like dup3 behaves d
Collin Funk wrote:
> Perhaps it is worth mentioning somewhere that XFAIL
> may refer to an actual bug that needs investigation?
Well, you know it now: All XFAIL are potential bugs, and need investigation
if the platform is considered important. :)
Bruno
On 5/17/24 2:10 PM, Bruno Haible wrote:
> Since I don't have time to investigate them and, OTOH, I don't want that
> the NetBSD test failures mark the entire continuous integration run as
> "failed", here are patches to mark them as expected failures.
Seems reasonable. Perhaps it is worth mentioni
, ts) == -1' failed
FAIL test-utimensat (exit status: 134)
Since I don't have time to investigate them and, OTOH, I don't want that
the NetBSD test failures mark the entire continuous integration run as
"failed", here are patches to mark them as expected failures.
2024-0
