Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] test-pkg: Extend the logfile with the first command as well
Date: Thu, 9 Mar 2017 21:36:05 +0100	[thread overview]
Message-ID: <20170309213605.20997679@free-electrons.com> (raw)
In-Reply-To: <1489072521-5514-1-git-send-email-benoit.allard@greenbone.net>

Hello,

On Thu,  9 Mar 2017 16:15:21 +0100, Beno?t Allard wrote:
> Signed-off-by: Beno?t Allard <benoit.allard@greenbone.net>
> ---
>  support/scripts/test-pkg | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Thanks, applied.

> diff --git a/support/scripts/test-pkg b/support/scripts/test-pkg
> index a040ce1..0e7779d 100755
> --- a/support/scripts/test-pkg
> +++ b/support/scripts/test-pkg
> @@ -108,7 +108,7 @@ build_one() {
>  	_EOF_
>      cat "${cfg}" >>"${dir}/.config"
>  
> -    if ! make O="${dir}" olddefconfig >/dev/null 2>&1; then
> +    if ! make O="${dir}" olddefconfig > "${dir}/logfile" 2>&1; then

To be honest, I wasn't sure if we wanted > or >> here. It matters if
you restart the test-pkg command after fixing issues. Do you want
logfiles to contain the log of all previous builds, or just the current
build?

For now, I've applied your patch as-is, with just ">", which means the
logfile will only contain the output of the last build. It seems better
to me this way, but we'll see if other folks disagree.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-03-09 20:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-09 15:15 [Buildroot] [PATCH 1/1] test-pkg: Extend the logfile with the first command as well Benoît Allard
2017-03-09 20:36 ` Thomas Petazzoni [this message]
2017-03-09 22:00   ` Yann E. MORIN
2017-03-09 22:02     ` Thomas Petazzoni
2017-03-09 22:05       ` Yann E. MORIN

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=20170309213605.20997679@free-electrons.com \
    --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