Skip to content
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

Disable lld Mach-O tests in the Swift LLVM fork #8511

Merged
merged 2 commits into from
Apr 3, 2024

Conversation

kubamracek
Copy link

The Swift LLVM fork disabled linking for Darwin in lld, see #8119. To make "ninja check-all" pass, we need to disable running the Mach-O tests.

@kubamracek
Copy link
Author

@swift-ci please test

1 similar comment
@kubamracek
Copy link
Author

@swift-ci please test

@rintaro
Copy link
Member

rintaro commented Apr 2, 2024

@swift-ci Please test Linux

@rintaro
Copy link
Member

rintaro commented Apr 2, 2024

@swift-ci Please test macOS

@rintaro
Copy link
Member

rintaro commented Apr 2, 2024

@swift-ci Please test Windows

Copy link

@al45tair al45tair left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure about the gc-dwarf-eh.s change. The change to lld/test/MachO/lit.local.cfg is fine.

Comment on lines 3 to 7
# Swift LLVM fork downstream change start
# Disable failing test
# XFAIL: *
# Swift LLVM fork downstream change end

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are we disabling the gc-dwarf-eh.s test for COFF here? (That isn't anything to do with Mach-O).

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed this change

@kubamracek
Copy link
Author

@swift-ci please test

@kubamracek
Copy link
Author

@swift-ci Please test Windows

@kubamracek kubamracek merged commit e5b62af into swiftlang:stable/20230725 Apr 3, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants