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

[5.9] Fix macOS build issues #419

Merged
merged 2 commits into from
May 15, 2023
Merged

[5.9] Fix macOS build issues #419

merged 2 commits into from
May 15, 2023

Conversation

MaxDesiatov
Copy link
Contributor

macOS build failures currently block PRs against release/5.9 branch. These were fixed in main, but still need to be cherry-picked for the release branch.

* Potential workaround for a CI issue

The macOS CI does not seem to work with Xcode 14.2 as superior, hitting

```
error: Error Domain=NSCocoaErrorDomain Code=4 "The file "swiftpm" doesn't exist." UserInfo={NSFilePath=/Users/ec2-user/jenkins/workspace/pr-swift-tools-support-core-macos/branch-main/swift-tools-support-core/Utilities/ci.xcworkspace/xcshareddata/swiftpm, NSUnderlyingError=0x600000a5a310 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}
```

I have a theory that this is triggered by us using a workspace that does not contain a resolved file, but that case works for me with SwiftPM 5.9 locally, so not sure.

* Use python 3

macOS 12 comes with updated python.
We only added the resolved file as a workaround, we may not need any concrete pins for that.
@MaxDesiatov
Copy link
Contributor Author

@swift-ci test

]
},
"version": 1
}
Copy link
Contributor

Choose a reason for hiding this comment

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

redundant?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We previously saw build failures without it, IIRC @neonichu already committed this on main?

Copy link
Contributor

Choose a reason for hiding this comment

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

oh yea, I was hoping we did not need this workaround. @neonichu ?

Copy link
Contributor

Choose a reason for hiding this comment

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

We do until we install a new Xcode that doesn't suffer from the problem. I haven't investigated which versions specifically hit the problem, but wasn't able to reproduce with the current release.

@tomerd tomerd merged commit e433d6d into release/5.9 May 15, 2023
@neonichu neonichu deleted the maxd/fix-macos-build branch May 15, 2023 23:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants