-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Windows-based testing #931
Conversation
Please provide a description/motivation for this PR. What is it about? |
Slowly getting there: https://ci.appveyor.com/project/RmiBges/moviepy/builds/23374435 Test suite is passing (with 4 disabled tests) on python 3.4 x64, failing on versions above |
Reproducible and passing build on appveyor: https://ci.appveyor.com/project/RmiBges/moviepy/builds/23390075 |
@Zulko I need to make a final review, but I'm pretty much done with this PR. It should make maintenance of moviepy on Windows a lot more easier. Overall the changes are really minor things, except these two:
Let me know if those changes are ok with you. If they are, could you register moviepy on appveyor to enable automated checks ? Thanks a lot. |
I have registered Moviepy on Appveyor. As you seem to be the only active maintainer right now, feel free to make changes that make your life easier, as long as they don't change the experience of other maintainers or users (if so, please ask first). Here I understand that this is additional tooling, but the rest will all work as before, right? |
@Zulko Thanks for doing the registration, however the appveyor check is not showing up here, if I remember correctly it should show up automatically. Have you set it up using OAuth or Github Apps ? Yes you're correct, pipenv is additional but optional tooling. It should not break anyone's workflow. I'll always keep in mind to ask before any significant change proposal. |
Could you check inside the webhook configuration on Github if the box "Pull Request" is enabled for appveyor ? https://help.appveyor.com/discussions/questions/203-auto-run-tests-on-pull-requests#comment_33212404 |
It's working now :) |
Great. Thanks for the help ! Do you want to add your name to the maintainers list at the end of the README ? |
For sure I'll do it here then :) |
This made me realise my handle also needs updating... (only drive-through checking in here after weeks of not even having time to look at GH, lol) |
This PR enables CI testing on Windows platform, with minimal changes to the existing codebase. Closes #628.
Also:
Invalid Handle
when trying to instanciate subprocesses in subsequent tests (Related: Zombie processes after reader.close() #164, ffmpeg_reader is creating zombie processes #833)sys.path.append('tests')
in entire test suite as there is no need to modify path variable at runtime like this