From: Daniel Vetter <daniel@ffwll.ch>
To: Daniel Stone <daniels@collabora.com>
Cc: "Eric Engeström" <eric.engestrom@intel.com>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
dri-devel@lists.freedesktop.org,
"Lucas De Marchi" <lucas.de.marchi@gmail.com>
Subject: Re: [PATCH libdrm] CI: Capture test logs as GitLab artifacts
Date: Thu, 6 Sep 2018 12:38:46 +0200 [thread overview]
Message-ID: <20180906103846.GR4929@phenom.ffwll.local> (raw)
In-Reply-To: <20180906100117.5627-1-daniels@collabora.com>
On Thu, Sep 06, 2018 at 11:01:17AM +0100, Daniel Stone wrote:
> GitLab CI already captures all the stdout/stderr output from the build
> process as the log. However, some other important information is hidden
> in other log files.
>
> Taken from Wayland, capture logs from the configuration process as well
> as from every check.
>
> Signed-off-by: Daniel Stone <daniels@collabora.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@gmail.com>
> Cc: Lucas De Marchi <lucas.de.marchi@gmail.com>
> Cc: Eric Engeström <eric.engestrom@intel.com>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
I think there's also an option to capture all non-tracked files when the
build fails. For the lazy :-) But this looks good too.
Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> ---
> .gitlab-ci.yml | 26 ++++++++++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
> diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
> index eee6abfc..50ec8527 100644
> --- a/.gitlab-ci.yml
> +++ b/.gitlab-ci.yml
> @@ -1,6 +1,29 @@
> +.artifacts-meson: &artifacts-meson
> + when: always
> + paths:
> + - _build/meson-logs
> +
> +.artifacts-autotools: &artifacts-autotools
> + when: always
> + paths:
> + - _build/*.log
> + - _build/amdgpu/*.log
> + - _build/etnaviv/*.log
> + - _build/exynos/*.log
> + - _build/freedreno/*.log
> + - _build/intel/*.log
> + - _build/libkms/*.log
> + - _build/nouveau/*.log
> + - _build/omap/*.log
> + - _build/radeon/*.log
> + - _build/tegra/*.log
> + - _build/tests/*.log
> + - _build/tests/*/*.log
> +
> latest-meson:
> stage: build
> image: base/archlinux:latest
> + artifacts: *artifacts-meson
> before_script:
> - pacman -Syu --noconfirm --needed
> base-devel
> @@ -35,6 +58,7 @@ latest-meson:
> latest-autotools:
> stage: build
> image: base/archlinux:latest
> + artifacts: *artifacts-autotools
> before_script:
> - pacman -Syu --noconfirm --needed
> base-devel
> @@ -69,6 +93,7 @@ latest-autotools:
> oldest-meson:
> stage: build
> image: debian:stable
> + artifacts: *artifacts-meson
> before_script:
> - printf > /etc/dpkg/dpkg.cfg.d/99-exclude-cruft "%s\n"
> 'path-exclude=/usr/share/doc/*'
> @@ -125,6 +150,7 @@ oldest-meson:
> oldest-autotools:
> stage: build
> image: debian:stable
> + artifacts: *artifacts-autotools
> before_script:
> - printf > /etc/dpkg/dpkg.cfg.d/99-exclude-cruft "%s\n"
> 'path-exclude=/usr/share/doc/*'
> --
> 2.19.0.rc0
>
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-09-06 10:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 10:01 [PATCH libdrm] CI: Capture test logs as GitLab artifacts Daniel Stone
2018-09-06 10:38 ` Daniel Vetter [this message]
2018-09-06 15:39 ` Sean Paul
2018-09-06 11:02 ` Eric Engestrom
2018-09-06 13:44 ` Emil Velikov
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=20180906103846.GR4929@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@ffwll.ch \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric.engestrom@intel.com \
--cc=lucas.de.marchi@gmail.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