-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Failing test suite with 0.4.0 release on MacOS #2421
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I have been getting this same failure on macOS 10.11, 10.13 and 10.14 against different versions of Xcode but haven't really investigated. |
Does the problem occur with master branch? |
yes. In fact I cannot recall ever having success runing full test on macOS. On linux, yes, I get good result. Off hand I'm thinking why does it work with CI builds? Primary diff is CI uses gcc8 to build zig's LLVM toolchain, I'm using Xcode-clang. If memory serves custom-clang also gave me same failure. |
Hmm. Unfortunately it works on my fully updated 10.14.4 macOS laptop as well so I cannot reproduce the issue. I need some help figuring out what's different about our systems. I build with Homebrew and the default system compiler. |
I will note the assertion is in LLD, the linker, which is known to be problematic for the macOS target and one of the reasons for #1535. |
Yes:
|
ok I've reduced it down to how Zig is built but have yet to find out why TEST FAILURE
TEST SUCCESS
|
@andrewrk it sounds like our setups are very similar. Same OS version, and I also build with Homebrew. I used the exact directions from the README:
I'd be happy to dig in deeper to find differences between our two configurations. |
@mikdusan I can explain that one: |
This looks to be a bug in lld. What's happening is the |
WIth Zig 0.4.0 built from source on macOS 10.14.4 (Mojave), I get the following error when running
bin/zig build --build-file ../build.zig test -Dskip-release
:Is this a known failure, or a possible problem with my setup? There are 5,718 passing tests (counted by their printing "...OK").
The text was updated successfully, but these errors were encountered: