Commit graph

122 commits

Author SHA1 Message Date
ishaan-jaff
61e55e216a (ci/cd) test 2024-01-04 15:45:31 +05:30
ishaan-jaff
c19195131c (ci/cd) tag the correct version 2024-01-04 15:40:44 +05:30
ishaan-jaff
7822a8d421 (fix) remove appdirs as a dependency 2023-12-28 11:25:36 +05:30
ishaan-jaff
a73a9a8b3a (ci/cd) langfuse 2023-12-27 18:46:07 +05:30
Krrish Dholakia
9a19c7c599 ci(config.yml): add black formatting to ci/cd pipeline 2023-12-27 12:23:10 +05:30
ishaan-jaff
094f6355e4 (chore) fix ci/cd yaml format 2023-12-26 10:39:29 +05:30
ishaan-jaff
157b21c591 (ci/cd) deploy new litellm image, after pass ci/cd 2023-12-26 10:33:05 +05:30
ishaan-jaff
312af21f49 (fix) ci/cd 2023-12-25 23:59:02 +05:30
Krrish Dholakia
a6d1c7e221 build(circle_ci/config.yml): update requirements 2023-12-25 07:39:02 +05:30
ishaan-jaff
766a6b9014 (ci/cd) yml 2023-12-12 12:33:03 -08:00
ishaan-jaff
85a14d45e5 (ci/cd) print verbose 2023-12-11 23:20:50 -08:00
ishaan-jaff
fe394df8fc (ci/cd) update model_prices_and_context_window_backup 2023-12-11 11:27:51 -08:00
Krish Dholakia
7ed68da149 Updated config.yml 2023-12-09 11:09:18 -08:00
Krish Dholakia
4d0615391b Updated config.yml 2023-12-09 11:00:40 -08:00
Krish Dholakia
c8eca35015 Updated config.yml 2023-12-09 10:23:36 -08:00
Krish Dholakia
341382cb97 Updated config.yml 2023-12-09 10:20:46 -08:00
ishaan-jaff
39ea2e0909 (ci/cd) add langfuse 2023-12-08 17:49:43 -08:00
Krish Dholakia
f2bba58a24 Updated config.yml 2023-12-08 17:49:42 -08:00
ishaan-jaff
a2b89b212c (ci/cd) pip install google-cloud-aiplatform 2023-12-07 10:30:29 -08:00
ishaan-jaff
f32e55780a (ci/cd) add google-cloud-aiplatform 2023-12-07 10:21:09 -08:00
Krish Dholakia
1ff8f75752 Updated config.yml 2023-12-04 21:19:32 -08:00
Krish Dholakia
90c13d39ac Updated config.yml 2023-12-04 12:01:22 -08:00
ishaan-jaff
6c6add2a3c (fix) ci/cd 2023-12-01 16:06:22 -08:00
ishaan-jaff
fb8ccdd422 (ci/cd) add orjson as a dep 2023-11-30 20:18:18 -08:00
Krish Dholakia
d3d8b86eaa Updated config.yml 2023-11-24 11:34:24 -08:00
Krish Dholakia
c4e53aa77b Updated config.yml 2023-11-17 14:24:04 -08:00
ishaan-jaff
f061c775d0 (chore) ci/cd show durations of slowest tests 2023-11-15 18:07:04 -08:00
ishaan-jaff
eda4401c71 (chore) clean ci cd pipeline 2023-11-15 17:42:02 -08:00
ishaan-jaff
bcc9ebb78f (chore) clean up ci/cd testing requirements 2023-11-15 17:28:37 -08:00
ishaan-jaff
6f923ea813 (fix) remove bloat from ci/cid 2023-11-15 12:39:51 -08:00
Krrish Dholakia
f2c8d12eed ci(requirements.txt): enable openai 2023-11-11 19:14:22 -08:00
Krish Dholakia
863d6d9f0c Updated config.yml 2023-11-11 19:05:21 -08:00
ishaan-jaff
81d3230651 (test) run ci/cd again 2023-11-06 18:13:18 -08:00
ishaan-jaff
d9a8e01b2a (ci/cd) fix openai==0.28.0 2023-11-06 18:05:18 -08:00
ishaan-jaff
35ffde257d (test) fix traceloop sdk version 2023-10-27 10:25:43 -07:00
ishaan-jaff
97d237a896 (fix) ci/cd traceloop-sdk 2023-10-27 09:49:37 -07:00
Krish Dholakia
b826a31f0f Updated config.yml 2023-10-26 17:44:24 -07:00
Krish Dholakia
1984344d18 Updated config.yml 2023-10-24 12:28:29 -07:00
Krish Dholakia
371f0cb9bc Updated config.yml 2023-10-20 13:48:12 -07:00
ishaan-jaff
7848f1b5b7 (feat) new function_to_dict litellm.util 2023-10-14 18:26:15 -07:00
ishaan-jaff
46ab76562c (ci/cd testing) add langchain to testing 2023-10-13 15:24:30 -07:00
Krish Dholakia
74c5e6f415 Updated config.yml 2023-10-09 13:40:20 -07:00
Krish Dholakia
4900f11570 Updated config.yml 2023-10-09 13:30:51 -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
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
Krish Dholakia
a871d85696 Updated config.yml 2023-10-07 18:06:07 -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
Krish Dholakia
c1284f1d20 Updated config.yml 2023-10-06 06:33:43 -07:00