DavidSpickett wrote: https://github.com/llvm/llvm-project/pull/94325 will get us past the compiler error.
Some things I noticed testing that: * There is an lld installed on the machine but it's in a path with spaces so lit can't run it. Generally we'd build lld along with lldb and use that in the test suite, when I did that it worked. * LLDB is not being built with scripting enabled, so a lot of the API tests won't be run. For a completed run I got these results: https://buildkite.com/llvm-project/github-pull-requests/builds/69540#018fe2bf-1cf8-49f7-a680-f44bf01dbaec ``` Failed Tests (4): lldb-shell :: Process/Windows/process_load.cpp lldb-shell :: SymbolFile/DWARF/x86/dwp-separate-debug-file.cpp lldb-shell :: Target/dependent-modules-nodupe-windows.test lldb-shell :: Unwind/windows-unaligned-x86_64.test Testing Time: 38.08s Total Discovered Tests: 2901 Unsupported : 1337 (46.09%) Passed : 1543 (53.19%) Expectedly Failed: 17 (0.59%) Failed : 4 (0.14%) ``` `dwp-separate-debug-file.cpp` I have fixed, it needed to require Python. `windows-unaligned-x86_64.test` just fails to breakpoint, I don't know why. The rest are something to do with `kernel32.dll` either not being able to load it, or it not showing up in the image list for a debugged program. I have never seen that before but it does sound like something a security setting might effect. https://github.com/llvm/llvm-project/pull/94208 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
