Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore(langchain): mark additional tests as flaky (#8941)
The following tests have been flagged as flaky in the nightly runs in CircleCI: - `test_global_tags` - `test_openai_llm_sync_with_multiple_prompts` - `test_openai_chat_model_sync_call_langchain_openai` - `test_openai_chat_model_sync_generate` - `test_chat_model_metrics` - `test_openai_math_chain_sync` - `test_chain_invoke_dict_input` - `test_chain_invoke_str_input` - `test_openai_sequential_chain_with_multiple_llm_sync` - `test_chain_logs` - `test_llm_logs_when_response_not_completed` - `test_lcel_chain_simple` - `test_lcel_chain_batch_311` - `test_lcel_chain_nested` - `test_llmobs_openai_llm` - `test_llmobs_openai_chat_model` - `test_llmobs_openai_chat_model_custom_role` Marking these as flaky as well until we can narrow down exactly why these are flaky (it seems on Python 3.11 specifically) ## Checklist - [x] Change(s) are motivated and described in the PR description - [x] Testing strategy is described if automated tests are not included in the PR - [x] Risks are described (performance impact, potential for breakage, maintainability) - [x] Change is maintainable (easy to change, telemetry, documentation) - [x] [Library release note guidelines](https://ddtrace.readthedocs.io/en/stable/releasenotes.html) are followed or label `changelog/no-changelog` is set - [x] Documentation is included (in-code, generated user docs, [public corp docs](https://github.com/DataDog/documentation/)) - [x] Backport labels are set (if [applicable](https://ddtrace.readthedocs.io/en/latest/contributing.html#backporting)) - [x] If this PR changes the public interface, I've notified `@DataDog/apm-tees`. ## Reviewer Checklist - [x] Title is accurate - [x] All changes are related to the pull request's stated goal - [x] Description motivates each change - [x] Avoids breaking [API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces) changes - [x] Testing strategy adequately addresses listed risks - [x] Change is maintainable (easy to change, telemetry, documentation) - [x] Release note makes sense to a user of the library - [x] Author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment - [x] 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)
- Loading branch information