[6.2] Run only Swift subset of LLDB tests for Linux Smoketest preset #80943
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Addresses rdar://149562580 (cherry picked from commit 60150e7)
|
@swift-ci please smoke test Linux |
|
@swift-ci please test |
|
Please test with following pull request: @swift-ci please smoke test Linux |
|
Discussed with Mishal offline, this is not useful on 6.2 since we are requiring full tests here. |
edymtt
deleted the
emiotto/only-run-swift-subset-of-lldb-tests-on-linux-smoketest-6.2
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addresses rdar://149562580
(cherry picked from commit 60150e7)
Update the Linux Smoketest preset to only run the LLDB tests that apply to Swift.
buildbot_linux,smoketestpresetrdar://149562580
Run only Swift subset of LLDB tests for Linux Smoketest preset #80916
Low -- this flag is already used by other presets used in CI, and in the worst case we will keep running too many tests but not failing
Linux PR testing in the original PR and manual inspection of the resulting log to ensure we indeed run less LLDB tests.
@adrian-prantl