-
Notifications
You must be signed in to change notification settings - Fork 439
test: add marker for running tests in subprocess (backport #3383) #4403
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
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
The `subprocess` pytest marker can be used to run arbitrary Python code in a Python subprocess. This is meant to replace the existing fixture to allow actual Python code to be written and tested, instead of using literal strings. ## Checklist - [ ] Added to the correct milestone. - [ ] Tests provided or description of manual testing performed is included in the code or PR. - [ ] Library documentation is updated. - [ ] [Corp site](https://github.com/DataDog/documentation/) documentation is updated (link to the PR). (cherry picked from commit c437ad2) # Conflicts: # tests/contrib/httpx/test_httpx.py # tests/integration/test_integration.py # tests/tracer/test_encoders.py
4 tasks
b8d98ef
to
5423fdc
Compare
5423fdc
to
a337e1b
Compare
@mergify[bot] this pull request is now in conflict 😩 |
P403n1x87
previously approved these changes
Oct 28, 2022
mabdinur
reviewed
Oct 28, 2022
mabdinur
reviewed
Oct 28, 2022
mabdinur
previously approved these changes
Oct 28, 2022
@mergify[bot] this pull request is now in conflict 😩 |
mabdinur
approved these changes
Oct 28, 2022
Kyle-Verhoog
approved these changes
Oct 28, 2022
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.
This is an automatic backport of pull request #3383 done by Mergify.
Cherry-pick of c437ad2 has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refresh
will re-evaluate the rules@Mergifyio rebase
will rebase this PR on its base branch@Mergifyio update
will merge the base branch into this PR@Mergifyio backport <destination>
will backport this PR on<destination>
branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com