-
Notifications
You must be signed in to change notification settings - Fork 10.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[build.ps1] Enable LLDB tests in Windows builds #76894
base: main
Are you sure you want to change the base?
Conversation
This is a preview. We need to land swiftlang/llvm-project#9370 first. |
@compnerd This should be ready for testing with the companion PR linked above. Do we need to land that or can we ask the CI to checkout llvm-project from that PR instead of the original |
Please test with following PRs: @swift-ci please test windows platform |
Oh wow, that works indeed! And sorry, it was easy to confuse. We need the latest linked PR. The other one was merged in the meantime :) But not too bad, I anyway had to patch @compnerd I checked locally and I think that the following will work:
|
Please test with following PRs: @swift-ci please test windows platform |
Great, thanks. Good news is that
Edit: We can just download and install it like we do for Python, WiX, FlexBison, etc. |
Please test with following PRs: @swift-ci please test windows platform |
The build failed with the following error in build step
This doesn't appear to be related to my changes. Is it due to the merge conflict in |
Please test with following PRs: @swift-ci please test |
Great, tests are running!
SwiftREPL failures (28) will be fixed with swiftlang/llvm-project#9416, the others I will investigate today. |
In these NativePDB tests, a line breakpoint is set and it gets resolved to a location that seems right, but at startup time we add another location and that fails the test. This might be an actual bug:
The tests in 25f5eca should be fixed and they pass reliably on my machine, but they failed in the CI test run. Let's see if they XPASS next time, because the companion PR in llvm-project now has the SDKROOT patch: swiftlang/llvm-project@62b9626 Otherwise we might be missing a cherry-pick. And for the record: The following test failed but the detailed report is lacking in the log! 🤷♂️ This is the only unreasonable difference to the log from the companion PR.
|
Please test with following PRs: @swift-ci please test |
SwiftREPL tests keep failing:
This means that the dummy executable for the REPL didn't load. It usually happens if it lacks a runtime dependency like swiftCore: https://github.com/swiftlang/llvm-project/blob/stable/20230725/lldb/tools/repl/swift/main.c#L66 |
Otherwise only
This looks very similar to the problem we saw in the NativePDB tests last time. |
Please test with following PRs: @swift-ci please test |
Please test with following PRs: @swift-ci please test |
The builds failed with compile errors that indicate a LLVM version mismatch. I guess we have to build against |
Can we run again with this PR please? This time we should reach the tests. |
Please test with following PRs: @swift-ci please test |
@compnerd Thanks for your feedback.
|
No unexpected failures or passes. This should have been the first successful run:
But still |
Please test with following PRs: @swift-ci please test windows platform |
Finally, we have a successful run!
Runtime impact on the CI pipeline was 5min: 3m10s for running the actual tests and ~2min for building LLDB test dependencies. Timing of the testing stage compared to the two surrounding successful builds:
|
8e7e50d
to
e99b3ec
Compare
Please test with following PRs: @swift-ci please test |
Build failed for an unrelated reason. Didn't reach the test stage. |
Please test with following PRs: @swift-ci please test windows platform |
Please test with following PRs: @swift-ci please test Windows platform |
Tests finished successfully. Again no falkes, same results as last run, same timing:
|
e99b3ec
to
44099ab
Compare
Please test with following PRs: @swift-ci please test Windows platform |
Please test with following PRs: @swift-ci please test |
44099ab
to
ef2c0af
Compare
Rebase and fix conflicts after #77948 |
Please test with following PRs: @swift-ci please test |
The Windows build failed due to one test in LLDB:
Apparently, we got an empty list from I never saw this test failing and I don't see a recent change, that might have caused it. Needs investigation. I will file an issue and disable it for the time being. |
Please test with following PRs: @swift-ci please test |
LLDB tests finished successfully. No falkes. The build failed in the subsequent |
cd81c57
to
0349f3e
Compare
@swift-ci please test |
The Windows bot didn't run, let's try again. @swift-ci please test Windows platform |
Two flakes: first new, second known (we'd have to adjust the filter here, because it doesn't work for individual unittests)
|
@swift-ci please test Windows platform |
Tests passed. Let's see if this is reproducible. @swift-ci please test Windows platform |
The build failed with an unrelated error in LLDB:
|
Tests passed. Let's see if this is reproducible. @swift-ci please test Windows platform |
This PR adds handling for the
-Test lldb
option, which allows to enable the LLDB test suite on Windows builds of the swift toolchain, fixing swiftlang/llvm-project#9141While we still see a lot of test failures, it's time to give the CI a try. Once we get to a stable subset of tests that pass, we can iterate to enable the remaining ones and increase coverage.
The PR adds a local Windows-specific mechanism to mark bulks of tests as XFAIL or SKIPPED. These tests are listed in file
utils/windows-llvm-lit-test-overrides.txt
. The goal is to get it down to a low number and remove the mechanism and file eventually.