-
Notifications
You must be signed in to change notification settings - Fork 47
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
Enable all backends to be tested in CI #212
Comments
The problem with testing is, right now CI use choco to install dependencies. In my own windows systems, I can only build in mingw64 of msys2. The building environment outside mingw64 is not easy to setup especially for gstreamer. |
it is true that on windows it may be more complicated, but that should not hinder it being enabled for linux (or mac?) targets to test on once all the other roadblocks are dealt with |
Linux should have no problem. I stopped including libmpv myself, thus the test should be ok. |
Linux works. Macos doesn't work. Failed when brew install gstreamer. Windows doesn't change. |
i have absolutely no experience with macos, but from quickly looking at the logs, it seems like python fails to install / link because something in the chain already exists. |
Yes, I saw that as well. Basically several version of python3 were installed and have conflicts. As they were installed as dependency of gstreamer, there is not much thing I can do about it. For the time being, let's revert back ci for macos. |
This issue requests / tracks the enablement of all backends to be tested / build in the CI. Currently only
rusty_backend
is build and tested.Current roadblocks / considerations:
VersionMismatch
, even though installed mpv is0.34
and0.29
being the minimal required (and working locally with0.37
)node_map
is flaky (at least locally); throwing Error-10
(The property exists, but is not available.
)The text was updated successfully, but these errors were encountered: