-
Notifications
You must be signed in to change notification settings - Fork 85
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
Attachments! #770
Attachments! #770
Conversation
4570404
to
fd7e89d
Compare
@swift-ci test |
1 similar comment
@swift-ci test |
If there is no |
We could also try to default to some benign location like /tmp, maybe. |
6b6d78a
to
510f445
Compare
@swift-ci test |
510f445
to
7da28f0
Compare
@swift-ci test |
02b30c1
to
097944b
Compare
@swift-ci test |
@swift-ci test Windows |
@swift-ci test |
ad35d3e
to
ed14512
Compare
@swift-ci test |
@swift-ci test |
@swift-ci test Windows |
@swift-ci test |
@swift-ci test Linux |
@swift-ci test macOS |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very cool! Took a deep look and left many comments/questions
@swift-ci test |
@swift-ci test Windows |
@swift-ci test |
@swift-ci test |
This reverts commit bb19b2a.
Work in progress patch to support swift-testing attachments. Currently prints the attachments out as a report at the end of a test run. In order to leverage them we need to set the --attachment-path, which is not available on the command line so we add a configuration json file. There is still more work to do to allow the user to specify their own attachment path on a per workspace basis. This will currently only work with swiftlang/swift-testing#770 as it isn't merged yet.
Work in progress patch to support swift-testing attachments. Currently prints the attachments out as a report at the end of a test run. In order to leverage them we need to set the --attachment-path, which is not available on the command line so we add a configuration json file. There is still more work to do to allow the user to specify their own attachment path on a per workspace basis. This will currently only work with swiftlang/swift-testing#770 as it isn't merged yet.
This PR introduces a new experimental feature, attachments. With this feature, you can "attach" values that conform to a new
Test.Attachable
protocol to a test. With the right command-line incantation (TBD), Swift Testing will automatically write attachments to disk for you.Note
This PR does not teach Xcode or VS Code how to handle attachments produced by
Swift Testing, nor does it add the necessary command-line arguments to the
swift test
command-line tool.This PR is one of a series that I'll be posting to build out this feature.
As always, keep in mind that symbols marked
@_spi(Experimental)
are subject to change or removal without notice.Resolves #714.
Resolves rdar://88648735.
Checklist: