-
Notifications
You must be signed in to change notification settings - Fork 31
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
[READY] Removing tox for clarity in CI and tests #42
Conversation
aff4dc3
to
454d713
Compare
I'm still working on solving an INTERNALERROR when running pytest with coverage reports. |
Pylint is run to only return non-zero exit status if there is an error. However, there are still many Warnings, Convention, and Refactoring messages that should be looked into to maintain high code quality. |
Hey @felipejinli , thanks a lot for the detailed work here. I'll be reviewing this PR this week. Also, did CI run for your new branch? Can you also link to the CI results of your work? |
Hey @felipejinli . Thanks a lot for your work. I've been trying to run the Also wrt the pylint stuff you mention in the above comment, what's the difference between flake8 and pylint? I've been using flake8 (as you saw) and I manually ignored a bunch of checks because i felt they were too aggressive. |
@asn-d6 That's very strange. Have you checked on your python's site-packages directory to see if pytest is actually installed? Might be helpful if you share the log. |
Hmmm, I did Now, I'm getting this:
|
Sorry, I'm yet to push the new changes. In the old tox setup, functional tests were not run in Travis CI. I'll push a new commit to fix this soon. |
Hmmm, I think the v2 functional tests have been broken for a while (because of some chutney changes). Let's just disable them for now and I will remove them for good in a few months when v2 gets deprecated. Sorry for not mentioning that and putting you to needless work. |
Merged! Thanks a lot @felipejinli ! I also opened a ticket about reviving the Chutney tests #46 |
BTW @felipejinli , I tried to revive the v2 functional tests that did not depend on Chutney but now Travis is failing because it can't find Any idea what I did wrong? |
@asn-d6 Sorry for the late reply. That's strange, I can't seem to find the cause. But I'll look into it again tomorrow! |
Purpose: This simplifies the setup process by removing tox. NB. Travis already runs tests inside an isolated virtualenv for python #32.
Regarding changes: Documentation builds are run at every push and its output directory has changed from .tox (before) to .docs/_build (after). @asn-d6 Does this cause a conflict (I'm unsure if there's any automated documentation deployment to docs site? Linters are run both for functional and unit tests.