Skip to content

SwiftDriverTests: conditionalise exitStatus #884

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 1 commit into from
Oct 25, 2021

Conversation

compnerd
Copy link
Member

Windows does not have a concept of signals. As such, we cannot have an
exit status of signalled. This allows the test suite to build, though
this test will currently fail.

Windows does not have a concept of signals.  As such, we cannot have an
exit status of `signalled`.  This allows the test suite to build, though
this test will currently fail.
@compnerd
Copy link
Member Author

@swift-ci please test

@cltnschlosser
Copy link
Contributor

Does it make sense to just skip the whole test? testSignalledBatchMessages

@compnerd
Copy link
Member Author

I guess the question is, what is the intent of the test? Does it care about signalling or does it care about the fact that it can process invalid termination? Because ultimately signals are just a proxy for the fact that there was an abnormal termination, which does does have a concept of, just not in the form of signals.

@compnerd compnerd merged commit ffb4eb7 into swiftlang:main Oct 25, 2021
@compnerd compnerd deleted the signalling branch October 25, 2021 20:37
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