Skip to content

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Sep 18, 2025
Merged

mark a failing test on linux+swiftbuild as withKnownIssue (moduleDirectDeps2) #9150

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Tests/FunctionalTests/ModuleAliasingFixtureTests.swift
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -122,7 +122,7 @@ struct ModuleAliasingFixtureTests {
)
}
} when: {
ProcessInfo.hostOperatingSystem == .windows && buildSystem == .swiftbuild
buildSystem == .swiftbuild
Copy link
Contributor

@bkhouri bkhouri Sep 18, 2025 •
edited
Loading

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.

Copy link
Contributor Author

@daveinglis daveinglis Sep 18, 2025

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

}
}

Expand Down