-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Clang failed 100 tests on llvmorg-19.1.7 #122959
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
Can you please share the output for the test failures (from your build log)? |
Oh sorry, of course you'd need that. Reading up on grabbing the build log, but here are the failures. |
I reran the tests and piped STDOUT and STDERR to logs below. Well this is concerning... different results. But still over 100 failures. |
Did you set core.autocrlf=false for the checkout? I think the test failures are due to Windows newline issues. From https://clang.llvm.org/get_started.html:
|
Sigh. autocrlf must've resurrected when I installed a git gui. Thanks for the help, sorry for the waste. |
The windows binaries do not contain a target for wasm, so I decided to build it myself. This is a fresh install of Windows 11 using Visual Studio 2022. I compiled with CMake and Ninja as advised on https://clang.llvm.org/get_started.html
I ran
cmake -GNinja -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_PROJECTS=clang ..\llvm
then
ninja check
as advised on the "get started" page.This is on tag
llvmorg-19.1.7
commitcd708029e0b2869e80abe31ddb175f7c35361f90
Is this to be expected?
The text was updated successfully, but these errors were encountered: