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

Update resolved file #417

Merged
merged 1 commit into from
Apr 25, 2023
Merged

Conversation

neonichu
Copy link
Contributor

We only added the resolved file as a workaround, we may not need any concrete pins for that.

We only added the resolved file as a workaround, we may not need any concrete pins for that.
@neonichu
Copy link
Contributor Author

@swift-ci please test

@tomerd tomerd changed the title Try empty resolved file Update resolved file Apr 25, 2023
@tomerd
Copy link
Contributor

tomerd commented Apr 25, 2023

ideally we delete the file instead

@neonichu
Copy link
Contributor Author

ideally we delete the file instead

Agreed in principle, we needed to add it recently in #404, presumably because of an issue in the installed Xcode.

@neonichu neonichu merged commit adefcdf into swiftlang:main Apr 25, 2023
@neonichu neonichu deleted the try-empty-resolved-file branch April 25, 2023 19:30
MaxDesiatov pushed a commit that referenced this pull request May 11, 2023
We only added the resolved file as a workaround, we may not need any concrete pins for that.
tomerd pushed a commit that referenced this pull request May 15, 2023
* Potential workaround for a CI issue (#404)

* 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.

* Try empty resolved file (#417)

We only added the resolved file as a workaround, we may not need any concrete pins for that.

---------

Co-authored-by: Boris Bügling <bbuegling@apple.com>
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.

2 participants