-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
The Travis tester seems to be failing #406
Comments
The reason it failed is that moviepy is registered with Travis, although there is no test suite yet. |
@mbeacom are you working on a test suite ? Otherwise I would propose that I just start a very minimal test suite with a super-naive test, just to make sure that PRs are at least syntatically correct. Would Pytest be ok for the test suite ? |
@mbeacom are you working on a test suite ? Otherwise I am happy to start one ? Would Pytest be ok ? |
I've added some tests in the test directory. Can we set this up to use Travis? |
I've added a .travis.yml file to my forked repo earney/moviepy, and it is passing on travis-ci. Feel free to use the .travis.yml and (test cases in the test directory as a starting point). I will do this if no one else wants to. @Zulko made a statement that he was going to work on this issue this weekend. |
My plan was to troubleshoot Travis but if your .travis.yml already works, feel free to go ahead and merge (maybe clean the comments). |
sure thing! |
closing with travis has been working for a week or so. |
Currently both pull requests (mine and this one) that have been submitted since the Travis testing suite was implemented have failed their tests. I think this is a fault of the tester or the test cases, as there appears to be no problem in the PR code.
My PR literally added 1 line of code, which has no reason to fail.
The text was updated successfully, but these errors were encountered: