Skip to content

Skip gpu tests in regions without gpu #461

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 4 commits into from
Nov 7, 2018
Merged

Conversation

yangaws
Copy link
Contributor

@yangaws yangaws commented Nov 6, 2018

Issue #, if available:

Description of changes:
In us-west-1, eu-west-2 and ca-central-1, there's no gpu ec2 instance like P2/P3. So the tf tests using gpu instance will fail and we should skip them in these regions.

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.

@codecov-io
Copy link

codecov-io commented Nov 6, 2018

Codecov Report

Merging #461 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #461   +/-   ##
=======================================
  Coverage   93.87%   93.87%           
=======================================
  Files          56       56           
  Lines        4199     4199           
=======================================
  Hits         3942     3942           
  Misses        257      257

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 8d76437...ade4b77. Read the comment docs.

@@ -35,6 +35,7 @@ def __call__(self, data):

@pytest.mark.continuous_testing
@pytest.mark.skipif(PYTHON_VERSION != 'py2', reason="TensorFlow image supports only python 2.")
@pytest.mark.skipif(REGION in ['us-west-1', 'eu-west-2', 'ca-central-1'])
Copy link
Contributor

Choose a reason for hiding this comment

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

add a reason. same below.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated

Copy link
Contributor

@nadiaya nadiaya left a comment

Choose a reason for hiding this comment

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

Other integ tests also run gpu tests (e.g. pytorch)

@yangaws
Copy link
Contributor Author

yangaws commented Nov 7, 2018

@nadiaya Only need to skip the tests that marked as continuous_testing (run as canary). For other p2 tests like pytorch async, it's not part of canary. But I guess I can still make the change though.

@@ -35,6 +35,8 @@ def test_distributed_cpu_training(sagemaker_session, chainer_full_version):
_run_mnist_training_job(sagemaker_session, "ml.c4.xlarge", 2, chainer_full_version)


@pytest.mark.skipif(REGION in ['us-west-1', 'eu-west-2', 'ca-central-1'],
reason='No ml.p2.xlarge supported in these regions')
Copy link
Contributor

Choose a reason for hiding this comment

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

what about p3? can't we use p3 then?

Copy link
Contributor Author

@yangaws yangaws Nov 7, 2018

Choose a reason for hiding this comment

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

P3 is either not supported or supported only by 1/3 of availability zones. So for these 3 regions we just skip tests for now to make canary good for now.

@yangaws yangaws merged commit 5201c60 into aws:master Nov 7, 2018
apacker pushed a commit to apacker/sagemaker-python-sdk that referenced this pull request Nov 15, 2018
metrizable pushed a commit to metrizable/sagemaker-python-sdk that referenced this pull request Dec 1, 2020
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.

4 participants