From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] support/testing: add test of BR2_CCACHE with an external toolchain
Date: Tue, 25 Jul 2017 09:03:48 +0200 [thread overview]
Message-ID: <20170725090348.5d073604@windsurf.lan> (raw)
In-Reply-To: <86ba6b0f-662b-ebd9-868f-a422e46821cc@mind.be>
Hello,
On Tue, 25 Jul 2017 00:54:30 +0200, Arnout Vandecappelle wrote:
> > You don't need to list all tests in there, if you want to execute all
> > of them.i
>
> I think Thomas first implemented it that way. But then gitlab-CI just reports a
> single pass/fail for the entire test suite, without details about what failed.
> AFAIK gitlab-CI reporting doesn't have xUnit integration that could be used to
> report detailed results from a single run.
I didn't implement it in a single pass, simply because I knew I wanted
Gitlab CI to show the breakdown per test, and not a global pass/fail
status. But Arnout's explanation remains true: if we simply do
a "./support/testing/run-tests -a", then we would have a single entry
in the Gitlab CI report that says if the entire test suite has passed
or fail. I believe the current situation, where each test is known as a
separate "thing" by Gitlab CI is better.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-07-25 7:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 16:35 [Buildroot] [git commit] support/testing: add test of BR2_CCACHE with an external toolchain Thomas Petazzoni
2017-07-24 17:54 ` Yann E. MORIN
2017-07-24 22:54 ` Arnout Vandecappelle
2017-07-25 7:03 ` 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=20170725090348.5d073604@windsurf.lan \
--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 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.