Commit Graph
3452 Commits
Author SHA1 Message Date
Krrish Dholakia a8c3871b02 ci(test_logging): need to rewrite test_logging to work in parallel testing 2023-10-07 19:18:09 -07:00
Krrish Dholakia 9ac3ff584c ci(test_logging): have a change to make circle ci run our testing 2023-10-07 18:33:24 -07:00
Krrish Dholakia 0fb95faa50 ci(config.yml): run all tests on circle ci 2023-10-07 18:28:25 -07:00
Krrish Dholakia 28a2e31ede ci(test_logging): running just this test on circle ci 2023-10-07 18:23:54 -07:00
Krrish Dholakia 9f118bb5db ci(test_logging): debugging circle ci 2023-10-07 18:19:55 -07:00
Krrish Dholakia 4b35f1b6bd ci(test_logging): testing why circle ci keeps failing this test 2023-10-07 18:16:32 -07:00
Krrish Dholakia 713d998680 aider: Added print working directory command before running pytest in CircleCI config.
# 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.
2023-10-07 18:14:35 -07:00
Krrish Dholakia cd8ae2ecf6 test(test_logging): add back more tests for circle ci 2023-10-07 18:11:03 -07:00
Krish Dholakia a871d85696 Updated config.yml 2023-10-07 18:06:07 -07:00
Krrish Dholakia 51663e5618 test(test_logging): commenting out all but one test to see if it works on circle ci 2023-10-07 18:02:23 -07:00
Krrish Dholakia 3a15425288 aider: Modified CircleCI configuration to run pytest only on test_logging.py
# Aider chat conversation:

USER: what does `python -m pytest -vv --junitxml=test-results/junit.xml` do?

ASSISTANT: This command runs the pytest testing tool for Python in a specific way. Here's a breakdown of what each part does:

- `python -m pytest`: This runs pytest as a module using the Python interpreter. Pytest is a testing framework that allows you to easily create small, simple tests, as well as complex, functional testing for applications and libraries.

- `-vv`: This is an option for pytest that increases verbosity. Pytest without any `-v` is silent except for failures. One `-v` makes it print the test function names, and `-vv` also prints the individual test cases within those functions.

- `--junitxml=test-results/junit.xml`: This is an option for pytest that tells it to generate a test report in the form of an XML file in the JUnit format. This is useful for integrating the test results into tools that understand JUnit test reports, like many continuous integration servers. The `test-results/junit.xml` part specifies the location and name of the report file to generate.

So, in summary, this command runs all the pytest tests in the current directory and its subdirectories, prints detailed output about what tests are being run and their results, and generates a JUnit-format XML report of the test results.

USER: `.circleci/config.yml`

ASSISTANT: I'm sorry, but your request is not clear. Could you please provide more details about what you want to do with the `.circleci/config.yml` file? Are there any specific changes you want to make or any issues you're facing with it?

USER: how do i modify the pytest to only run test_logging.py

ASSISTANT: To modify the pytest command to only run `test_logging.py`, you need to specify the file name in the command. Here is how you can do it:

```yaml
.circleci/config.yml
<<<<<<< HEAD
      - run:
          name: Run tests
          command: |
            python -m pytest -vv --junitxml=test-results/junit.xml
          no_output_timeout: 30m
=======
      - run:
          name: Run tests
          command: |
            python -m pytest -vv test_logging.py --junitxml=test-results/junit.xml
          no_output_timeout: 30m
>>>>>>> updated
```

This change will make pytest only run the tests in the `test_logging.py` file. If `test_logging.py` is not in the root directory, you should provide the relative path to it from the root directory. For example, if it's in a `tests` directory, you would use `tests/test_logging.py`.
2023-10-07 17:58:07 -07:00
Krrish Dholakia 10ad137b2e docs(telemetry): add telemetry to docs 2023-10-07 17:49:42 -07:00
Krish DholakiaandGitHub f2febff0bb Merge pull request #556 from AnderMendoza/main
Readme Update
2023-10-07 17:29:43 -07:00
Krrish Dholakia 51e5e2b8d5 docs(proxy_server): doc cleanup 2023-10-07 17:29:04 -07:00
ishaan-jaff 051b21b61f (feat) proxy_server display model list when user does not specify model 2023-10-07 17:19:02 -07:00
ishaan-jaff e987d31028 (feat+fix) proxy_cli max_tokens int, --test stream 2023-10-07 16:38:40 -07:00
Krrish Dholakia 212734f142 test(test_logging): adding print statements for debugging circle ci 2023-10-07 16:20:17 -07:00
ishaan-jaff f37e2d4f8f (test) add back tg ai streaming test 2023-10-07 16:15:54 -07:00
Anderson MendozaandGitHub 6a89037b04 docs(readme update): adding issues links 2023-10-07 17:57:44 -05:00
Krrish Dholakia 815893c7d9 bump: version 0.5.5 → 0.5.6 2023-10-07 15:54:57 -07:00
Krrish Dholakia f6a48946b9 docs(custom-callback): return complete streaming response to custom callback 2023-10-07 15:54:52 -07:00
Krrish Dholakia 0c29658ee2 bump: version 0.5.4 → 0.5.5 2023-10-07 15:51:16 -07:00
Krrish Dholakia 58da58d5e1 style(openai.py): using typing for params 2023-10-07 15:51:16 -07:00
ishaan-jaff 42c363073b (docs) pass aws_access_key_id etc to completion 2023-10-07 15:49:28 -07:00
Krrish Dholakia 73fd895ee0 bump: version 0.5.3 → 0.5.4 2023-10-07 15:43:47 -07:00
Krrish Dholakia bcf0b0ac7b style(main.py): clean up print statement 2023-10-07 15:43:40 -07:00
Krrish Dholakia 9cda24e1b2 fix(utils): adds complete streaming response to success handler 2023-10-07 15:42:00 -07:00
ishaan-jaff f941975a78 (docs) with github 2023-10-07 15:38:36 -07:00
ishaan-jaff e1c9772b76 bump: version 0.5.2 → 0.5.3 2023-10-07 15:32:08 -07:00
ishaan-jaff 286cb993a4 (docs) bedrock 2023-10-07 15:31:40 -07:00
ishaan-jaff a67a531507 (docs) bedrock 2023-10-07 15:29:38 -07:00
ishaan-jaff acef90b923 (feat) sagemaker auth in completion 2023-10-07 15:27:58 -07:00
ishaan-jaff a58d0e9c94 (test) bedrock auth in completion 2023-10-07 15:27:58 -07:00
ishaan-jaff 48f5662b80 (feat) bedrock auth in completion 2023-10-07 15:27:58 -07:00
Krrish Dholakia 86a835f6fd docs(callbacks.md): add input callback to the callback docs 2023-10-07 14:21:30 -07:00
Krrish Dholakia ab8093118b docs(adding-litellm-proxy-config-to-docs): adding litellm proxy config to docs 2023-10-07 14:14:05 -07:00
Krrish Dholakia 78e413675e docs(completion-docs): add ollama provider specific settings 2023-10-07 13:53:01 -07:00
Krrish Dholakia d69038883c docs(completion-docs): adds more details on provider-specific params 2023-10-07 13:49:30 -07:00
ishaan-jaff aa615fea4f (docs) azure 2023-10-07 13:41:18 -07:00
ishaan-jaff 160e0e092a (docs) azure openai 2023-10-07 13:36:35 -07:00
ishaan-jaff 27c3a9b39a (test) new azure test for passing base, version 2023-10-07 13:27:07 -07:00
ishaan-jaff 2bdf16dac9 (docs) azure 2023-10-07 13:22:31 -07:00
ishaan-jaff a0b42d84f3 (docs) azure cookbook 2023-10-07 13:22:24 -07:00
ishaan-jaff 37454cf874 (docs) update azure docs 2023-10-07 12:08:19 -07:00
ishaan-jaff 66dd747f68 (docs) update index.md on docs.litellm.ai 2023-10-07 11:44:21 -07:00
ishaan-jaff 90a11bc138 (docs) remove mkdocs yml 2023-10-07 11:44:07 -07:00
ishaan-jaff 121fdaa8d2 bump: version 0.5.1 → 0.5.2 2023-10-07 11:12:34 -07:00
ishaan-jaff a326a0ade1 test(completion): test bumping a version 2023-10-07 11:11:54 -07:00
Krrish Dholakia f2a834e3e8 bump: version 0.5.0 → 0.5.1 2023-10-07 11:07:59 -07:00
Krrish Dholakia dd33abcee9 fix(test_client.py): adds docs for test_client.py 2023-10-07 11:07:35 -07:00