Skip to content

Remove invalid versions #613

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 3 commits into from
Oct 28, 2021
Merged

Conversation

xedin
Copy link
Contributor

@xedin xedin commented Oct 27, 2021

  • Fix a couple of projects that switched to use main branch
  • Fix build_swift_package to specify expected -swift-version (it was defaulted before)
  • Adjust projects.json to use only supported Swift versions

@xedin
Copy link
Contributor Author

xedin commented Oct 27, 2021

@swift-ci please test

@xedin xedin force-pushed the remove-invalid-versions branch from 20b366a to 847f3ca Compare October 28, 2021 00:39
@xedin
Copy link
Contributor Author

xedin commented Oct 28, 2021

@swift-ci please test

@xedin
Copy link
Contributor Author

xedin commented Oct 28, 2021

Fixed one more 5.1 spot :(

@xedin xedin merged commit 6e8f7aa into swiftlang:main Oct 28, 2021
@@ -2346,14 +2274,6 @@
{
"version": "4.2",
"commit": "2fe5b325a8a54e77c545b2f511213420da133b8c"
},
Copy link
Member

Choose a reason for hiding this comment

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

Is it intended that we are only left with the 4.2 branch for Result instead of the 5.1 branch? I think we are now testing compiler main against the 4.2 branch of Result (which is causing a stress tester failure because offsets have moved around).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, all of the packages where just defaulting to what either 4 or 5 before and once I added -swift-version support all of the ones I removed started failing with unavailable methods and such, if we want to add swift-version 5 back, need to figure out the commit for 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