From: Thomas Huth <thuth@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: fam@euphon.net, berrange@redhat.com, f4bug@amsat.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Willian Rampazzo" <willianr@redhat.com>,
stefanha@redhat.com, pbonzini@redhat.com,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
aurelien@aurel32.net
Subject: Re: [PATCH v1 2/6] gitlab-ci: Display Avocado log content when tests timeout
Date: Wed, 17 Feb 2021 14:38:55 +0100 [thread overview]
Message-ID: <e7ab2379-2748-d58c-6bad-0803bf45e20b@redhat.com> (raw)
In-Reply-To: <20210217121932.19986-3-alex.bennee@linaro.org>
On 17/02/2021 13.19, Alex Bennée wrote:
> From: Philippe Mathieu-Daudé <philmd@redhat.com>
>
> Since commit ba2232bae6d ("gitlab-ci: Refactor code that show logs
> of failed acceptances") we display the log content of failing tests
> (Avocado "FAIL" event).
>
> Since we are also interested in tests timeouting, update our global
> Avocado config to display log content for the "INTERRUPT" event,
> "possible when the timeout is reached" (See [*]).
>
> [*] https://avocado-framework.readthedocs.io/en/latest/guides/writer/chapters/writing.html#test-statuses
>
> Suggested-by: Willian Rampazzo <willianr@redhat.com>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> Message-Id: <20210215171438.935665-1-philmd@redhat.com>
> ---
> .gitlab-ci.yml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index 7adb9a4cef..234cead60c 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -64,7 +64,7 @@ include:
> - echo "[datadir.paths]" > ~/.config/avocado/avocado.conf
> - echo "cache_dirs = ['${CI_PROJECT_DIR}/avocado-cache']"
> >> ~/.config/avocado/avocado.conf
> - - echo -e '[job.output.testlogs]\nstatuses = ["FAIL"]'
> + - echo -e '[job.output.testlogs]\nstatuses = ["FAIL", "INTERRUPT"]'
> >> ~/.config/avocado/avocado.conf
> - if [ -d ${CI_PROJECT_DIR}/avocado-cache ]; then
> du -chs ${CI_PROJECT_DIR}/avocado-cache ;
>
Acked-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2021-02-17 13:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 12:19 [PATCH v1 0/6] my current testing/next queue (meson/gitlab/fedora bump) Alex Bennée
2021-02-17 12:19 ` [PATCH v1 1/6] meson.build: expose TCG cross compiler information in summary Alex Bennée
2021-02-17 12:19 ` [PATCH v1 2/6] gitlab-ci: Display Avocado log content when tests timeout Alex Bennée
2021-02-17 13:38 ` Thomas Huth [this message]
2021-02-17 12:19 ` [PATCH v1 3/6] gitlab-ci.yml: Run check-tcg with TCI Alex Bennée
2021-02-17 16:38 ` Philippe Mathieu-Daudé
2021-02-17 17:51 ` Richard Henderson
2021-02-17 12:19 ` [PATCH v1 4/6] docker: Bump Fedora images to release 33 Alex Bennée
2021-02-17 12:19 ` [PATCH v1 5/6] travis.yml: Limit simultaneous jobs to 3 Alex Bennée
2021-02-17 12:19 ` [PATCH v1 6/6] tests/acceptance: allow a "graceful" failing for virtio-gpu test Alex Bennée
2021-02-17 13:20 ` Marc-André Lureau
2021-02-19 15:53 ` 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=e7ab2379-2748-d58c-6bad-0803bf45e20b@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=aurelien@aurel32.net \
--cc=berrange@redhat.com \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=wainersm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).