forked from phoenix/litellm-mirror
# Aider chat conversation: USER: what directory is pytest in? ASSISTANT: The `pytest` command is typically installed in the `bin` directory of your Python environment. If you're using a virtual environment, it would be in the `bin` directory of that environment. However, the location of the `pytest` command doesn't affect how ^C KeyboardInterrupt USER: i mean the pytest command in the config.yml ASSISTANT: The pytest command in the `.circleci/config.yml` file is being run in the `~/project` directory. This is specified by the `working_directory` key in the `local_testing` job. When the `python -m pytest -vv test_logging.py --junitxml=test-results/junit.xml` command is run, it's being run in the `~/project` directory. If `test_logging.py` is not in the `~/project` directory, you would need to provide the relative path to it from `~/project`. For example, if it's in a `tests` directory under `~/project`, you would use `tests/test_logging.py`. USER: can you print the pwd before running the pytest? # Run pytest and generate JUnit XML report - run: name: Run tests command: | python -m pytest -vv tests/test_logging.py --junitxml=test-results/junit.xml no_output_timeout: 30m ASSISTANT: Sure, you can add a command to print the current working directory (pwd) before running the pytest command. Here's how you can do it: ```yaml .circleci/config.yml <<<<<<< HEAD # Run pytest and generate JUnit XML report - run: name: Run tests command: | python -m pytest -vv tests/test_logging.py --junitxml=test-results/junit.xml no_output_timeout: 30m ======= # Run pytest and generate JUnit XML report - run: name: Run tests command: | pwd python -m pytest -vv tests/test_logging.py --junitxml=test-results/junit.xml no_output_timeout: 30m >>>>>>> updated ``` This change will print the current working directory before running the pytest command. |
||
---|---|---|
.. | ||
config.yml | ||
requirements.txt |