From owner-freebsd-testing@FreeBSD.ORG  Tue Jul 29 11:02:18 2014
Return-Path: <owner-freebsd-testing@FreeBSD.ORG>
Delivered-To: freebsd-testing@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 562D9A92
 for <freebsd-testing@freebsd.org>; Tue, 29 Jul 2014 11:02:18 +0000 (UTC)
Received: from smtprelay05.ispgateway.de (smtprelay05.ispgateway.de
 [80.67.31.100])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 0FBCE2ABE
 for <freebsd-testing@freebsd.org>; Tue, 29 Jul 2014 11:02:17 +0000 (UTC)
Received: from [84.44.154.146] (helo=fabiankeil.de)
 by smtprelay05.ispgateway.de with esmtpsa (SSLv3:AES128-SHA:128)
 (Exim 4.68) (envelope-from <freebsd-listen@fabiankeil.de>)
 id 1XC50D-0004ch-9T
 for freebsd-testing@freebsd.org; Tue, 29 Jul 2014 12:51:29 +0200
Date: Tue, 29 Jul 2014 12:51:32 +0200
From: Fabian Keil <freebsd-listen@fabiankeil.de>
To: <freebsd-testing@freebsd.org>
Subject: Re: Missing atf-check output: example:failing_test -> failed:
 atf-check failed; see the output of the test for details
Message-ID: <0d851725.1cb2c6b8@fabiankeil.de>
In-Reply-To: <CAFY7cWAQEvAHeNO-yugneEbsYsntZaEz=ruthSeZ+Xjcz_xbTA@mail.gmail.com>
References: <5ee51891.12b049e9@fabiankeil.de>
 <CAOtMX2j=NMyacDw8gV=N7eS07G5SJ_bL=ktPDDHVGC7QFc9M9A@mail.gmail.com>
 <450da50a.02ce9897@fabiankeil.de>
 <CAOtMX2i6ziW+WqQ2jcRWNesNOFbiat2psEi8bvb0qTb2=93ukg@mail.gmail.com>
 <CAFY7cWAQEvAHeNO-yugneEbsYsntZaEz=ruthSeZ+Xjcz_xbTA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 boundary="Sig_/e/3Qw.AYZnJuEFA_0zR/370"; protocol="application/pgp-signature"
X-Df-Sender: Nzc1MDY3
X-BeenThere: freebsd-testing@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: Testing on FreeBSD <freebsd-testing.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-testing>, 
 <mailto:freebsd-testing-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-testing/>
List-Post: <mailto:freebsd-testing@freebsd.org>
List-Help: <mailto:freebsd-testing-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-testing>, 
 <mailto:freebsd-testing-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2014 11:02:18 -0000

--Sig_/e/3Qw.AYZnJuEFA_0zR/370
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Julio Merino <jmmv@freebsd.org> wrote:

> On Mon, Jul 28, 2014 at 9:11 AM, Alan Somers <asomers@freebsd.org> wrote:
> > On Sat, Jul 26, 2014 at 2:58 AM, Fabian Keil
> > <freebsd-listen@fabiankeil.de> wrote:

> > I don't recommend calling "kyua debug" for all tests.  The best
> > approach is to run "kyua test; kyua report-html <options>".  The HTML
> > report will show you the full stdout and stderr output of each failing
> > test case.
>=20
> We should actually just make "kyua report" show the stdout and stderr,
> and this is easier to do. Having to resort to report-html is... just
> ugly.

Agreed.

> I just haven't thought about a UI for it.  Maybe "kyua report
> --show-output [test cases]" would be good enough?

I'd prefer two options, one that only shows the output for
failing test cases and one that shows the output for all.

Fabian

--Sig_/e/3Qw.AYZnJuEFA_0zR/370
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlPXfLQACgkQBYqIVf93VJ1TFACfWVQe+cFxF4T5MBppBNpJc/gF
VBAAn0EhAAyfXVEtuvgz6EnSjGqL9/dW
=/PR6
-----END PGP SIGNATURE-----

--Sig_/e/3Qw.AYZnJuEFA_0zR/370--