Skip to content

Freeze framework integ test to latest version #359

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

Merged
merged 2 commits into from
Aug 21, 2018
Merged

Conversation

yangaws
Copy link
Contributor

@yangaws yangaws commented Aug 20, 2018

Issue #, if available:

Description of changes:
Freeze the framework integ test to latest version.

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.

  • I have read the CONTRIBUTING doc
  • I have added tests that prove my fix is effective or that my feature works (if appropriate)
  • I have updated the changelog with a description of my changes (if appropriate)
  • I have updated any necessary documentation (if appropriate)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@@ -91,12 +91,12 @@ def chainer_version(request):
return request.param


@pytest.fixture(scope='module', params=['1.4.1', '1.5.0', '1.6.0', '1.7.0', '1.8.0'])
@pytest.fixture(scope='module', params=['1.8.0'])
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we use the DEFAULT_VERSION constant here to minimize duplication?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah there's no duplicate here, for now each framework will only have one latest version always.

But seems get a LATEST_VERSION constant would be more clear to readers. I will apply that. Thanks!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Then let me check if:
1, all frameworks have that
2, 1.2 and 1.2.1 can both work

@codecov-io
Copy link

Codecov Report

Merging #359 into master will increase coverage by 0.16%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##           master    #359      +/-   ##
=========================================
+ Coverage   92.93%   93.1%   +0.16%     
=========================================
  Files          51      51              
  Lines        3555    3555              
=========================================
+ Hits         3304    3310       +6     
+ Misses        251     245       -6
Impacted Files Coverage Δ
src/sagemaker/local/image.py 89.18% <0%> (+1.8%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 80fa52e...dd5d200. Read the comment docs.

@yangaws yangaws merged commit d7665de into aws:master Aug 21, 2018
pdasamzn pushed a commit to pdasamzn/sagemaker-python-sdk that referenced this pull request Nov 1, 2018
apacker pushed a commit to apacker/sagemaker-python-sdk that referenced this pull request Nov 15, 2018
Correct typo to avoid confusion on number of endpoints
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants