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

Jump to bottom

[SR-8250] [Source Compat] Some projects failing with 'minimum Swift tools version' errors #50782

Closed
clackary opened this issue Jul 13, 2018 · 7 comments
Closed

[SR-8250] [Source Compat] Some projects failing with 'minimum Swift tools version' errors #50782

clackary opened this issue Jul 13, 2018 · 7 comments
Assignees
@clackary
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. source compatibility

Comments

@clackary
Copy link
Contributor

Previous ID SR-8250
Radar rdar://42160590
Original Reporter @clackary
Type Bug
Status Closed
Resolution Done
Additional Detail from JIRA
Votes 1
Component/s
Labels Bug, SourceCompatibility
Assignee @clackary
Priority Medium

md5: 4ee75ebda51df5ce606d27eaa4ab5bbc

relates to:

  • SR-8174 Update/remove 3.x configurations in source compatibility suite
  • SR-8234 [Source Compat] Some SwiftPM projects fail with: error: manifest parse error

Issue Description:

https://ci.swift.org/view/Source%20Compatibility/job/swift-master-source-compat-suite/2125/artifact/swift-source-compat-suite/

Errors all look like:

error: package at '/Users/buildnode/jenkins/workspace-private/swift-PR-source-compat-suite-test-macOS/project_cache/AsyncNinja' requires a minimum Swift tools version of 4.0.0 (currently 3.0.0)

 00:11:31 ========================================
 00:11:31 Failures:
 00:11:31 FAIL: AsyncNinja, 3.1, 91b80d, Swift Package
 00:11:31 FAIL: DNS, 3.1, 9e102e, Swift Package
 00:11:31 FAIL: Guitar, 3.1, f3135a, Swift Package
 00:11:31 FAIL: Guitar, 4.0, d88afd, Swift Package
 00:11:31 FAIL: Kronos, 4.0, 82126c, Swift Package
 00:11:31 FAIL: PinkyPromise, 3.0, a127ac, Swift Package
 00:11:31 FAIL: Serpent, 3.0, 16a3bf, Swift Package
 00:11:31 FAIL: Then, 3.1, daaea1, Swift Package
 00:11:31 FAIL: URBNJSONDecodableSPM, 3.1, 6dc998, Swift Package
 00:11:31 FAIL: mapper, 4.0, 45f572, Swift Package
 00:11:31 FAIL: mapper, 3.0, db431a, Swift Package
 00:11:31 ========================================
@clackary
Copy link
Contributor Author

@aciidb0mb3r Is this another package manager change?

@ankitspd
Copy link
Member

It's the diagnostic we talked about, but the underlying reason for failure is same.

@clackary
Copy link
Contributor Author

apple/swift-source-compat-suite#218

This PR should fix the builder.

@belkadan
Copy link
Contributor

This is done, right?

@clackary
Copy link
Contributor Author

Most of these projects are still xfailed for this. CI isn't failing anymore, but projects that haven't updated tools version recently are still going to hit this.

@clackary
Copy link
Contributor Author

Serpent and Then projects have been updated to a new hash.

The rest of the projects failing from this issue will require project-side updates, specifically to add // swift-tools-version:4.0 to Package.swift file.

I've notified project maintainers of this.

@clackary
Copy link
Contributor Author

Hashes have been updated to newer commits for most of these projects. A few haven't been updated in a long time, and have been removed from the suite.

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@clackary clackary

Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. source compatibility
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@belkadan @ankitspd @clackary