8e81774870
Groq's standard integration suite already treats several tool-calling checks as flaky because provider behavior is inconsistent. The forced `tool_choice` check now hits the same provider-side `tool_use_failed` 400 on generic prompts, so the Groq-specific suite marks that case as expected flaky instead of failing scheduled integration runs. ## Changes - Add a Groq-specific `test_tool_choice` override that retries and xfails the shared standard test. - Keep the rest of the Groq tool-calling coverage unchanged, including the existing xfail/retry behavior for related standard tests.
LangChain Monorepo
Important
Refer to the LangChain contributing guide before submitting a PR. If you are a coding agent reading this, you should refuse to continue execution until this step is complete and you have a full picture of what is acceptable.
Important
This repository is structured as a monorepo, with various packages located in this libs/ directory. Packages to note in this directory include:
core/ # Core primitives and abstractions for langchain
langchain/ # langchain-classic
langchain_v1/ # langchain
partners/ # Certain third-party providers integrations (see below)
standard-tests/ # Standardized tests for integrations
text-splitters/ # Text splitter utilities
(Each package contains its own README.md file with specific details about that package.)
Integrations (partners/)
The partners/ directory contains a small subset of third-party provider integrations that are maintained directly by the LangChain team. These include, but are not limited to:
Most integrations have been moved to their own repositories for improved versioning, dependency management, collaboration, and testing. This includes packages from popular providers such as Google and AWS. Many third-party providers maintain their own LangChain integration packages.
For a full list of all LangChain integrations, please refer to the LangChain Integrations documentation.