| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
In particular, not building the tests should
help cutting down on time spent linking.
|
|
|
|
|
|
| |
We currently run the testsuite against x11 in both
the debug and release builds. Once ought to
be enough.
|
|
|
|
|
|
|
|
|
|
| |
The fedora-x86-64 build does not only build with debug,
it also does the hello build, and it runs the testsuite
multiple times.
Move the hello build to the fedora release build. The idea
is that this lets us do more work in parallel, and spend
less time waiting for the longest-running ci job.
|
|
|
|
|
|
|
| |
We are ignoring failures here, and nobody is working
on fixing them. And the failures end up at the end
of the log, adding annoyance to finding the actual
failures.
|
| |
|
|
|
|
|
|
| |
We don't really need to have two full separate
test runs for these conditions, so combine them
into one test setup.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
And its buddy, wireplumber.
But we don't need gnome-desktop-testing
anymore, now that installed tests are gone.
|
|
|
|
|
| |
This is just duplicating all our test runs,
for no discernible gain.
|
|
|
|
|
| |
This is in preparation for trying to use mutter --headless
in ci.
|
| |
|
| |
|
|
|
|
| |
Rename the 'waylandgles' test setup to 'wayland_gles'.
|
| |
|
|
|
|
|
| |
Refresh the Fedora base (still at 37), and add the Python packaging
module for gi-docgen.
|
| |
|
|
|
|
| |
Close GNOME/gtk#5594
|
|
|
|
| |
It's more flexible and allows us to combine the flatpak jobs
|
|
|
|
|
| |
We don't use it most of the time and it's also confusing to new contributors who think it's important to fix it.
Keep it for manual runs, so that interested people can just click a button to see the results. It also makes it easy to turn back on later.
|
|
|
|
|
|
| |
It fails because of address sanitizer crashes,
and takes a long time. It is not that useful
in this shape.
|
|\
| |
| |
| |
| | |
Add a build-testsuite option
See merge request GNOME/gtk!5419
|
| |
| |
| |
| |
| | |
Don't build demos and tests, and only build
the testsuite where we want to run it.
|
|/
|
|
|
|
|
| |
The build is error-free and we want to keep it that way.
We'd also like to make Timm do real work instead of having to fix clang
warnings all the time and this build is a clang build.
|
|
|
|
| |
Would be nice if meson had a nicer way of doing this, but...
|
|
|
|
| |
It is required, so lets not rely on defaults.
|
|
|
|
| |
It appears that f16c crashes asan instantly.
|
|
|
|
|
| |
It fails too often, and it never does us
any good.
|
|
|
|
| |
We're downloading them anyway.
|
|
|
|
|
|
|
| |
Installed tests require access to the system prefix, and thus a
system-wide installation of Meson, which we don't have.
We're going to restore this job at a later date.
|
| |
|
|
|
|
|
| |
Otherwise we're not actually updating anything. `meson subprojects
download` will skip subprojects that already exist.
|
| |
|
|
|
|
|
| |
Avoid using `sudo` in the installed-tests CI job, since we're installing
Meson as the current user.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
meson setup:
configuration
meson compile:
compilation
meson install
installation
Do not use ninja directly, and do not use `meson` as a synonym for
`meson setup`.
|
|
|
|
|
| |
We use the latest 0.64 even if we depend on 0.60 because of fixes in the
subproject command.
|
|
|
|
|
| |
Updating the subprojects will apparently fail if they haven't been
downloaded.
|
|
|
|
|
|
|
|
| |
The python3-toml package is deprecated, and replaced by python3-tomli.
At least, until we bump up the dependency to Fedora 37: then we can
depend on Python 3.11, and its TOML parser in the standard library.
See also: https://gitlab.gnome.org/GNOME/gi-docgen/-/merge_requests/168
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are two possible interpretations of "expected failure": either
the test *must* fail (exactly the inverse of an ordinary test, with
success becoming failure and failure becoming success), or the test
*may* fail (with success intended, but failure possible in some
environments). Autotools had the second interpretation, which seems
more useful in practice, but Meson has the first.
Instead of using should_fail, we can put the tests in one of two new
suites: "flaky" is intended for tests that succeed or fail unpredictably
according to the test environment or chance, while "failing" is for
tests that ought to succeed but currently never do as a result of a
bug or missing functionality. With a sufficiently new version of Meson,
the flaky and failing tests are not run by default, but can be requested
by running a setup that does not exclude them, with a command like:
meson test --setup=x11_unstable --suite=flaky --suite=failing
As a bonus, now that we're setting up setups and their excluded suites
programmatically, the gsk-compare-broadway tests are also excluded by
default when running the test setup for a non-broadway backend.
When running the tests in CI, --suite=gtk overrides the default
exclude_suites, so we have to specify --no-suite=flaky and
--no-suite=failing explicitly.
This arrangement is inspired by GNOME/glib!2987, which was contributed
by Marco Trevisan.
Signed-off-by: Simon McVittie <smcv@debian.org>
|
| |
|
|
|
|
|
|
| |
It seems that libjpeg-turbo first finds nasm,
and then doesn't find it. Turn off simd to keep
it from looking for it in the first place.
|
|
|
|
|
| |
The runner seems busted, so allow builds to fail
for now.
|
|
|
|
| |
Drop the `.pre` phase.
|
|
|
|
| |
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
|
|
|
|
|
|
|
|
|
| |
CI is mostly interested in GTK not introducing compiler warnings, other
submodules like Wayland might have their own and that shouldn't hinder
CI testing of GTK.
Disable -Werror for the wayland submodule, and let it be fixed independently
at some point.
|
|\
| |
| |
| |
| | |
flatpak: add a NodeEditor demo
See merge request GNOME/gtk!4898
|
| | |
|