Skip to content
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

fix: add timeouts on docker local-invoke, start-api and start-lambda integration tests #1478

Merged
merged 7 commits into from
Oct 18, 2019

Conversation

sriram-mv
Copy link
Contributor

  • cause the builds to fail on appveyor rather than halting the test
    forever, resulting in a lengthy build timeout.
  • had to play around with requirements to be able to adopt pytest-timeout, also do we need tox?

Issue #, if available:

Description of changes:

Checklist:

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

- cause the builds to fail on appveyor rather than halting the test
  forever, resulting in a lengthy build timeout.
@sriram-mv sriram-mv changed the title fix: add timeouts on docker local-invoke, start-api and start-lambda fix: add timeouts on docker local-invoke, start-api and start-lambda integration tests Oct 18, 2019
@sriram-mv
Copy link
Contributor Author

Might need to adopt https://github.com/pytest-dev/pytest-rerunfailures as well.

@@ -1,13 +1,13 @@
coverage==4.3.4
tox==2.2.1
Copy link
Contributor

Choose a reason for hiding this comment

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

No we don't need tox. +1

pytest-cov==2.4.0
# astroid > 2.0.4 is not compatible with pylint1.7
astroid>=1.5.8,<2.1.0
pylint==1.7.2

# Test requirements
pytest==3.1.0
py==1.4.33
pytest==3.6.0
Copy link
Contributor

Choose a reason for hiding this comment

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

This might cause some weird test failures/warnings I think.

Copy link
Contributor

Choose a reason for hiding this comment

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

Are you talking about removing py or the pytest upgrade?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I had to upgrade pytest to even be able to use pytest-timeouts.

Copy link
Contributor

@sanathkr sanathkr left a comment

Choose a reason for hiding this comment

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

LGTM. Hope tests pass

@@ -30,6 +31,7 @@ def setUp(self):
def tearDown(self):
os.remove(self.events_file_path)

@pytest.mark.timeout(timeout=300, method='thread')
Copy link
Contributor

Choose a reason for hiding this comment

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

is this seconds?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yeah its seconds.

@sriram-mv
Copy link
Contributor Author

Gonna increase the lambda timeouts on the integration test templates. Looks like 3 seconds is too low (sporadically) when running docker linux containers on appveyor windows.

- removal of python2 matrix
- change to always activation of virtualenv on windows on every stage
- infinite timeout, but each of these tests has an individual timeout of
  300s
@sriram-mv sriram-mv force-pushed the pytest_timeout branch 2 times, most recently from 55c5426 to a1e2635 Compare October 18, 2019 18:50
- temporarily remove smoke tests on windows matrix
@sriram-mv sriram-mv merged commit ec80eb0 into aws:develop Oct 18, 2019
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.

None yet

3 participants