Skip to content

Conversation

@charles-zablit
Copy link

@charles-zablit charles-zablit commented Oct 24, 2025

This patch makes check-lldb a disjoint set of check-lldb-swift meaning check-lldb runs the same set of tests as upstream.

@charles-zablit
Copy link
Author

@swift-ci please test

@charles-zablit charles-zablit force-pushed the charles-zablit/windows/lldb-only-run-swift-test-subset branch from ee40430 to c5a6610 Compare October 24, 2025 16:42
@charles-zablit
Copy link
Author

@swift-ci please test

@charles-zablit charles-zablit force-pushed the charles-zablit/windows/lldb-only-run-swift-test-subset branch from c5a6610 to 82a5cab Compare October 25, 2025 01:11
@charles-zablit charles-zablit changed the title [lldb] add support to filter lang/swift tests through an environment variable [lldb] make check-lldb a disjoint set of check-lldb-swift Oct 25, 2025
Copy link

@adrian-prantl adrian-prantl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this would be a good idea. The check-lldb target is meant to run all LLDB tests. We have other check-lldb-* targets and all of them are subsets of check-lldb, for example check-lldb-api, and check-lldb-shell. If we restricted check-lldb to only run non-swift tests that would break with this convention. That would be very confusing and also break tons of automation.

@adrian-prantl
Copy link

This convention isn't even LLDB-specific, all check-targets in LLVM behave like this (e.g., check-llvm-tools).

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.

3 participants