-
-
Notifications
You must be signed in to change notification settings - Fork 46.9k
Travis CI: Simplify the testing #887
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
Conversation
I think the repository only enables LGTM and maybe there's no need to use Travis anyone. |
The problems are that:
This can be seen in #882 which failed the LGTM tests even though it fixed the syntax error. It was only after #882 was merged that the LGTM tests started to pass. We want the test runner to test the code the current pull request but LGTM always tests the master branch. Travis CI (this PR) or CircleCI (#888) will test the current pull request and tell us if the code in that pull request should be accepted or not. |
I'll leave this to the owners. @AnupKumarPanwar |
@AnupKumarPanwar Can we please get https://travis-ci.org/TheAlgorithms/Python re-enabled? It ran 21 days ago. |
@cclauss It's already enabled. |
Great! Thanks. |
Can we please get this PR reviewed and merged? Now that Travis CI has been enabled all of our new PRs are failing which slows down the contribution and review process. This PR should get them working again. I have no problem running multiple CI tools (many projects do so) but once this PR has landed, we can disable LGTM if desired. Travis CI is clearly more flexible than LGTM. |
These changes were created to get around the fact that Travis CI was not enabled on this repo. Now that Travis is enabled, we can remove these modifications. The problems are that: 1. [LGTM does not want us running flake8 on their infrstructure](https://discuss.lgtm.com/t/can-i-get-lgtm-to-run-flake8-tests/1445/6) and 2. when we do, it [does not work as expected](https://discuss.lgtm.com/t/tests-are-not-automatically-run-when-lgtm-yml-is-modified/1446/4).
Uh oh!
There was an error while loading. Please reload this page.