We're currently facing the problem that the gitlab-CI jobs for the
shared runners take too much of the limited CI minutes on gitlab.com.
Here are now some patches that optimize some of the jobs a little bit
to take less runtime. We slightly lose some test coverage by some of
these changes (e.g. by dropping ppc-softmmu from a Clang-based test
and only continue testing ppc64-softmmu with Clang in another job),
but that should still be much better than running out of CI minutes
after 3/4 of a month.

Thomas Huth (6):
  gitlab-ci.d/buildtest: Remove ppc-softmmu from the clang-system job
  gitlab-ci.d/buildtest: Remove aarch64-softmmu from the
    build-system-ubuntu job
  tests/qtest/display-vga-test: Add proper checks if a device is
    available
  gitlab-ci.d/buildtest: Merge the --without-default-* jobs
  gitlab-ci.d/buildtest: Merge the two gprof-gcov jobs
  gitlab-ci.d/buildtest: Disintegrate the build-coroutine-sigaltstack
    job

 tests/qtest/display-vga-test.c | 65 +++++++++++++---------------------
 .gitlab-ci.d/buildtest.yml     | 51 ++++++--------------------
 .gitlab-ci.d/crossbuilds.yml   |  2 +-
 3 files changed, 37 insertions(+), 81 deletions(-)

-- 
2.31.1

On 30/1/23 11:44, Thomas Huth wrote:
> We're currently facing the problem that the gitlab-CI jobs for the
> shared runners take too much of the limited CI minutes on gitlab.com.
> Here are now some patches that optimize some of the jobs a little bit
> to take less runtime. We slightly lose some test coverage by some of
> these changes (e.g. by dropping ppc-softmmu from a Clang-based test
> and only continue testing ppc64-softmmu with Clang in another job),
> but that should still be much better than running out of CI minutes
> after 3/4 of a month.

FWIW the last time I wanted to add some tests Alex suggested me to
run a before/after gcov report and justify the new path tested.

Maybe we should enforce something similar, either cover new paths
or fix a bug.