All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wainer dos Santos Moschetta <wainersm@redhat.com>
To: qemu-devel@nongnu.org
Cc: willianr@redhat.com, alex.bennee@linaro.org, thuth@redhat.com,
	philmd@redhat.com, crosa@redhat.com
Subject: [PATCH 0/3] gitlab-ci: Refactor show logs code and archive logs
Date: Fri, 11 Dec 2020 15:38:24 -0300	[thread overview]
Message-ID: <20201211183827.915232-1-wainersm@redhat.com> (raw)

Since the Travis CI time, it has carried (commit 67892c9537d9ac500934) a python
code to print the logs of acceptance tests in case of fail. Recently Avocado
released a new plug-in (called "testlogs") which allow us to configure the
framework to show the logs of tests which finished with a given status. For
example, print the logs of tests which FAIL or CANCEL. This series is about
replacing the old implementation by that native Avocado feature, on the
GitLab CI.

I took that opportunity to also introduce a change in the configuration
to archive the tests results files on GitLab CI for 2 days, regarless the
job failed or not. If the logs are important enough to retain them, it is
possible to do so by clicking on a 'Keep' button on UI; or you can simply
download it to your workstation.

Here is an example of job that succeed:
https://gitlab.com/wainersm/qemu/-/jobs/905873563

And its results files can be found at:
https://gitlab.com/wainersm/qemu/-/jobs/905873563/artifacts/browse/build/tests/results/latest/test-results/

Then an example of job that failed (I changed a test, forcing its fail):
https://gitlab.com/wainersm/qemu/-/jobs/906089498

[1] https://github.com/avocado-framework/avocado/issues/4266

Wainer dos Santos Moschetta (3):
  tests/acceptance: Bump avocado requirements to 83.0
  gitlab-ci: Refactor code that show logs of failed acceptances
  gitlab-ci: Archive logs of acceptance tests

 .gitlab-ci.yml         | 7 ++++++-
 tests/requirements.txt | 2 +-
 2 files changed, 7 insertions(+), 2 deletions(-)

-- 
2.28.0



             reply	other threads:[~2020-12-11 19:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11 18:38 Wainer dos Santos Moschetta [this message]
2020-12-11 18:38 ` [PATCH 1/3] tests/acceptance: Bump avocado requirements to 83.0 Wainer dos Santos Moschetta
2020-12-14 20:48   ` Willian Rampazzo
2020-12-11 18:38 ` [PATCH 2/3] gitlab-ci: Refactor code that show logs of failed acceptances Wainer dos Santos Moschetta
2020-12-14 20:53   ` Willian Rampazzo
2020-12-11 18:38 ` [PATCH 3/3] gitlab-ci: Archive logs of acceptance tests Wainer dos Santos Moschetta
2020-12-17 12:48   ` Thomas Huth
2020-12-17 13:36   ` Willian Rampazzo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201211183827.915232-1-wainersm@redhat.com \
    --to=wainersm@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=crosa@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=willianr@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.