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
Bringing LLDB testing to swift-main-windows-toolchain seems important to monitor flakes. We filtered loads of flaky test in the bringup phase, but future changes may introduce new ones and it's critical to find them early. Otherwise they might clog the PR-testing bots.
Right now, it invokes swift\utils\build.ps1 directly and passes -Test swift,dispatch,xctest. We could either extend it to -Test swift,dispatch,xctest,lldb or drop the parameter entirely so that build.ps1 selects the default.
The text was updated successfully, but these errors were encountered:
The infrastructure for running a stable subset of LLDB tests on Windows is in place on mainline. We enabled it for PR-testing with #78844, but https://ci-external.swift.org/job/swift-main-windows-toolchain/ uses a custom (hardcoded) invocation that I cannot access.
Bringing LLDB testing to swift-main-windows-toolchain seems important to monitor flakes. We filtered loads of flaky test in the bringup phase, but future changes may introduce new ones and it's critical to find them early. Otherwise they might clog the PR-testing bots.
Right now, it invokes
swift\utils\build.ps1
directly and passes-Test swift,dispatch,xctest
. We could either extend it to-Test swift,dispatch,xctest,lldb
or drop the parameter entirely so thatbuild.ps1
selects the default.The text was updated successfully, but these errors were encountered: