It looks like this test is failing with ASan:
https://logs.chromium.org/logs/emscripten-releases/buildbucket/cr-buildbucket/8728149317242328273/+/u/Emscripten_testsuite__ASan_/stdout
(and SAFE_HEAP, I imagine it's the same issue: https://logs.chromium.org/logs/emscripten-releases/buildbucket/cr-buildbucket/8728149317242328273/+/u/Emscripten_testsuite__SAFE_HEAP_/stdout)

It looks like there's a null deref in open(). It may very well be pre-existing, but just exposed by this test.

I'll look into it (unless someone else fixes it first).

This is enough to reproduce the asan failure:

#include <fcntl.h>

int main() {
  open("./does-not-exist/", O_CREAT);
}

This is enough to reproduce the asan failure:

#include <fcntl.h>

int main() {
  open("./does-not-exist/", O_CREAT);
}

Can you share the command line flags needed?

Oh thats because if you specify O_CREAT you also need to specify that mode argument. If you don't the open syscall will read the mode from uninitialized memory.

open is actually variadic. So specifying O_CREAT with a mode is like using print without enough argments.

From https://man7.org/linux/man-pages/man2/open.2.html:

The mode argument must be supplied if O_CREAT or O_TMPFILE is
specified in flags; if it is not supplied, some arbitrary
bytes from the stack will be applied as the file mode.