-
Notifications
You must be signed in to change notification settings - Fork 10.5k
SILGen Tests #16347
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
SILGen Tests #16347
Conversation
@swift-ci please test |
Build failed |
Build failed |
@swift-ci please test |
@swift-ci please test |
Build failed |
Build failed |
CC: @aschwaighofer @jrose-apple suggestions as to why there are differences between the platforms here? |
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.
My guess is always that you ended up using the mock SDK with the real overlays. Don't forget that the fake overlays have to be built and put into the search path!
@@ -0,0 +1,12 @@ | |||
@interface NSEntityDescription |
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.
Probably best to import Foundation and inherit from NSObject too. Things unexpectedly being base classes does weird things in Objective-C.
@swift-ci please smoke test macOS platform |
@swift-ci please smoke test macOS platform |
Darwin Failing Tests: Swift(macosx-x86_64).SILGen.without_actually_escaping_block.swift |
@swift-ci please smoke test macOS platform |
@swift-ci please smoke test macOS platform |
@swift-ci please smoke test macOS platform |
@swift-ci please smoke test |
When trying to figure out errors from an import failure, the nullability completeness warnings would clutter the output making it difficult to identify the errors. Sprinkle the declaarations with `_Null_unspecified` to maintain the current nullability semantics and silence the warnings. NFC.
This module was specified in the IDE and SILGen testing module maps, which causes a failure. Remove the duplicated declaration in the SILGen inputs and use IDE's definition.
The local bridging headers needed two new definitions: - NSErrorDomain - NS_OPTIONS These can be used by the SILGen tests to build against a stubbed Foundation rather than requiring the host to provide it.
One of the SILGen tests uses CoreData. Provide a stubbed out definition sufficient for the tests.
Enable a number of SILGen tests to run on all targets. This improves coverage on non-Darwin targets.
@swift-ci please smoke test |
Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.
Resolves SR-NNNN.