From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH 1/4] .gitlab-ci.yml: save rootfs as artifact for runtime tests
Date: Mon, 31 Jul 2017 21:24:07 +0200 [thread overview]
Message-ID: <20170731212407.02a7b111@windsurf.home> (raw)
In-Reply-To: <20170730044946.11999-1-ricardo.martincoski@gmail.com>
Hello,
On Sun, 30 Jul 2017 01:49:43 -0300, Ricardo Martincoski wrote:
> Sometimes when a test fails in a gitlab pipeline the reason of the
> failure cannot be determined using only the logfile.
>
> Add the modified rootfs as an artifact of the job to improve
> troubleshooting. To accomplish this, always use -k option from the test
> infra, unconditionally add the resulting images to the artifacts, and
> let the runner do the cleanup for us.
>
> These artifacts can also be useful when a test fails locally but pass at
> gitlab runners.
>
> When the test does not generate a image, this message is displayed in
> the runner log:
> WARNING: test-output/*/images/*: no matching files
>
> Cc: Arnout Vandecappelle <arnout@mind.be>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com>
> ---
> See also
> http://lists.busybox.net/pipermail/buildroot/2017-July/199332.html
> ---
> .gitlab-ci.yml | 5 ++++-
> .gitlab-ci.yml.in | 5 ++++-
> 2 files changed, 8 insertions(+), 2 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2017-07-31 19:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-30 4:49 [Buildroot] [RFC PATCH 1/4] .gitlab-ci.yml: save rootfs as artifact for runtime tests Ricardo Martincoski
2017-07-30 4:49 ` [Buildroot] [RFC PATCH 2/4] support/testing: allow to use extra large timeouts Ricardo Martincoski
2017-07-31 19:25 ` Thomas Petazzoni
2017-07-31 23:27 ` Ricardo Martincoski
2017-08-01 6:01 ` Thomas Petazzoni
2017-08-05 2:05 ` [Buildroot] [PATCH v2 1/2] support/testing: allow to use a multiplier for timeouts Ricardo Martincoski
2017-08-05 2:05 ` [Buildroot] [PATCH v2 2/2] .gitlab-ci.yml: use large timeouts for runtime tests Ricardo Martincoski
2017-08-10 9:18 ` [Buildroot] [PATCH v2 1/2] support/testing: allow to use a multiplier for timeouts Arnout Vandecappelle
2017-07-30 4:49 ` [Buildroot] [RFC PATCH 3/4] .gitlab-ci.yml: use large timeouts for runtime tests Ricardo Martincoski
2017-07-30 4:49 ` [Buildroot] [RFC PATCH 4/4] testing/infra/emulator: remove qemu warnings about audio Ricardo Martincoski
2017-07-31 19:26 ` Thomas Petazzoni
2017-07-31 19:24 ` Thomas Petazzoni [this message]
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=20170731212407.02a7b111@windsurf.home \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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