LLDB fails to hit process launch breakpoint in SwiftCI

[weliveindetail]

This failed for no obvious reason. The test isn't new and it is unmodified from upstream LLDB:
https://github.com/swiftlang/llvm-project/blob/stable/20240723/lldb/test/Shell/Commands/command-process-launch-user-entry.test

It works there and it works for me locally in swiftlang LLDB. Best guess so far is a difference in %clang_host -g.

******************** TEST 'lldb-shell :: Commands/command-process-launch-user-entry.test' FAILED ********************
Exit Code: 1

Command Output (stdout):
--
# RUN: at line 1
t:\5\bin\clang.exe --target=specify-a-target-or-use-a-_host-substitution --target=x86_64-unknown-windows-msvc -fmodules-cache-path=T:/5/lldb-test-build.noindex/module-cache-clang\lldb-shell -g C:\Users\swift-ci\jenkins\workspace\swift-PR-windows\llvm-project\lldb\test\Shell\Commands/Inputs/main.c -o T:\5\tools\lldb\test\Shell\Commands\Output\command-process-launch-user-entry.test.tmp
# executed command: 't:\5\bin\clang.exe' --target=specify-a-target-or-use-a-_host-substitution --target=x86_64-unknown-windows-msvc '-fmodules-cache-path=T:/5/lldb-test-build.noindex/module-cache-clang\lldb-shell' -g 'C:\Users\swift-ci\jenkins\workspace\swift-PR-windows\llvm-project\lldb\test\Shell\Commands/Inputs/main.c' -o 'T:\5\tools\lldb\test\Shell\Commands\Output\command-process-launch-user-entry.test.tmp'
# .---command stderr------------
# | clang: warning: argument unused during compilation: '-fmodules-cache-path=T:/5/lldb-test-build.noindex/module-cache-clang\lldb-shell' [-Wunused-command-line-argument]
# `-----------------------------
# RUN: at line 2
t:\5\bin\lldb.exe --no-lldbinit -S T:/5/tools/lldb\test\Shell\lit-lldb-init-quiet T:\5\tools\lldb\test\Shell\Commands\Output\command-process-launch-user-entry.test.tmp -s C:\Users\swift-ci\jenkins\workspace\swift-PR-windows\llvm-project\lldb\test\Shell\Commands\command-process-launch-user-entry.test -o exit | t:\5\bin\filecheck.exe C:\Users\swift-ci\jenkins\workspace\swift-PR-windows\llvm-project\lldb\test\Shell\Commands\command-process-launch-user-entry.test
# executed command: 't:\5\bin\lldb.exe' --no-lldbinit -S 'T:/5/tools/lldb\test\Shell\lit-lldb-init-quiet' 'T:\5\tools\lldb\test\Shell\Commands\Output\command-process-launch-user-entry.test.tmp' -s 'C:\Users\swift-ci\jenkins\workspace\swift-PR-windows\llvm-project\lldb\test\Shell\Commands\command-process-launch-user-entry.test' -o exit
# note: command had no output on stdout or stderr
# executed command: 't:\5\bin\filecheck.exe' 'C:\Users\swift-ci\jenkins\workspace\swift-PR-windows\llvm-project\lldb\test\Shell\Commands\command-process-launch-user-entry.test'
# .---command stderr------------
# | C:\Users\swift-ci\jenkins\workspace\swift-PR-windows\llvm-project\lldb\test\Shell\Commands\command-process-launch-user-entry.test:6:10: error: CHECK: expected string not found in input
# | # CHECK: Process {{.*}} stopped
# |          ^
# | <stdin>:8:25: note: scanning from here
# | (lldb) process launch -m
# |                         ^
# | <stdin>:9:1: note: possible intended match here
# | Process 3720 launched: 'T:\5\tools\lldb\test\Shell\Commands\Output\command-process-launch-user-entry.test.tmp' (x86_64)
# | ^
# | 
# | Input file: <stdin>
# | Check file: C:\Users\swift-ci\jenkins\workspace\swift-PR-windows\llvm-project\lldb\test\Shell\Commands\command-process-launch-user-entry.test
# | 
# | -dump-input=help explains the following input dump.
# | 
# | Input was:
# | <<<<<<
# |            1: (lldb) command source -s 0 'T:/5/tools/lldb\test\Shell\lit-lldb-init-quiet' 
# |            2: Executing commands in 'T:\5\tools\lldb\test\Shell\lit-lldb-init-quiet'. 
# |            3: (lldb) command source -C --silent-run true lit-lldb-init 
# |            4: (lldb) target create "T:\\5\\tools\\lldb\\test\\Shell\\Commands\\Output\\command-process-launch-user-entry.test.tmp" 
# |            5: Current executable set to 'T:\5\tools\lldb\test\Shell\Commands\Output\command-process-launch-user-entry.test.tmp' (x86_64). 
# |            6: (lldb) command source -s 0 'C:\Users\swift-ci\jenkins\workspace\swift-PR-windows\llvm-project\lldb\test\Shell\Commands\command-process-launch-user-entry.test' 
# |            7: Executing commands in 'C:\Users\swift-ci\jenkins\workspace\swift-PR-windows\llvm-project\lldb\test\Shell\Commands\command-process-launch-user-entry.test'. 
# |            8: (lldb) process launch -m 
# | check:6'0                             X error: no match found
# |            9: Process 3720 launched: 'T:\5\tools\lldb\test\Shell\Commands\Output\command-process-launch-user-entry.test.tmp' (x86_64) 
# | check:6'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# | check:6'1     ?                                                                                                                        possible intended match
# |           10: Process 3720 exited with status = 0 (0x00000000) 
# | check:6'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# |           11: (lldb) exit 
# | check:6'0     ~~~~~~~~~~~~
# |           12: ==== LLDB swift-healthcheck log. === 
# | check:6'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# |           13: This file contains the configuration of LLDB's embedded Swift compiler to help diagnosing module import and search path issues. The swift-healthcheck command is meant to be run *after* an error has occurred. 
# | check:6'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# |           14: lldb version 19.1.4 
# | check:6'0     ~~~~~~~~~~~~~~~~~~~~
# |           15: Swift version 6.1-dev (LLVM 86de23d048565c5, Swift 093051f8abc31ec) 
# | check:6'0     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# | >>>>>>
# `-----------------------------
# error: command failed with exit status: 1