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

Fixed test for 'Connection refused' which could be 'Connection reset'. #61

Merged
merged 3 commits into from
Mar 1, 2019

Conversation

mauritsvanrees
Copy link
Sponsor Member

Fixes issue #59.

@mister-roboto
Copy link

@mauritsvanrees thanks for creating this Pull Request and help improve Plone!

To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass.

Whenever you feel that the pull request is ready to be tested, either start all jenkins jobs pull requests by yourself, or simply add a comment in this pull request stating:

@jenkins-plone-org please run jobs

With this simple comment all the jobs will be started automatically.

Happy hacking!

@mauritsvanrees
Copy link
Sponsor Member Author

@jenkins-plone-org please run jobs

Either W503 will fail or W504.

lint-py27 runtests: commands[2] | flake8 --doctests src tests setup.py
src/plone/testing/layer.py:126:26: W504 line break after binary operator
src/plone/testing/layer.py:127:74: W504 line break after binary operator
setup.py:49:36: W504 line break after binary operator
It's strange.  Without this, when I run flake8 I get this:
$ .tox/lint-py27/bin/flake8 --doctests src tests setup.py
src/plone/testing/layer.py:127:13: W503 line break before binary operator
src/plone/testing/layer.py:128:13: W503 line break before binary operator
setup.py:51:9: W503 line break before binary operator

We should ignore W503, so I pass an extra option, and then I get different errors:
$ .tox/lint-py27/bin/flake8 --doctests --ignore=W503 src tests setup.py
src/plone/testing/zope.py:124:19: T000 Todo note found.
src/plone/testing/tests.py:95:9: T003 use of Django-style assert statement found (instead of regular assert): assertIsNotNone
@mauritsvanrees
Copy link
Sponsor Member Author

@jenkins-plone-org please run jobs

@mauritsvanrees
Copy link
Sponsor Member Author

Since Jenkins 5.2 is broken the entire day, and this fixes it, I merge it myself. All checks pass.

@mauritsvanrees mauritsvanrees merged commit 6f54d0e into master Mar 1, 2019
@mauritsvanrees mauritsvanrees deleted the issue-59-connection-refused-reset branch March 1, 2019 21:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants