We lately realized that the Avocado framework was not designed to be regularly run on CI environments. Therefore, as of 5.2 we deprecate the gitlab-ci jobs using Avocado. To not disrupt current users, it is possible to keep the current behavior by setting the QEMU_CI_INTEGRATION_JOBS_PRE_5_2_RELEASE variable (see [*]). >From now on, using these jobs (or adding new tests to them) is strongly discouraged.
Tests based on Avocado will be ported to new job schemes during the next releases, with better documentation and templates. [*] https://docs.gitlab.com/ee/ci/variables/README.html#create-a-custom-variable-in-the-ui Signed-off-by: Philippe Mathieu-Daudé <phi...@redhat.com> --- .gitlab-ci.yml | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index d0173e82b16..2674407cd13 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -66,6 +66,15 @@ include: - cd build - python3 -c 'import json; r = json.load(open("tests/results/latest/results.json")); [print(t["logfile"]) for t in r["tests"] if t["status"] not in ("PASS", "SKIP", "CANCEL")]' | xargs cat - du -chs ${CI_PROJECT_DIR}/avocado-cache + rules: + # As of QEMU 5.2, Avocado is not yet ready to run in CI environments, therefore + # the jobs based on this template are not run automatically (except if the user + # explicitly sets the QEMU_CI_INTEGRATION_JOBS_PRE_5_2_RELEASE environment + # variable). Adding new jobs on top of this template is strongly discouraged. + - if: $QEMU_CI_INTEGRATION_JOBS_PRE_5_2_RELEASE == null + when: manual + allow_failure: true + - when: always build-system-ubuntu: <<: *native_build_job_definition -- 2.26.2
