From: NeilBrown <neilb@suse.de>
To: g.esp@free.fr
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH 1/3] Align FAILED to test name to be parsable
Date: Mon, 12 Nov 2012 16:48:56 +1100 [thread overview]
Message-ID: <20121112164856.3a4da5ab@notabene.brown> (raw)
In-Reply-To: <975144635.322922429.1350981075121.JavaMail.root@zimbra33-e6.priv.proxad.net>
[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]
On Tue, 23 Oct 2012 10:31:15 +0200 (CEST) g.esp@free.fr wrote:
>
>
> ----- Mail original -----
> > De: "NeilBrown" <neilb@suse.de>
> > À: "g esp" <g.esp@free.fr>
> > Cc: linux-raid@vger.kernel.org
> > Envoyé: Mardi 23 Octobre 2012 00:23:56
> > Objet: Re: [PATCH 1/3] Align FAILED to test name to be parsable
> >
> > On Mon, 22 Oct 2012 10:31:23 +0200 (CEST) g.esp@free.fr wrote:
> >
> ...
> > I've change the patch description and removed the change to the failed
> > message, because I don't want the log to appear in-line:
> >
> When using an automated build system (like I do in the linux from sources way), usually the last action is to remove the package source that was just build. So that would remove any log needed to check the reasons of the failures.
>
> coreutils, after the test suite end, add all logs for failed and skipped tests.
> I think this is a good compromise.
>
> Did you want that sort of behavior?
I wouldn't object to it as an option. --errors-in-line or something.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2012-11-12 5:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 16:03 [PATCH 1/3] Align FAILED to test name to be parsable Gilles Espinasse
2012-10-21 22:08 ` NeilBrown
2012-10-22 8:31 ` g.esp
2012-10-22 22:23 ` NeilBrown
2012-10-23 8:31 ` g.esp
2012-11-12 5:48 ` NeilBrown [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=20121112164856.3a4da5ab@notabene.brown \
--to=neilb@suse.de \
--cc=g.esp@free.fr \
--cc=linux-raid@vger.kernel.org \
/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).