-
Notifications
You must be signed in to change notification settings - Fork 13.5k
Test clang-tools-extra/test/clang-doc/basic-project.test failing when built using non-ninja generator #97507
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
There still are some failing builds caused by https://lab.llvm.org/buildbot/#/builders/35/builds/1367 Can you look into it? Thanks! (Disabling the test might be an acceptable short term solution) |
I disabled the test in 88549cf |
We have an internal job which attempts to build the LLVM tree using the Visual Studio 2019 builder configuration (non-ninja) and it recently started hitting a test failure of clang-tools-extra/test/clang-doc/basic-project.test which I bisected back to when f14ad74 (#96358) was committed. The problem is that the change hard-codes how to find the dependent assets as
../share/clang-doc
. This is fine in ninja builds, but fails with the Visual Studio generator because the configuration name is part of the path.For example, in a ninja build, the value of AssetsPath is (correctly)
C:\Dev\git\merge\build\bin\..\share\clang-doc\index.js
. But when using a Visual Studio generator, the value of AssetsPath is nowC:\Dev\git\merge\build\Debug\bin\..\share\clang-doc\index.js
which refers to a non-existent directory. In this particular case, it requires an extra..
in the path to find the expected directory.Lit test output:
The text was updated successfully, but these errors were encountered: