-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create python-integration-tests.yml #763
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dluc
reviewed
May 2, 2023
dluc
reviewed
May 2, 2023
python/tests/integration/completions/test_azure_oai_chat_service.py
Outdated
Show resolved
Hide resolved
dluc
reviewed
May 2, 2023
awharrison-28
force-pushed
the
awharrison/python-integration-tests
branch
from
May 2, 2023 20:29
bb66a9c
to
e18a7b3
Compare
…com/microsoft/semantic-kernel into awharrison/python-integration-tests
…com/microsoft/semantic-kernel into awharrison/python-integration-tests
… to their existing names
…com/microsoft/semantic-kernel into awharrison/python-integration-tests
mkarle
approved these changes
May 4, 2023
codebrain
pushed a commit
to searchpioneer/semantic-kernel
that referenced
this pull request
May 16, 2023
### Motivation and Context Run python integration tests on every push to main, and every 12 hours. These integration tests will run on every push to main as well as twice a day. At the time of this PR, we are seeing ~3 PRs to the python SK per day. Each Integration test run will make ~32 AI requests. For each PR, 12 runs will be made: 3 each for python 3.8, 3.9, 3.10, and 3.11 for a total of ~400 calls per push to main. We should re-evaluate the trigger on pushes to main if PRs to the python SK significantly increase. ### Description - add workflow definition for integration tests - Example run: https://github.com/microsoft/semantic-kernel/actions/runs/4874609026/jobs/8695771345?pr=763 - For push triggers, add path checks for dotnet/** or python/** depending on the type of workflow - pinned requirements.txt dependencies to the versions pinned in the pyproject.toml file to ensure parity between pip package dependencies and local code **Note**: Integration tests are failing on windows with python 3.8 - already captured a task to address the problem
dehoward
pushed a commit
to lemillermicrosoft/semantic-kernel
that referenced
this pull request
Jun 1, 2023
### Motivation and Context Run python integration tests on every push to main, and every 12 hours. These integration tests will run on every push to main as well as twice a day. At the time of this PR, we are seeing ~3 PRs to the python SK per day. Each Integration test run will make ~32 AI requests. For each PR, 12 runs will be made: 3 each for python 3.8, 3.9, 3.10, and 3.11 for a total of ~400 calls per push to main. We should re-evaluate the trigger on pushes to main if PRs to the python SK significantly increase. ### Description - add workflow definition for integration tests - Example run: https://github.com/microsoft/semantic-kernel/actions/runs/4874609026/jobs/8695771345?pr=763 - For push triggers, add path checks for dotnet/** or python/** depending on the type of workflow - pinned requirements.txt dependencies to the versions pinned in the pyproject.toml file to ensure parity between pip package dependencies and local code **Note**: Integration tests are failing on windows with python 3.8 - already captured a task to address the problem
johnoliver
pushed a commit
to johnoliver/semantic-kernel
that referenced
this pull request
Jun 5, 2024
### Motivation and Context Run python integration tests on every push to main, and every 12 hours. These integration tests will run on every push to main as well as twice a day. At the time of this PR, we are seeing ~3 PRs to the python SK per day. Each Integration test run will make ~32 AI requests. For each PR, 12 runs will be made: 3 each for python 3.8, 3.9, 3.10, and 3.11 for a total of ~400 calls per push to main. We should re-evaluate the trigger on pushes to main if PRs to the python SK significantly increase. ### Description - add workflow definition for integration tests - Example run: https://github.com/microsoft/semantic-kernel/actions/runs/4874609026/jobs/8695771345?pr=763 - For push triggers, add path checks for dotnet/** or python/** depending on the type of workflow - pinned requirements.txt dependencies to the versions pinned in the pyproject.toml file to ensure parity between pip package dependencies and local code **Note**: Integration tests are failing on windows with python 3.8 - already captured a task to address the problem
johnoliver
pushed a commit
to johnoliver/semantic-kernel
that referenced
this pull request
Jun 5, 2024
### Motivation and Context Run python integration tests on every push to main, and every 12 hours. These integration tests will run on every push to main as well as twice a day. At the time of this PR, we are seeing ~3 PRs to the python SK per day. Each Integration test run will make ~32 AI requests. For each PR, 12 runs will be made: 3 each for python 3.8, 3.9, 3.10, and 3.11 for a total of ~400 calls per push to main. We should re-evaluate the trigger on pushes to main if PRs to the python SK significantly increase. ### Description - add workflow definition for integration tests - Example run: https://github.com/microsoft/semantic-kernel/actions/runs/4874609026/jobs/8695771345?pr=763 - For push triggers, add path checks for dotnet/** or python/** depending on the type of workflow - pinned requirements.txt dependencies to the versions pinned in the pyproject.toml file to ensure parity between pip package dependencies and local code **Note**: Integration tests are failing on windows with python 3.8 - already captured a task to address the problem
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation and Context
Run python integration tests on every push to main, and every 12 hours.
These integration tests will run on every push to main as well as twice a day. At the time of this PR, we are seeing ~3 PRs to the python SK per day. Each Integration test run will make ~32 AI requests. For each PR, 12 runs will be made: 3 each for python 3.8, 3.9, 3.10, and 3.11 for a total of ~400 calls per push to main.
We should re-evaluate the trigger on pushes to main if PRs to the python SK significantly increase.
Description
Note: Integration tests are failing on windows with python 3.8 - already captured a task to address the problem
Contribution Checklist
dotnet format