| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
GitHub changed how step otputs are to be set, see
https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
For our docker containers we need to forward the GITHUB_OUTPUT
environment var. The same applies to some other currently unused
env vars. To reduce copy-paste create a proxy-shell script.
|
| |
|
|
|
|
| |
MSYS2 already defines a $MINGW_PACKAGE_PREFIX environment variable
making it superfluous to explicit track the matching prefix ourselves.
The local $pre variable is kept to make the package list more readable.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
It turns out, the undefined behaviour we detected was not in our own
code, but in the inline isnan() function from MinGW-w64's headers.
A patch has been submitted to and merged by MinGW-w64:
https://sourceforge.net/p/mingw-w64/mailman/mingw-w64-public/thread/20221109020507.1704-1-chortos@inbox.lv/
Until a version containing the fix is available in MSYS2, we
can avoid problematic inlines by defining __CRT__NO_INLINE.
Closes: https://github.com/libass/libass/issues/639
|
| |
|
|
|
|
| |
If static libass is linked into a binary defining functions
of the same name there will be issues. To avoid this ensure
our non-static functions are all prefixed with 'ass_'.
|
| |
|
|
|
| |
Previously, some bug reporters used it to create
(plain) "xy-VSFilter" reference screenshots.
|
| |
|
|
|
|
| |
Without sanitisers, tests (currently) pass,
so we can at least run them unsanitised.
Of course, fixing the UB would be the ideal solution.
|
| |
|
|
|
|
| |
We added and tweaked the configs so much, this is now actually
more concise and also avoids ambiguity whether an existing entry
is modified or a new one added.
|
| |
|
|
|
| |
macos-10.15 is being phased out and currently, prior to
full removal, fails unconditionally during specific times.
|
| |
|
|
|
|
|
|
| |
UBSAN finds something in the UWP build with the
regression/karaoke/357-k-and-kf-desynced.ass sample.
But due to lack of libubsan there's no report and
manual investigation is needed --- which requires a
Windows development setup.
|
| |
|
|
|
|
|
|
|
|
| |
Use `-j 1` in CI for unmangled output.
In the future this could be improved by integrating with Automake's
test support to get better output with multiple jobs. Considering
the layour of the crash tests will likely change and that currently
the tests run in less 15 seconds even with just a single thread,
this should be good enough for now.
|
| |
|
|
| |
The step's env settings are not forwarded to containers.
|
| | |
|
| | |
|
| |
|
|
| |
There no longer are any prefixed libtool-packages in MSys2's repo.
|
| | |
|
| |
|
|
|
| |
The container is purpose built to have the minimum version of all direct
dependencies as well as an old'ish compiler and autotools toolchain.
|
| |
|
|
|
|
| |
Make build-config comments more consistent and
also list already installed deps for apt,
but avoid installing additional recommended packages
|
| |
|
|
|
|
|
| |
We no longer use caches which might be affected by sudden version
changes, and 18.04's FriBiDi is too old for USE_FRIBIDI_EX_API.
A follow-up will add a dedicated build
to test older library configurations.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Reuse the desktop build for this, as UCRT32 doesn't exist.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Since GHA only has native support for glibc-linux use Alpine via Docker.
Even though GHA does have native Docker support, its
`job.<name>.container` option cannot be used here, as there appears to
be no way to set a noop image name atm (empty string causes an error).
Using `tail -f /dev/null` to keep the image running (while ignoring
zombie processes) was taken from GHA's native Docker setup procedure.
Relies on /home/runner/work being the default for checked out repos.
|
| | |
|
| |
|
|
|
|
|
| |
By not caching at all.
Now that we're no longer using `brew update`, caching is barely doing
anything, but causes some problems when the cache is not newer than
GHA's preinstalled stuff.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We need to run Coverity on a clang build, because Coverity's gcc
misreports its version causing ASS_DEPRECATED_ENUM version checks to
falsely suceed, which then causes the build to fail.
Coverity's clang likely also misreports its version, but whatever clang
build Coverity is using happens to work with our current code.
Coverity's gcc failing:
https://travis-ci.org/github/libass/libass/builds/743655400
Coverity's clang succeeding:
https://travis-ci.org/github/libass/libass/builds/740511824
Also Coverity's travis script is borked and always returns an error even
on success, because it expects Coverity's server to respond with code
201, but they actually return 200 instead.
To get meaningful job status we are using a custom script based on
Coverity's upstream script and fontforge's Coverity script.
|
| |
|
|
|
| |
This commit is adapted from mpv and should speed up MacOS builds.
https://github.com/mpv-player/mpv/commit/3586ef77f31c9e0d396b0356a4054d57cbd146cb
|
|
|
travis-ci.org will close on 31.12.2020, and travis-ci.com's free plan
does not include MacOS builds, therefore we need an alternative.
Unfortunately, I couldn't find a way to get IRC notifications with
GitHubActions and Coverity is also missing in GHA atm, so for now
Travis still remains.
|
