Skip to content

toxgen: Make it clearer which suites can be migrated #4196

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Mar 26, 2025
Merged

toxgen: Make it clearer which suites can be migrated #4196

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c6c5cb0
toxgen: Make it clearer which suites can be migrated
sentrivana Mar 25, 2025
f1300b9
Merge branch 'master' into ivana/toxgen/add-comments
sentrivana Mar 26, 2025
9ff1309
Merge branch 'master' into ivana/toxgen/add-comments
sentrivana Mar 26, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 8 additions & 4 deletions scripts/populate_tox/populate_tox.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,22 +49,26 @@
# suites over to this script. Some entries will probably stay forever
# as they don't fit the mold (e.g. common, asgi, which don't have a 3rd party
# pypi package to install in different versions).
#
# Test suites that will have to remain hardcoded since they don't fit the
# toxgen usecase
"asgi",
"aws_lambda",
"cloud_resource_context",
"common",
"gevent",
"opentelemetry",
"potel",
# Integrations that can be migrated -- we should eventually remove all
# of these from the IGNORE list
"aiohttp",
"anthropic",
"arq",
"asgi",
"asyncpg",
"aws_lambda",
"beam",
"boto3",
"chalice",
"cohere",
"cloud_resource_context",
"cohere",
"django",
"fastapi",
"gcp",
Expand Down
Loading