Zig Version
0.10.0-dev.670+e1a535360
Steps to Reproduce
This issue was noticed during a CI run of an unrelated Pull Request. I was not able to reproduce this issue locally. Furthermore, after force pushing a commit with the same contents verbatim, the segfault disappeared.
Expected Behavior
zig build test-std step in the CI passes.
Actual Behavior
The test step is aborted with a segfault.
The CI run log can be found here. I uploaded the full log to a GitHub Gist.
The segfault occurs here:
266/918 Thread.test "std-native-ReleaseSafe-bare-multi setName, getName"... OK
267/918 Thread.test "std-native-ReleaseSafe-bare-multi std.Thread"... OK
268/918 Thread.test "std-native-ReleaseSafe-bare-multi Thread.join"... OK
269/918 Thread.test "std-native-ReleaseSafe-bare-multi Thread.detach"... OK
270/918 Thread.test "std-native-ReleaseSafe-bare-multi Condition.signal"... OK
271/918 Thread.Mutex.test "std-native-ReleaseSafe-bare-multi basic usage"... Segmentation fault at address 0x7f87c8c02fb8
error: the following test command crashed:
/workspace/zig-cache/o/a39675fd908afe859ebfdcecc6d01cc0/test /workspace/_debug/staging/bin/zig
test...The following command exited with error code 1:
/workspace/_debug/staging/bin/zig test /workspace/lib/std/std.zig --test-name-prefix std-native-ReleaseSafe-bare-multi -OReleaseSafe --cache-dir /workspace/zig-cache --global-cache-dir /root/.cache/zig --name test -fno-single-threaded -I /workspace/test --zig-lib-dir /workspace/lib --enable-cache
error: the following build command failed with exit code 1:
/workspace/zig-cache/o/6cd3d08a5f08b8d3d8f602a3312dafe3/build /workspace/_debug/staging/bin/zig /workspace /workspace/zig-cache /root/.cache/zig test-std -fqemu -fwasmtime
Zig Version
0.10.0-dev.670+e1a535360
Steps to Reproduce
This issue was noticed during a CI run of an unrelated Pull Request. I was not able to reproduce this issue locally. Furthermore, after force pushing a commit with the same contents verbatim, the segfault disappeared.
Expected Behavior
zig build test-stdstep in the CI passes.Actual Behavior
The test step is aborted with a segfault.
The CI run log can be found here. I uploaded the full log to a GitHub Gist.
The segfault occurs here: