-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[test] rth: Use dynamic linking to properly test backwards-deployment #14447
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 Please test |
Would you elaborate a bit on how this properly tests resilience over the previous method? |
The old version of Swift doesn't actually try to weak-link anything that wasn't imported from Clang, so I don't have a test case yet. But it's one of the things I'm working on that I took over from Slava, rdar://problem/29888071. Anyway, the purpose of resilience is to allow changing out a library after a client has been built, and that includes linking. This is closer to what actually happens when backwards-deploying an app on an older OS, or updating an OS out from under existing apps. |
"It wasn't wrong but it could be more right." |
Thanks! LGTM. |
Build failed |
Build failed |
8f34506
to
eb2c6e6
Compare
@swift-ci Please test |
Build failed |
eb2c6e6
to
0a15c75
Compare
@swift-ci Please test |
Build failed |
Build failed |
@swift-ci Please test macOS |
Build failed |
0a15c75
to
b4cf5fd
Compare
@swift-ci Please test |
Build failed |
Build failed |
I cannot catch a break with this rewrite. Guess I need to stop cutting corners. :-/ |
b4cf5fd
to
424c3be
Compare
Build failed |
Build failed |
LGTM. |
Dang it, Linux. |
The added test worked before as well; it's to make sure I didn't break the existing behavior.
424c3be
to
71c4156
Compare
@swift-ci Please test |
Build failed |
Build failed |
The added test worked before as well; it's to make sure I didn't break the existing behavior.