| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
No longer needed after removal of 32-bit builds.
This reverts commit d56ad8f0329e973d4c41e93f8491b4d3ceac9793.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
While mpv can be build for 32-bit platforms, MSYS started dropping some
of the 32-bit packages [1]. We cannot be asked to monitor and fix CI build
each time a dependency package randomly disappears [2].
Disable MSYS 32-bit builds if the support for this platforms is phased
out upstream. Sadly this will reduce our build coverage.
[1] https://www.msys2.org/news/#2023-12-13-starting-to-drop-some-32-bit-packages
[2] https://github.com/msys2/MINGW-packages/commit/fff2fa3711e3cf1c9b65b12784ab3d9428a779f1
See also: https://github.com/msys2/MINGW-packages/issues/19747
|
|
|
|
|
|
|
| |
This package isn't available for i686 anymore, and not worth the hassle
to only install it for win64 since it isn't particularly useful.
See: https://github.com/msys2/MINGW-packages/commit/fff2fa3711e3cf1c9b65b12784ab3d9428a779f1
|
|
|
|
| |
"behavior" is written in US English form in all templates except here.
|
|
|
|
|
|
|
|
|
| |
https://0x0.st/ has a maximum retention period of 1 year, and much less
for larger files. Uploading them directly to github issue avoids this,
which most people are already doing anyway because of greater convenience.
log file: don't request 0x0.st.
sample files: recommend github first.
|
|
|
|
|
|
|
|
|
|
|
| |
Add more and unify requested information:
windows, linux, others: request GPU model to provide more info about
known hardware limitations and hardware/driver combo bugs.
windows, others: request general GPU info.
build: request meson version.
windows, linux, others: request backtrace in case of crash.
all: clarify the language of not attaching a log file.
|
|
|
|
| |
This reverts commit 67aa5684379d42ad1e9b8cc66a04d63394e63994.
|
|
|
|
|
|
|
| |
msys added xxhash has a makedep for libplacebo* which means we need to
install it in the CI as well if we want to build against it.
*: https://github.com/msys2/MINGW-packages/commit/07f4c34d22fda0284a1857ac5006d784fe058075
|
|
|
|
|
|
|
|
|
|
| |
In the pursuit of stability.
It is slower and QEMU-based, but if this isn't stable, I don't know what
will be.
Bump the timeout to 30 minutes, just in case. It seems to take 12-15
minutes to finish.
|
|
|
|
| |
Maybe macos-13 runners will be more stable?
|
|
|
|
|
|
|
|
|
|
| |
Since vmactions is basically a bootlooping disaster* with no signs of
life from upstream, let's try a different action instead and hope it
works better. We don't need to force the latest release channel, so
delete that part. Also make the pkg install just one command for
simplicity.
*: https://github.com/vmactions/freebsd-vm/issues/74
|
|
|
|
|
|
|
|
|
| |
I won't even comment how terrible this option is and why in 2023 default
is not at least `autocrlf=input`.
Disable the conversion to CRLF. We build everything in MSYS2 sysroot,
which supports/expects LF. While the checkout itself is done with
actions/checkout@v3 and this causes problems.
|
|
|
|
| |
for downloading libplacebo.wrap via git
|
| |
|
|
|
|
|
| |
It bootloops quite often these days which is annoying and clogs up all
the macos runners. https://github.com/vmactions/freebsd-vm/issues/74
|
|
|
|
|
|
|
|
|
|
|
|
| |
Homebrew has finally given up supporting macOS 11, and all updated
dependencies are being built locally. Additionally, python3.12 - being
a dependency of libass in Homebrew - seems to completely fail under
cairo's meson usage on macOS 11, even if we let it build.
Thus, finally remove macOS 11 from our macOS build matrix, leaving
12 and 13.
ref: Homebrew/brew#16019
|
|
|
|
|
|
| |
Copy and pasted from commit msg lint obviously, but I forgot to rename
it. Oops. Capitalize the name field while I'm at it (seems like all the
other workflows do it too).
|
|
|
|
|
| |
Should hopefully avoid any accidents with stray characters and other
things. Only needs to run if something within DOCS changes.
|
|
|
|
|
|
|
|
|
| |
When someone purely changes some documentation or something similar,
there's no point in having the whole CI build go off. This also leads to
the bot spamming a comment linking to artifacts. This is only useful if
actual source code changes (i.e. so users can test if need). So just add
a path filter to blacklist directories we don't want to consider. If all
changed files match those directories then the CI won't run.
|
| |
|
| |
|
|
|
|
|
|
| |
Apparently it is available in public beta since late April.
ref actions/virtual-environments#6426
|
|
|
|
| |
Arguably the better place for this as it provides fine-grained feedback.
|
|
|
|
| |
Instead of `quarterly`, to get access to recent packages.
|
|
|
|
|
|
|
| |
Python 3.11 will be released soon as default Python package, and
actually python3.11 package already disappeared from the repository.
This reverts commit c637beb5223b0af5a671c8829a0e1a42e7e9a411.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Can significantly reduce build time, most of dependencies have fixed
versions, so they can be cached fully. Others will be incrementally
build.
Cache is saved on every run and restored from the newest one. Size is
limited to 500M (compressed) to keep cache save/restore fast. Clean
cached build is little over 100M, so we have a headroom as things will
grow. ccache will automatically evict least recently used entries.
It is unlikely that clean build will exceed the limit anytime soon, but
it is something to keep in mind, as we do not want to evict cache
entries from current build, so the cache size need to be set correctly.
|
|
|
|
| |
Those builds should be evaluated separately, no need to fail other one.
|
| |
|
|
|
|
|
|
| |
Remove waf entirely in favor of meson as the only supported build
system. Waf was officially deprecated in 0.36.0, and has not been
preferred over meson since 0.35.0.
|
|
|
|
|
|
|
| |
Run not only scripts inside build system, but also meson itself with
Python 3.11.
Fixes: eb4da3400a1c37eea7b258b00297e8b8fcdd8db4
|
|
|
|
|
| |
It is unstable and fails quite often. Just disable it and remove log
printing of failure.
|
| |
|
|
|
|
|
|
|
|
|
| |
There is a long-standing bug with random crashes of Python 3.10 on CI.
See:
https://github.com/python/cpython/issues/105400
https://github.com/msys2/MINGW-packages/issues/11864
https://github.com/msys2/MINGW-packages/issues/17415
|
|
|
|
|
|
|
|
|
| |
To avoid building against stale version of dependencies. In particular
libplacebo is moving target and as we can see the build has been broken
few times recently, so let the CI validate it for us.
The time to build everything is under 30 minutes, which is acceptable in
my opinion, not much longer than macos build.
|
|
|
|
|
| |
Allows python to download waf correctly, fixing CI failure due to its
outdated built-in certificate pool.
|
|
|
|
|
| |
luajit is currently crashing on 32-bit build:
https://github.com/msys2/MINGW-packages/issues/17042
|
| |
|
|
|
|
|
| |
libplacebo-next version requirement was increased recently, need to
rebuild it to fix mingw CI builds.
|
|
|
|
| |
libplacebo requires >= 0.63
|
|
|
|
|
|
|
| |
It turns out that you actually have to add failure() to each condition
otherwise a default status check of success() is applied (thanks
github). Looks redundant but whatever. Thanks to @kasper93 for actually
reading the documentation.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of running the test directly in the build script, we can make a
separate step in the workflow so it looks a little prettier. For running
the actual tests, we skip mingw since they will never be run (cross
compiled). Additionally, improve the github workflow logic a bit so that
way logs on failure are only shown when that specific step fails. The
freebsd job still has to be less elegant since it's in a weird vm
thingy.
Not really related but the location of various build directories
(particularly waf) are corrected as well (might as well).
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
While the waf build has served us well for many years, it's time to
officially consider it deprecated. The meson build was added fully with
the intention to eventually replace waf and its current state is more
than good enough to do that. Let's start the deprecation period now to
give users a heads up to switch before we remove waf for good.
|
|
|
|
|
|
|
|
|
|
| |
This way each time a new Python version is installed via Homebrew
, we don't get CI failures due to the upstream Python distribution
also being installed.
Ref: actions/runner-images#6459
Ref: actions/runner-images#6507
Ref: actions/runner-images#2322
|
|
|
|
|
|
|
| |
Workflow virtual machines have now been updated so that moby package
contains rule for the newly added syscalls, such as 'clone3'.
Effectively reverts 64fa440c697b9b8e96e14e33f7e79c6674c5b1a3 .
|
|
|
|
|
| |
These utilize a custom docker container in any case, but this brings
us to consistency with the mingw-w64 jobs.
|
|
|
|
|
| |
mingw-w64 has utilized this for a while so might as well make it
consistent.
|
|
|
|
|
|
|
| |
Thankfully, this version is no longer the default on any of the
macOS runners.
Effectively reverts a76527772eb52084c61241b89cfb42ce59f6f6a4 .
|
|
|
|
|
|
|
|
|
| |
This older image has been deprecated and will be removed in December.
The images have also already had planned outages during which the CI
flow has been affected. Thus it feels like a good idea to clean
this up at this point.
Ref: actions/runner-images#5583
|
|
|
|
|
|
|
| |
This was only needed because the mingw CI used to run on Ubuntu 20.04
which had a version of meson too old for mpv. This hasn't been the case
since we switched to 22.04 in f7164fcfaca1b1d8f0ceb9cb58e532c172cf83fa
and can now just use the package manager version.
|
| |
|
|
|
|
|
|
|
| |
- newer library versions
- use libplacebo submodules
- prefer meson where possible
- fix minor details
|
|
|
|
|
|
|
| |
Despite being run in a VM, the workflow actually copies the files back
to the host. We can then explictly print the error logs on failure in
their own separate section for visibility instead of it being hidden
within all the vm output.
|
|
|
|
|
| |
Apparently an implicit dependency on it through one of the
otherwise installed packages is no longer there.
|
| |
|
|
|
|
| |
Reduce the churn by transparently picking up bustage fixes.
|
| |
|
|
|
|
|
| |
FreeBSD doesn't support /latest and /quarterly package repos on EOL
versions. 13.0 reaches EOL on 2022-08-31, so avoid CI breakage.
|
|
|
|
| |
This is needed for x11 which is in turn needed for vdpau.
|
|
|
|
| |
Newer image builds already include Meson.
|
| |
|
|
|
|
|
| |
Updates mingw-w64 to 8.0 as well as generally bumps the toolchain
to gcc 10.x.
|
|
|
|
|
|
| |
Apparently it is now in public beta.
ref actions/virtual-environments#5446
|
|
|
|
|
|
|
|
|
|
| |
Recently, git patched a CVE which makes it much more strict about
different users operating on directories they don't own. For us, this
causes breakage with version.sh and version.py since they both run a git
describe command to fetch the commit hash. Currently, this only affects
the tumbleweed container (likely because it was recently changed) and
thus the git describe command always errors out. Workaround this by just
explictly adding the mpv directory as a safe directory for git.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
LuaJIT is still actively developed, but upstream is allergic to making
new releases for whatever reason. The last tagged release was in May of
2017, so we probably shouldn't expect a new release anytime soon. Now
for mpv, this doesn't really matter except in the case of macOS where
2.0.5 is actually a bit broken (and of course the CI uses luajit). More
specifically, the 2.0.5 pc is broken and has a "-pagezero_size 10000"
flag which causes libmpv to fail (only executables are allowed to use
this). This magically works on waf. It's possible that it just happens
to ignore the link arguments. However on the meson build, this is broken
and led to a really ugly hack using a partial dependency so both mpv and
libmpv succeed. Fortunately, the 2.1 luajit branch fixes this.
Unfortunately, there's no actual release.
Instead, just use Lua 5.1. Note that lua 5.1 is technically deprecated
in homebrew, but the chances of this going away is pretty slim since
everyone knows that new lua versions are not backwards compatible.
Anyways, using 5.1 works fine and lets us get rid of a terrible hack in
the meson build. People really shouldn't be using 2.0 LuaJIT anyway.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This define was always just a stopgap for that two month period (August
2021 - October 2021) where the bytes_read field in ffmpeg was completely
missing. Before that time, it was a private member in a struct (which
mpv used). Afterwards, it officially became public. Fortunately, the
lack of this field never actually made it into a release, so it could
have only possibly affected people building from the master branch.
Since ffmpeg 5.0 came out recently, and it's been plenty of months since
that two month window, we can go ahead and drop this check. This
finishes up the work done in 78cfeee2b93830f2988508a653b508336147b79d.
Sidenote: the cached ffmpeg version in the mingw ci were from that time
period when the bytes_read field was missing. The N in the workflow is
bumped to force a full rebuild and fresh clone of ffmpeg.
|
|
|
|
| |
We have this ao again since #9298 so let's run it through the CI.
|
|
< |