-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Driver: do not generate a dSYM bundle for static archives #37526
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
@swift-ci test |
Build failed |
Build failed |
84e4937
to
3dfbcfa
Compare
@swift-ci please test |
Build failed |
Build failed |
@swift-ci please test Windows platform |
@swift-ci please test |
When building a static library with debug information, do not create a dSYM generation job as it cannot be executed on a non-image target. This is important for the case where the single invocation is both the compile and link job. This was detected in conjunction with @gottesmm.
@swift-ci please test Windows platform |
@swift-ci please test macOS |
@swift-ci please test Linux |
Windows failures are related to concurrency. I don't think it should stop this from going in. |
The Windows failures are not related (tests are coming online due to LLVM changes) |
When building a static library with debug information, do not create a
dSYM generation job as it cannot be executed on a non-image target.
This is important for the case where the single invocation is both the
compile and link job.
This was detected in conjunction with @gottesmm
Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.
Resolves SR-NNNN.