mirror of
https://github.com/xemu-project/xemu.git
synced 2024-12-25 05:15:28 +00:00
f56bf4caf7
Due to a design problem and misunderstanding between the Avocado framework and QEMU, Avocado is fetching many asset artifacts it shouldn't be fetching, exhausting the jobs CI timeout. Since Avocado artifacts are cached, this is not an issue with old forks, which already have populated the cache and do not need to download new artifacts to run the tests. However this is very confusing to new contributors who start to fork the project and keep having failing CI pipelines. As a temporary kludge, add the QEMU_CI_AVOCADO_TESTING variable to allow old forks to keep running the Avocado tests, while still allowing new forks to use the mainstream set of CI tests. Keep the tests enabled by default on the mainstream namespace which is old enough to have a populated cache, hoping we will keep this cache long enough until the Avocado/QEMU design issue is fixed. Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org> Reviewed-by: Alex Bennée <alex.bennee@linaro.org> Message-Id: <20210525082556.4011380-9-f4bug@amsat.org>
40 lines
1.5 KiB
YAML
40 lines
1.5 KiB
YAML
#
|
|
# This is the GitLab CI configuration file for the mainstream QEMU
|
|
# project: https://gitlab.com/qemu-project/qemu/-/pipelines
|
|
#
|
|
# !!! DO NOT ADD ANY NEW CONFIGURATION TO THIS FILE !!!
|
|
#
|
|
# Only documentation or comments is accepted.
|
|
#
|
|
# To use a different set of jobs than the mainstream QEMU project,
|
|
# you need to set the location of your custom yml file at "custom CI/CD
|
|
# configuration path", on your GitLab CI namespace:
|
|
# https://docs.gitlab.com/ee/ci/pipelines/settings.html#custom-cicd-configuration-path
|
|
#
|
|
# ----------------------------------------------------------------------
|
|
#
|
|
# QEMU CI jobs are based on templates. Some templates provide
|
|
# user-configurable options, modifiable via configuration variables.
|
|
#
|
|
# These variables can be set globally in the user's CI namespace
|
|
# setting:
|
|
# https://docs.gitlab.com/ee/ci/variables/#create-a-custom-variable-in-the-ui
|
|
# or set manually each time a branch/tag is pushed, as a git-push
|
|
# command line argument:
|
|
# https://docs.gitlab.com/ee/user/project/push_options.html#push-options-for-gitlab-cicd
|
|
#
|
|
# Example setting the QEMU_CI_EXAMPLE_VAR variable:
|
|
#
|
|
# git push -o ci.variable="QEMU_CI_EXAMPLE_VAR=value" myrepo mybranch
|
|
#
|
|
# ----------------------------------------------------------------------
|
|
#
|
|
# List of environment variables that can be use to modify the set
|
|
# of jobs selected:
|
|
#
|
|
# - QEMU_CI_AVOCADO_TESTING
|
|
# If set, tests using the Avocado framework will be run
|
|
|
|
include:
|
|
- local: '/.gitlab-ci.d/qemu-project.yml'
|