authorgravatar for mlugg@mlugg.co.ukMatthew Lugg <mlugg@mlugg.co.uk> 2023-09-23 19:07:30+01:00
committergravatar for mlugg@mlugg.co.ukMatthew Lugg <mlugg@mlugg.co.uk> 2023-09-23 22:01:08+01:00
log62d077cfa1ad5ebbf97ed91a71d5b88f9c313e9d
tree06c2ffd8015e7846d257261e09f6808f20fee70f
parent09a57583a4ccce30603ffc8d0e3d7359dc3cb978
signaturelock-open Commit is signed but in an unrecognized format.

tests: give explicit stack size to module tests on WASI

I have observed the standard library tests overflowing the default WASI stack as of the previous commit. As best as I can tell, this isn't directly our fault: LLVM is just emitting less efficient code in debug builds with the new codegen patterns.

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

test/tests.zig+5
...@@ -1034,6 +1034,11 @@ pub fn addModuleTests(b: *std.Build, options: ModuleTestOptions) *Step {...@@ -1034,6 +1034,11 @@ pub fn addModuleTests(b: *std.Build, options: ModuleTestOptions) *Step {
10341034
1035 these_tests.addIncludePath(.{ .path = "test" });1035 these_tests.addIncludePath(.{ .path = "test" });
10361036
1037 if (test_target.target.getOs().tag == .wasi) {
1038 // WASI's default stack size can be too small for some big tests.
1039 these_tests.stack_size = 2 * 1024 * 1024;
1040 }
1041
1037 const qualified_name = b.fmt("{s}-{s}-{s}{s}{s}{s}", .{1042 const qualified_name = b.fmt("{s}-{s}-{s}{s}{s}{s}", .{
1038 options.name,1043 options.name,
1039 triple_txt,1044 triple_txt,