| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
Otherwise we're going to need an AT-SPI service on the session, and the
accessibility bus.
|
|
|
|
|
|
| |
Using sysprof and glib as subprojects of the same
project sadly does not work. Subprojects are not
as robust as they should be.
|
|
|
|
|
|
| |
It turns out that the sysprof meson setup does not
work with meson 0.54 :( So version 25 of our ci images
bumps the meson version to 0.55.3.
|
|
|
|
|
|
| |
meson adds features that then trigger warnings when we run
a newer meson over some of our subprojects. This is all too
fragile.
|
|
|
|
|
| |
We wanted to enable werror for gtk without enabling it
for all our subprojects. Sadly, we failed. Try again
|
|
|
|
| |
These images have meson 0.54.
|
|
|
|
|
|
|
| |
Yielding option means that if pango is built as a subproject, it will
take the value of that option from the parent project (e.g. gst-build).
For that to work it must be of the same type, which is "feature" instead
of "boolean" in all GStreamer modules.
|
|
|
|
|
|
|
|
| |
I added libcloudproviders to the base image, but
now I see that we already enabled libcloudproviders
in the build anyway, so I'm a bit confused.
Fixes: #2480
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use feature options for things that are optional features,
update the docs.
Visible changes here is that the 'print-backends' option
got renamed to 'print' to go better with 'media', and the
'tracker3' option got renamed to 'tracker'.
For options that have been changed into features, the
syntax now is -Dfeature=enabled or -Dfeature=disabled
or -Dfeature=auto.
|
|
|
|
|
|
|
| |
We don't support any profilers other than sysprof,
so name the option accordingly. While we are at it,
change it to a meson feature option, so
-Dprofiler=true becomes -Dsysprof=enabled
|
|
|
|
|
| |
Otherwise, we end up stuck on old checkouts, and
bumping requirements lets to build failures.
|
|
|
|
|
| |
This will hopefully prevent regressions in
installed-tests.
|
|
|
|
| |
v22 adds gnome-desktop-testing-runner and enables sudo.
|
|
|
|
|
|
| |
Try to teach meson not to build our subprojects with
-Werror, since that is just insane, and exposes us
to random build failures in subprojects.
|
|
|
|
|
| |
Some jobs can run out of order, as they are entirely self-contained. If
we use the newly added DAG attributes, we can speed up the CI pipeline.
|
| |
|
|
|
|
| |
We do have some slow tests.
|
|
|
|
|
|
|
|
|
| |
Run our testsuite under asan. We do this in a
separate build, since we need to turn off
introspection to make the build succeed.
As Michael Catanzaro pointed out, this requires a
privileged runner in order to use kernel apis.
|
|
|
|
| |
This image includes libasan and libubsan.
|
|
|
|
|
| |
We ended up breaking the build when it's enabled, so we should test the
feature in our CI pipeline.
|
|
|
|
| |
So we don't have to copy them around.
|
|
|
|
|
|
| |
Currently we have to hunt all the `image` keys when updating the image
in use for a job. We should centralise them all at the top of the file,
so they are easy to update in one simple change.
|
|
|
|
|
| |
64 bit is more common now and also tests more things because
sizeof(glong) != sizeof(gpointer)
|
|
|
|
|
| |
Our doc build now uses pandoc, so use an image
that has it.
|
|
|
|
|
| |
The `extends` keyword is more readable than YAML's weird anchor syntax,
and we don't have too many anchors in our job definitions anyway.
|
|
|
|
|
|
| |
Run the testsuite under x11, wayland and broadway
in the fedora-x86_64 job. This requires us to use
the v17 image which includes weston.
|
|
|
|
|
|
|
|
| |
It doesn't understand the powershell syntax which leads to the cache
key being empty which leads to cache restore being skipped
which leads to slow builds not using ccache.
See https://gitlab.com/gitlab-org/gitlab-runner/-/issues/2747
|
|
|
|
|
|
|
| |
They use powershell instead of cmd.exe, use the tag win32-ps instead of win32,
and run Windows 2016 instead of 2012r2.
The old runners will be switched off in the comming weeks.
|
|
|
|
| |
Needed for !1017.
|
| |
|
|
|
|
|
|
|
| |
Use the Clang static analysis tool.
For the time being, we're going to allow it to fail, but the plan is to
fix every issue it raises.
|
|
|
|
|
| |
We want the style checks running at the start of the CI pipeline, no
need to have a specific phase for it.
|
| |
|
|
|
|
| |
We want to re-use it for other jobs.
|
|
|
|
|
|
| |
Don't build the API reference on deploy; build it in a separate job,
instead, so we can run it on all pipelines, and deploy it only for
master.
|
|
|
|
|
|
|
| |
The CI infrastructure was changed to run with fewer privileges, so we
need to adapt our Flatpak jobs to compensate.
See: https://mail.gnome.org/archives/desktop-devel-list/2020-February/msg00055.html
|
|
|
|
| |
We don't need all the debugging messages.
|
|
|
|
| |
We have more accurate CI jobs, now; the Flatpak jobs are nice to have.
|
|
|
|
|
| |
The tests are now passing in release builds, lets keep
it that way.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
We need to investigate release-specific failures, and possibly fix our
test suite to deal with debug-specific poking through the internal
state.
For the time being, allow the release job to fail, but this is strictly
a temporary measure.
|
|
|
|
|
|
| |
We should at least try to get the style check done by a machine, as
opposed to have humans go through merge requests with coding style
nitpicks.
|
|
|
|
|
|
| |
We are going to need to hide the report generation into the test runner
script, as we want the job to produce the reports even in case of
failure, instead of bailing out immediately.
|
|
|
|
|
|
| |
Now that we figured out why the build was failing on Fedora when the
profiling code was enabled, we can go back to building both shared and
static libraries by default.
|
| |
|
| |
|
|
|
|
|
| |
Sadly, we can't do a static build with the profiling code enabled
because we don't have a static GLib build available.
|
|
|
|
|
| |
They are easier to use and document, and allow us to add new base images
in the future without making a mess.
|