Skip to content

Conversation

@drodriguez
Copy link
Contributor

The test started working in the last week, for unknown reasons.

Remove the XFAIL line, but keep the infra for detecting the MSVC version
for the tests. It might be useful later.

If the test starts failing again, and nobody has any idea why, the best
path forward might be marking it as UNSUPPORTED.

The test started working in the last week, for unknown reasons.

Remove the XFAIL line, but keep the infra for detecting the MSVC version
for the tests. It might be useful later.

If the test starts failing again, and nobody has any idea why, the best
path forward might be marking it as UNSUPPORTED.
@drodriguez drodriguez requested a review from compnerd November 7, 2020 23:59
@drodriguez
Copy link
Contributor Author

@swift-ci please smoke test

Copy link
Member

@compnerd compnerd left a comment

Choose a reason for hiding this comment

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

Thanks!

@drodriguez drodriguez merged commit 0aa41bc into swiftlang:main Nov 8, 2020
@drodriguez drodriguez deleted the windows-un-xfail-msvc-2017-test branch November 8, 2020 02:32
drodriguez added a commit to drodriguez/swift that referenced this pull request Nov 10, 2020
The test is very flaky. It works and stops working randomly for no
apparent reason. To avoid future problems, and since VS2019 keeps
working without these problems, mark the tests as unsupported to avoid
the noise.

See also swiftlang#34143 and swiftlang#34625.
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