You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running tests for LLDB in CI, the ones for SwiftREPL fail with an error like this:
$ "t:\5\bin\lldb.exe" "--no-lldbinit" "-S" "T:/5/tools/lldb\test\Shell\lit-lldb-init-quiet" "--repl"
error: failed to stop process at REPL breakpoint
This means that the dummy executable repl_swift.exe didn't reach its main loop, which happens if it lacks runtime dependencies. repl_swift.exe loads the two external binaries at startup: swiftCore.dll and swiftrt.obj.
These binaries are produced in the Swift runtime build step. They don't exist yet, when repl_swift.exe is built, but only at the time when the LLDB build directory is reconfigured for testing. We started to:
When running tests for LLDB in CI, the ones for SwiftREPL fail with an error like this:
This means that the dummy executable
repl_swift.exe
didn't reach its main loop, which happens if it lacks runtime dependencies.repl_swift.exe
loads the two external binaries at startup: swiftCore.dll and swiftrt.obj.These binaries are produced in the Swift runtime build step. They don't exist yet, when
repl_swift.exe
is built, but only at the time when the LLDB build directory is reconfigured for testing. We started to:Furthermore, LLDB issues a manual lookup for the
SDKROOT
environment variable in lldb/source/Host/windows/HostInfoWindowsSwift.cpp when running in repl mode. If it fails, then we get the following error from SwiftASTContext::CreateInstance():We started to forward
SDKROOT
from the system's environment to LLDB Shell tests with 42e7e20With these preparations in place, the following tests are expected to pass:
As of today, this works locally on a development machine, but not when running tests in CI.
The text was updated successfully, but these errors were encountered: