From owner-freebsd-testing@FreeBSD.ORG Sat Jul 26 08:58:48 2014 Return-Path: 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 63B113BD; Sat, 26 Jul 2014 08:58:48 +0000 (UTC) Received: from smtprelay04.ispgateway.de (smtprelay04.ispgateway.de [80.67.31.31]) (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 2137C2640; Sat, 26 Jul 2014 08:58:47 +0000 (UTC) Received: from [87.79.198.227] (helo=fabiankeil.de) by smtprelay04.ispgateway.de with esmtpsa (SSLv3:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1XAxoM-0003bW-G3; Sat, 26 Jul 2014 10:58:38 +0200 Date: Sat, 26 Jul 2014 10:58:41 +0200 From: Fabian Keil To: Subject: Re: Missing atf-check output: example:failing_test -> failed: atf-check failed; see the output of the test for details Message-ID: <450da50a.02ce9897@fabiankeil.de> In-Reply-To: References: <5ee51891.12b049e9@fabiankeil.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/AWhD6yk+bxIyBTkCdiIncNH"; 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jul 2014 08:58:48 -0000 --Sig_/AWhD6yk+bxIyBTkCdiIncNH Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Alan Somers wrote: > On Fri, Jul 25, 2014 at 12:55 PM, Fabian Keil > wrote: > > I'm currently evaluating using kyua to test a FreeBSD-specific > > shell script, however I'm having trouble analysing failing tests. [...] > > I get: > > > > | fk@r500 ~/git/zogftw/tests $kyua --loglevel debug test -k Kyuafile ex= ample:failing_test > > | example:failing_test -> failed: atf-check failed; see the output of= the test for details [0.150s] > > | > > | 0/1 passed (1 failed) > > | Committed action 21 > > > > The test failure obviously is expected, but I'm missing the referenced > > "output of the test". The relevant log excerpt: [...] > > I'm looking for something like this: > > > > | fk@r500 ~ $/usr/local/libexec/atf-check -s exit:1 -o empty -e empty '= true' > > | Executing command [ true ] > > | Fail: incorrect exit status: 0, expected: 1 > > | stdout: > > | > > | stderr: > > | > > > > I didn't read all the docs available yet and I may be missing something, > > but seeing test failures is something I'd expect to work out of the box. > > Can someone familiar with kyua confirm that this is working as expected? > The test output is stored in Kyua's sqlite database. There are two > ways to see it: > 1) Run " kyua report-html" > 2) Sometimes its easier just to rerun the testcase in debug mode. Do > "kyua debug example:failing_test" Thanks a lot. Not showing test failures on the cli by default seems like a strange design decision to me, but I guess I'll get used to it or write a wrapper script that calls kyua debug for all tests. Fabian --Sig_/AWhD6yk+bxIyBTkCdiIncNH Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlPTbcEACgkQBYqIVf93VJ0RJQCglUy3nhQHeMLYPongYIgze9xk V7wAnAvNpRLqUrd9QrfQtUhjbdW8RgG/ =2/jp -----END PGP SIGNATURE----- --Sig_/AWhD6yk+bxIyBTkCdiIncNH--