Closed dyung closed 1 month ago
There still are some failing builds caused by basic-project.test
https://lab.llvm.org/buildbot/#/builders/35/builds/1367 https://github.com/llvm/llvm-project/pull/100576 https://buildkite.com/llvm-project/github-pull-requests/builds/85141 https://buildkite.com/llvm-project/github-pull-requests/builds/85249 https://github.com/search?q=repo%3Allvm%2Fllvm-project+basic-project.test&type=pullrequests
Can you look into it? Thanks! (Disabling the test might be an acceptable short term solution)
I disabled the test in 88549cf47cafc4c4a6042393ee07fc2dc20566cc
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 f14ad74478494cbd9d23af841d6f6b2808afda71 (#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: