-
Notifications
You must be signed in to change notification settings - Fork 1.2k
infra: use fixture for Chainer and XGBoost Python version, clean up remaining version fixtures #1631
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
infra: use fixture for Chainer and XGBoost Python version, clean up remaining version fixtures #1631
Conversation
…emaining version fixtures
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
@@ -248,8 +233,13 @@ def rl_ray_version(request): | |||
|
|||
|
|||
@pytest.fixture(scope="module") | |||
def chainer_full_version(request): | |||
return request.config.getoption("--chainer-full-version") | |||
def chainer_full_version(): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Out of scope, but are we still supporting Chainer? Should this be removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's been no public announcement to say we're not supporting it.
Issue #, if available:
#1461 (follow-up to #1609)
Description of changes:
see description of #1612
I also cleaned up the remaining framework version fixtures that hadn't been caught in the previous PRs.
Testing done:
linters
Merge Checklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.General
Tests
unique_name_from_base
to create resource names in integ tests (if appropriate)By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.