Cannot run tests

[SeppiaBrilla]

Hello everyone,
I was trying to run the langchain's unit tests, however, whenever I run the command: make test, the shell returns the following output:

poetry run pytest tests/unit_tests/
ERROR: usage: pytest [options] [file_or_dir] [file_or_dir] [...]
pytest: error: unrecognized arguments: --snapshot-warn-unused
  inifile: /home/seppiabrilla/Documents/University/projects/langchain/libs/core/pyproject.toml
  rootdir: /home/seppiabrilla/Documents/University/projects/langchain/libs/core

make: *** [Makefile:10: test] Error 4

I'm on PopOs 22.04 and I'm using pytest version 7.4.3.
Can you help me? Thanks!

[dosubot[bot]]

🤖

Hello @SeppiaBrilla! I'm Dosu, a friendly bot here to assist you with your LangChain journey. I'm here to help you squash bugs, answer your queries, and guide you through contributing to this project. While waiting for a human maintainer, feel free to ask me anything regarding the repository. Let's get those unit tests running! 🚀

The error you're encountering when running LangChain's unit tests with the command make test is likely due to a version mismatch. In your pyproject.toml file, the pytest version is specified as ^7.4.2. This means that the project is configured to work with pytest version 7.4.2 and any minor updates to it, but not necessarily with version 7.4.3.

To resolve this issue, you can downgrade your pytest version to 7.4.2. You can do this by running the following command:

pip install pytest==7.4.2

After downgrading pytest, try running the tests again with make test. If you're still encountering issues, there may be other factors at play that aren't evident from the provided context.

As for the --snapshot-warn-unused argument in the pytest command, I wasn't able to find specific information about it within the LangChain repository. It's possible that this argument is related to a specific pytest plugin or a custom feature of LangChain. If you could provide more information about where this argument is being used, I might be able to give a more accurate answer.

I hope this helps! If you have any other questions or need further clarification, feel free to ask.

Best,
Dosu

Sources

• libs/cli/pyproject.toml
• templates/rag-aws-bedrock/pyproject.toml

---

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

[rahul-trip]

@dosu-bot
I am facing the same issue. Not sure how to fix this.

I have upgraded my pytest to version pytest-8.0.0 .
Still no luck!

[reachusama]

@SeppiaBrilla Did you solve this ?

I am facing the same issue :/

[gianfrancodemarco]

I had the same problem, you should probably just update pytest

[rahul-trip]

@dosu-bot
I am facing the same issue. Not sure how to fix this.

I have upgraded my pytest to version pytest-8.0.0 .
Still no luck!

[mkhludnev]

I'm somewhat surprised but this pytest's option is provided by separate package https://pypi.org/project/syrupy/. Perhaps it's obvious but not for myself. ok this package is mentioned in Makefile. Take care!

[chrispy-snps]

I would like to contribute, but I also cannot figure out how to run unit tests.

The "Langchain > Testing" documentation here specify to build the make test target, but there is no such target in the Makefile:

$ make test
make: *** No rule to make target `test'.  Stop.

I tried running pytest instead, but that fails in the collecting test session phase with:

ERROR  - ModuleNotFoundError: No module named 'vcr'

Edit 1: @hwchase17 - #7959 removed the test target from Makefile. Can you please update the documentation topic linked above with revised unit testing instructions? Thanks!

Edit 2: I found Makefiles in the lower-level directories, but I still get errors there:

$ cd libs/langchain
$ make test
poetry run pytest --disable-socket --allow-unix-socket tests/unit_tests/
ERROR: usage: pytest [options] [file_or_dir] [file_or_dir] [...]
pytest: error: unrecognized arguments: --snapshot-warn-unused --disable-socket --allow-unix-socket
  inifile: /remote/us01home28/chrispy/git/langchain/libs/langchain/pyproject.toml
  rootdir: /remote/us01home28/chrispy/git/langchain/libs/langchain

make: *** [test] Error 4

[eyurtsev]

hmm the testing page is out of date -- i'll add an issue for us to update

Review

https://python.langchain.com/docs/contributing/repo_structure

Identify the package that you're working in, cd into it and use poetry to set up env, then make test will run tests

[kylehh]

pip install syrupy can solve the error and it works for me with pytest 8.0.2 and syrupy 4.6.1

[eyurtsev]

Could you review these contributor docs and let me know if things are unclear?

https://python.langchain.com/docs/contributing

Take a look at the repo structure as well -- it's a mono repo. The root Makefile is a bit confusing, but it's only for docs not for testing code

poetry is used all all sub-packages to set up the testing environment and is do-able using the same command (see docs above ^)

[chrispy-snps]

I'm using Python 3.11.

I'm still not able to run unit tests. If I run the following commands in a clone repository:

rm -rf venv
python -m venv ./venv
. venv/bin/activate
pip install poetry
poetry install --with test
cd libs/langchain/
make test

I get the following:

$ make test
poetry run pytest --disable-socket --allow-unix-socket tests/unit_tests/
ERROR: usage: pytest [options] [file_or_dir] [file_or_dir] [...]
pytest: error: unrecognized arguments: --disable-socket --allow-unix-socket
  inifile: /global/silig01/chrispy/git/langchain/libs/langchain/pyproject.toml
  rootdir: /global/silig01/chrispy/git/langchain/libs/langchain

make: *** [test] Error 4

In which directory should I create the venv?

In which directory should I run poetry install --with test?

[gevial]

I faced the same issue in master branch. After checking out the latest tag (v0.1.16 at the time of writing), make test worked.
Seems like something's wrong in master.