Add python-lsp-server to downstream tests #639
+31
−0
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
Author
|
All checks are passing. Thanks for the review - happy to make any requested changes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR adds python-lsp-server as a downstream project to validate pluggy compatibility.
The downstream script installs the local pluggy worktree and runs the python-lsp-server test suite. Some plugin tests depend on optional third-party dependencies (for example, rope, flake8, pycodestyle) and may fail during collection. These failures are allowed to avoid gating CI, while still providing useful downstream signal.
This follows the existing downstream testing pattern used in the repository.
Closes #465