Skip to content
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

chore(langchain): update latest langchain test version [backport #9902 to 2.10] #9914

Merged
merged 3 commits into from
Jul 25, 2024

Conversation

Yun-Kim
Copy link
Contributor

@Yun-Kim Yun-Kim commented Jul 23, 2024

Backports #9902 to 2.10.

This PR updates the langchain test suite to use the latest langchain version. Note that the latest langchain version
adds a few properties to the BaseLLM/ChatModel classes, which means the latest version tests will see more span tags than previously. To avoid further splitting of the test cassettes/snapshots in this test suite, I have marked these extra tags to be ignored. This is not a breaking change, just updating test versions and to avoid breaking CI.

Checklist

  • 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
  • The change includes or references documentation updates if necessary
  • Backport labels are set (if applicable)

Reviewer Checklist

  • 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 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

@Yun-Kim Yun-Kim added the changelog/no-changelog A changelog entry is not required for this PR. label Jul 23, 2024
@Yun-Kim Yun-Kim requested review from a team as code owners July 23, 2024 20:15
@Yun-Kim Yun-Kim force-pushed the yunkim/backport-9902-to-210 branch 2 times, most recently from 17cb5e5 to 000c88a Compare July 23, 2024 20:26
This PR updates the langchain test suite to use the latest langchain
version. Note that the latest langchain version
[adds](https://github.com/langchain-ai/langchain/pull/23691/files) a few
properties to the BaseLLM/ChatModel classes, which means the latest
version tests will see more span tags than previously. To avoid further
splitting of the test cassettes/snapshots in this test suite, I have
marked these extra tags to be ignored. This is not a breaking change,
just updating test versions and to avoid breaking CI.

- [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))

- [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)
@Yun-Kim Yun-Kim force-pushed the yunkim/backport-9902-to-210 branch from 000c88a to 55e5ca3 Compare July 23, 2024 20:33
@datadog-dd-trace-py-rkomorn
Copy link

datadog-dd-trace-py-rkomorn bot commented Jul 23, 2024

Datadog Report

Branch report: yunkim/backport-9902-to-210
Commit report: 98467d9
Test service: dd-trace-py

✅ 0 Failed, 175492 Passed, 1786 Skipped, 12h 4m 5.82s Total duration (13m 3.14s time saved)
⌛ 2 Performance Regressions

⌛ Performance Regressions vs Default Branch (2)

  • test_schematized_service_names[None] - test_djangorestframework.py 7.19s (+5.78s, +412%) - Details
  • test_schematized_operation_name_env_v1 - test_httpx.py 4.05s (+3.44s, +565%) - Details

@pr-commenter
Copy link

pr-commenter bot commented Jul 23, 2024

Benchmarks

Benchmark execution time: 2024-07-24 19:09:59

Comparing candidate commit 98467d9 in PR branch yunkim/backport-9902-to-210 with baseline commit 40423ae in branch 2.10.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 221 metrics, 9 unstable metrics.

@Yun-Kim Yun-Kim enabled auto-merge (squash) July 24, 2024 15:30
@Yun-Kim Yun-Kim closed this Jul 24, 2024
auto-merge was automatically disabled July 24, 2024 21:08

Pull request was closed

@Yun-Kim Yun-Kim reopened this Jul 24, 2024
@Yun-Kim Yun-Kim closed this Jul 24, 2024
@Yun-Kim Yun-Kim reopened this Jul 24, 2024
@Yun-Kim Yun-Kim enabled auto-merge (squash) July 25, 2024 14:11
@Yun-Kim Yun-Kim merged commit 8364700 into 2.10 Jul 25, 2024
331 checks passed
@Yun-Kim Yun-Kim deleted the yunkim/backport-9902-to-210 branch July 25, 2024 14:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog/no-changelog A changelog entry is not required for this PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants