Skip to content

[6.0.1] Guard parse_version #503

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

Conversation

shahmishal
Copy link
Member

The most recent versions of parse_version throw an exception if the version is empty. The version passed in is only set on Darwin (call to mac_ver(), so it's causing test failures on newer versions of Linux since the test suite can't even start.

Now, the only reason for the version parse is because the tests are looking at whether or not concurrency is available on the OS. This is only a limitation if we're working with Darwin. Swift 5.10 on Windows and Linux always have a Swift 5.10 concurrency runtime, so we don't even need to check for a version.

rdar://128502662
(cherry picked from commit 65e6ecd) (cherry picked from commit f26bc21)

The most recent versions of `parse_version` throw an exception if the
version is empty. The version passed in is only set on Darwin (call to
`mac_ver()`, so it's causing test failures on newer versions of Linux
since the test suite can't even start.

Now, the only reason for the version parse is because the tests are
looking at whether or not concurrency is available on the OS. This is
only a limitation if we're working with Darwin. Swift 5.10 on Windows
and Linux always have a Swift 5.10 concurrency runtime, so we don't even
need to check for a version.

rdar://128502662
(cherry picked from commit 65e6ecd)
(cherry picked from commit f26bc21)
@shahmishal
Copy link
Member Author

@swift-ci test

@shahmishal shahmishal merged commit 090b62c into release/6.0.1 Sep 5, 2024
2 checks passed
@shahmishal shahmishal deleted the cherry-pick-6.0.1-f26bc2138b8cd8f73317d7b7c019bf016ca5bc33 branch September 5, 2024 04:49
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