Skip to content

Revert " Infer object format when it can't be determined from a triple's successfully parsed environment" #203

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

Merged
merged 1 commit into from
Aug 11, 2020

Conversation

owenv
Copy link
Contributor

@owenv owenv commented Aug 11, 2020

Reverts #201

Linux CI builds with this change are failing with "unableToFind(tool: "swift-autolink-extract")" during SMP tests. I've been unable to find the cause, so reverting for now.

@owenv
Copy link
Contributor Author

owenv commented Aug 11, 2020

@swift-ci test

Copy link
Member

@DougGregor DougGregor left a comment

Choose a reason for hiding this comment

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

Thanks for the quick revert! Not sure how this got through swift-driver CI but failed in Swift CI.

@DougGregor DougGregor merged commit 70864a4 into master Aug 11, 2020
@DougGregor DougGregor deleted the revert-201-object-format-fix branch August 11, 2020 14:34
@owenv
Copy link
Contributor Author

owenv commented Aug 11, 2020

@DougGregor yeah, I'm pretty confused as to what happened here, I'll need to investigate this more before reapplying. Thanks for the approval!

@artemcm
Copy link
Contributor

artemcm commented Aug 11, 2020

Thanks for the quick revert! Not sure how this got through swift-driver CI but failed in Swift CI.

Swift-driver CI tested against a toolchain that did not yet contain the change that would expose this failure. Also, the test that failed is a SwiftPM test, and I don't think those run in swift-driver CI at all. As SwiftPM and swift-driver get friendlier, perhaps we should also run SwiftPM tests with the integrated driver enabled as a part of swift-driver CI. It will add some overhead to our lightning-fast CI, but it will probably be worth it.

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.

3 participants