-
Notifications
You must be signed in to change notification settings - Fork 1.4k
mark a failing test on linux+swiftbuild as withKnownIssue (moduleDirectDeps2) #9150
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
Conversation
|
@swift-ci test |
|
@swift-ci test linux |
…ps2) This was previously marked as a known Issue before but got changed in another PR resulting in a PR merge race causing breakage.
2bbd5ca to
9186cd8
Compare
|
@swift-ci test |
|
@swift-ci test windows |
| } | ||
| } when: { | ||
| ProcessInfo.hostOperatingSystem == .windows && buildSystem == .swiftbuild | ||
| buildSystem == .swiftbuild |
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.
do we understand what started to cause this failure as the change that added support for module aliasing in SwiftBuild has passed on all platforms, except Windows due to known issues.
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.
yes, we need to fix SwiftBuild linker task to specify linked libraries correctly. This will be my next update soon
|
Merging to unblock PR testing |
needs to be investigated
rdar://160781783