chore(ci): update beautifulsoup framework test to use local ddtrace not PyPI latest [backport 2.15]
#11142
Conversation
This file contains 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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
…e` not PyPI latest (#11132) The `beautifulsoup` framework tests were using `pip install ddtrace` to install `ddtrace`, which was using the `latest` version of `ddtrace` from PyPI instead of the local version from the branch ([see example here](https://github.com/DataDog/dd-trace-py/actions/runs/11462716535/job/31894873509#step:5:19)). This PR fixes this to run `pip3 install ./ddtrace` instead so we're testing with the current version of `ddtrace` for the branch that triggered the test. ## Checklist - [x] PR author has checked that all the criteria below are met - The PR description includes an overview of the change - The PR description articulates the motivation for the change - The change includes tests OR the PR description describes a testing strategy - The PR description notes risks associated with the change, if any - Newly-added code is easy to change - The change follows the [library release note guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html) - The change includes or references documentation updates if necessary - Backport labels are set (if [applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)) ## Reviewer Checklist - [x] Reviewer has checked that all the criteria below are met - Title is accurate - All changes are related to the pull request's stated goal - Avoids breaking [API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces) changes - Testing strategy adequately addresses listed risks - Newly-added code is easy to change - Release note makes sense to a user of the library - If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment - Backport labels are set in a manner that is consistent with the [release branch maintenance policy](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting) (cherry picked from commit 9ba5f9a)
github-actions
bot
added
the
changelog/no-changelog
juanjux
approved these changes
Oct 24, 2024
avara1986
approved these changes
Oct 24, 2024
emmettbutler
approved these changes
Oct 28, 2024
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.
Backport 9ba5f9a from #11132 to 2.15.
The
beautifulsoupframework tests were usingpip install ddtraceto installddtrace, which was using thelatestversion ofddtracefrom PyPI instead of the local version from the branch (see example here).This PR fixes this to run
pip3 install ./ddtraceinstead so we're testing with the current version ofddtracefor the branch that triggered the test.Checklist
Reviewer Checklist