Skip to content

Conversation

@cclauss
Copy link

@cclauss cclauss commented Feb 6, 2018

Run flake8 on Python 3 to find syntax errors and undefined names. --exit-zero treats all errors as warnings.

@cclauss
Copy link
Author

cclauss commented Feb 7, 2018

@aaltay None of my Jenkins builds seem to succeed: https://github.com/apache/beam/pulls/cclauss

Can you please help me understand if I am doing something wrong.

@jkff jkff assigned jkff and unassigned jkff Feb 7, 2018
@jkff jkff requested a review from aaltay February 7, 2018 22:12
@aaltay
Copy link
Member

aaltay commented Feb 8, 2018

Hi @cclauss, I looked at the errors and filed a few JIRA issues. Thank you for doing this, I believe we need to resolve the following issues to unblock this PR:

https://issues.apache.org/jira/browse/BEAM-3669 - lint error most likely unrelated to your change.
https://issues.apache.org/jira/browse/BEAM-3670 - test error, potentially affecting head.
https://issues.apache.org/jira/browse/BEAM-3671 - jenkins machines are missing python3 binaries, may take a while to resolve.

@aaltay
Copy link
Member

aaltay commented Feb 16, 2018

retest this please

Run flake8 on Python 3 to find syntax errors and undefined names.   __--exit-zero__ treats _all_ errors as warnings.
Copy link
Contributor

@holdenk holdenk left a comment

Choose a reason for hiding this comment

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

I'm not sure we want to treat all errors as warnings? It seems like it might be better to slowly add the flake8 tests we have fixed and treat the errors as errors so we don't regress by mistake.

passenv = TRAVIS*

[testenv:py36]
# autocomplete_test depends on nose when invoked directly.
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think this comment is relevant for this env.

@cclauss
Copy link
Author

cclauss commented Feb 23, 2018

@holdenk Thanks as always for your wise counsel. I was just trying to get these tests to be run at all by Jenkins so that others would see what I am seeing locally. I have been trying to progress your futurize work but in smaller chunks. Now that I see how difficult it is to provision Python 3 in the Jenkins environment, I believe that keeping changes relatively small is the way to make steady progress. We can tighten the screws as you recommend after we can actually run tests under Python 3.

@cclauss
Copy link
Author

cclauss commented Mar 2, 2018

Mostly fixed in #4376

@cclauss cclauss closed this Mar 2, 2018
@cclauss cclauss deleted the patch-2 branch March 2, 2018 01:31
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