-
Notifications
You must be signed in to change notification settings - Fork 10.6k
[Windows] Stop using multiroot data file #83693
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
[Windows] Stop using multiroot data file #83693
Conversation
…tion on Windows" This reverts commit 61f833c.
|
@swift-ci Please smoke test |
compnerd
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am unsure that this is the true cause of that silent crash. This is something that @bnbarham and I have been trying to isolate (it is CI only). I wonder if we should do a more judicious revert of just the parameter. This is unfortunate, but if this is causing it to reproduce more often, I am curious if this might help us narrow down what is going on.
|
Looks like it somehow happens for swift-foundation now, rather than just the swift-corelibs-foundation that we've been seeing 🤔 I very much doubt this is the actual cause, but I have no explanation of how it suddenly causes it in swift-foundation. Interestingly not all of them have And merging to unblock CI, since I do see a bunch of failed builds since that PR was merged :(. |
…ionTestConfiguration` is set to `debug` This was discussed in swiftlang#80122 (comment) but got reverted by swiftlang#83693. Re-apply the fix.
|
That’s interesting. Maybe the difference is whether we test in debug or release configuration (swift-foundation currently tests in release while swift-corelibs-foundation tests in debug due to an incorrect merge conflict resolution that I described in #80122 (comment). Trying to line the configurations up in #83720, maybe that can give some insights into the root cause. |
|
Oh I only saw this after I commented on the other PR. Yeah, that is the current assumption (which your PR looks to have confirmed) 👍 |
I have seen testing of swift-foundation fail without an error message (eg. https://ci-external.swift.org/job/sourcekit-lsp-PR-windows/3152/, build log attached to this PR), which likely started occurring after #80122. Revert that change to unbreak CI.
sourcekit-lsp-PR-windows-3152.txt