From: Cleber Rosa <crosa@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Thomas Huth" <thuth@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Willian Rampazzo" <wrampazz@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Beraldo Leal" <bleal@redhat.com>
Subject: [PATCH 2/3] Acceptance tests: do not show canceled test logs on GitLab CI
Date: Fri, 9 Oct 2020 16:55:12 -0400 [thread overview]
Message-ID: <20201009205513.751968-3-crosa@redhat.com> (raw)
In-Reply-To: <20201009205513.751968-1-crosa@redhat.com>
Tests resulting in "CANCEL" in Avocado are usually canceled on
purpose, and are almost identical to "SKIP". The logs for canceled
tests are adding a lot of noise to the logs being shown on GitLab CI,
and causing distraction from real failures.
As a side note, this "after script" is scheduled for removal once the
feature is implemented within Avocado itself.
Reference: https://github.com/avocado-framework/avocado/issues/4266
Signed-off-by: Cleber Rosa <crosa@redhat.com>
---
.gitlab-ci.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index a51c89554f..bed5fe6161 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -63,7 +63,7 @@ include:
fi
after_script:
- 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")]' | xargs cat
+ - 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
build-system-ubuntu:
--
2.25.4
next prev parent reply other threads:[~2020-10-09 20:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 20:55 [PATCH 0/3] Acceptance Tests: improve usage on GitLab CI Cleber Rosa
2020-10-09 20:55 ` [PATCH 1/3] Acceptance tests: bump pycdlib version for easier installation Cleber Rosa
2020-10-10 7:36 ` Philippe Mathieu-Daudé
2020-10-10 7:36 ` [Bug 1897783] " Philippe Mathieu-Daudé
2020-10-12 1:16 ` Cleber Rosa
2020-10-19 16:02 ` Willian Rampazzo
2020-10-19 16:02 ` [Bug 1897783] " Willian Rampazzo
2020-10-09 20:55 ` Cleber Rosa [this message]
2020-10-10 9:10 ` [PATCH 2/3] Acceptance tests: do not show canceled test logs on GitLab CI Philippe Mathieu-Daudé
2020-10-09 20:55 ` [PATCH 3/3] Acceptance tests: show test report " Cleber Rosa
2020-10-10 9:11 ` Philippe Mathieu-Daudé
2020-10-12 13:09 ` Alex Bennée
2020-10-12 21:18 ` Cleber Rosa
2020-10-12 10:32 ` [PATCH 0/3] Acceptance Tests: improve usage " Thomas Huth
-- strict thread matches above, loose matches on Subject: below --
2020-09-29 18:09 [Bug 1897783] [NEW] avocado tests not running on aarch64 host Philippe Mathieu-Daudé
2020-09-29 19:27 ` [Bug 1897783] " Philippe Mathieu-Daudé
2020-09-29 20:37 ` Cleber Rosa
2020-09-29 20:46 ` Cleber Rosa
2020-09-29 20:52 ` Cleber Rosa
2020-10-09 21:01 ` Cleber Rosa
2020-12-10 9:05 ` Thomas Huth
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=20201009205513.751968-3-crosa@redhat.com \
--to=crosa@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=ehabkost@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
--cc=wrampazz@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).