authorgravatar for alex@alexrp.comAlex Rønne Petersen <alex@alexrp.com> 2025-09-25 05:47:15+02:00
committergravatar for alex@alexrp.comAlex Rønne Petersen <alex@alexrp.com> 2025-09-25 12:57:56+02:00
logdd4be26f539548520bdfc159e2a86ab5301e12e8
tree2d08e254d5817070050acebca0cf55c286792988
parent6257f4abb7c65b034b4c0804cff2623e22b9971d

libc-test: disable daemon-failure.c

It's flaky in that systems with a high FD limit will get an unexpected ENOMEM error from daemon(), failing the test.

1 files changed, 1 insertions(+), 1 deletions(-)

test/libc.zig+1-1
...@@ -71,7 +71,7 @@ pub fn addCases(cases: *tests.LibcContext) void {...@@ -71,7 +71,7 @@ pub fn addCases(cases: *tests.LibcContext) void {
71 cases.addLibcTestCase("functional/wcsstr.c", true, .{});71 cases.addLibcTestCase("functional/wcsstr.c", true, .{});
72 cases.addLibcTestCase("functional/wcstol.c", true, .{});72 cases.addLibcTestCase("functional/wcstol.c", true, .{});
7373
74 cases.addLibcTestCase("regression/daemon-failure.c", false, .{});74 // cases.addLibcTestCase("regression/daemon-failure.c", false, .{}); - unexpected ENOMEM with high FD limit
75 cases.addLibcTestCase("regression/dn_expand-empty.c", false, .{});75 cases.addLibcTestCase("regression/dn_expand-empty.c", false, .{});
76 cases.addLibcTestCase("regression/dn_expand-ptr-0.c", false, .{});76 cases.addLibcTestCase("regression/dn_expand-ptr-0.c", false, .{});
77 cases.addLibcTestCase("regression/execle-env.c", false, .{});77 cases.addLibcTestCase("regression/execle-env.c", false, .{});