Skip to content

[lldb] Split TestSwiftEmbeddedFrameVariable into two tests #8464

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 3 commits into from
Mar 25, 2024

Conversation

augusto2112
Copy link

[lldb] Split TestSwiftEmbeddedFrameVariable into two tests

Split TestSwiftEmbeddedFrameVariable into one test that runs with
instantiation of SwiftASTContext enabled, and one that runs with it
disabled.

The first one is useful because of the validation code that compares
TypeSystemSwiftTypeRef results with SwiftASTContext's.

The second one is useful to validate that the test is passing without
TypeSystemSwiftTypeRef falling back to SwiftASTContext.

For testing purposes, it's useful to have a setting to disable the
instantiation of SwiftASTContext, to ensure that
TypeSystemSwiftTypeRef, which by default falls back to it on failure, is
working independently.

This setting might also be useful for end users, as when debugging
a program that was built with a different compiler version versus what
is embedded in LLDB instantiation of Swift AST contexts would be moot.
Split TestSwiftEmbeddedFrameVariable into one test that runs with
instantiation of SwiftASTContext enabled, and one that runs with it
disabled.

The first one is useful because of the validation code that compares
TypeSystemSwiftTypeRef results with SwiftASTContext's.

The second one is useful to validate that the test is passing without
TypeSystemSwiftTypeRef falling back to SwiftASTContext.
@augusto2112
Copy link
Author

@swift-ci test

@augusto2112
Copy link
Author

@adrian-prantl there are 3 commits here, it's probably easier to check them separately

@adrian-prantl adrian-prantl merged commit dee589f into swiftlang:swift/release/6.0 Mar 25, 2024
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.

2 participants