From owner-freebsd-testing@FreeBSD.ORG Thu Jul 3 00:39:29 2014 Return-Path: Delivered-To: freebsd-testing@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 60DBE517; Thu, 3 Jul 2014 00:39:29 +0000 (UTC) Received: from mail-lb0-x22b.google.com (mail-lb0-x22b.google.com [IPv6:2a00:1450:4010:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9B23725A8; Thu, 3 Jul 2014 00:39:28 +0000 (UTC) Received: by mail-lb0-f171.google.com with SMTP id s7so8634774lbd.30 for ; Wed, 02 Jul 2014 17:39:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=HNxRmsXMzm6GuOULk4Odl0ysi4i85WbHkSs47yobMXA=; b=euhPyuSQeTVN+yvpa3eHqNjMQZVZit5kthAotLwngVsgXoxYDSl1fvUeHfVu6UUeyD LnqKNE7qIxODVrI/C4NiMVfr5d7CHWpq3ao486Adb+e5f4P4O68mZymcnq5nOuwrF23n vBzyCwIk0wDTnrMBWgIgBbtRXBBN9jNLmNGQuouvxf8wvb70o5DZjHzFwTF1zsc7ttEd am93p0X6tQZ9rsueBnDwpcOvi7RROx76E+EEb9qNnHBR3i6q+F0O44OT8UaUN3ANgPkj 1z89HEwSFcV7PCagkrE15l8BolibcQvYybZGuosAoq9txNqZiXL0YWvWi70XRbixyG2a F45g== MIME-Version: 1.0 X-Received: by 10.112.97.202 with SMTP id ec10mr902439lbb.20.1404347966382; Wed, 02 Jul 2014 17:39:26 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.67.71 with HTTP; Wed, 2 Jul 2014 17:39:26 -0700 (PDT) In-Reply-To: References: Date: Wed, 2 Jul 2014 17:39:26 -0700 X-Google-Sender-Auth: zt-zJSIKCTuuP7L-FhG_UDkJmyo Message-ID: Subject: Re: Kyua + Jenkins integration From: Craig Rodrigues To: Julio Merino Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18 Cc: "freebsd-testing@freebsd.org" , "jenkins-admin@freebsd.org" 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: Thu, 03 Jul 2014 00:39:29 -0000 Hi, OK, thanks for the explanation. It would be useful if the reporting options had a flag to direct output to a file: kyua report-junit -o foo.xml instead of: kyua report-junit > foo.xml However, without the "-o" flag, I can still live with it. Can you do another release of kyua with this change, and maybe Garrett's TAP fixes? What you have done is very useful, and I want to deploy it on multiple machines via "pkg install" instead of downloading the source and building it myself. Thanks. -- Craig On Fri, Jun 27, 2014 at 8:44 AM, Julio Merino wrote: > On Mon, Jun 16, 2014 at 4:59 PM, Craig Rodrigues > wrote: > > On Wed, Jun 11, 2014 at 3:23 AM, Julio Merino wrote: > >> > >> > https://github.com/jmmv/kyua/commit/7acd1a1fa05e600ac41094857ee1344f4ae7adb5 > >> > > > > By default, "kyua report-html" will write output files in the ./html > directory, > > unless overridden by "--output [directory]". > > However, "kyua report-junit" seems to write output files to stdout > > instead by default. > > > > You might want to make the default behavior of "kyua report-junit" by > closer > > to "kyua report-html", i.e. do not write the output files to stdout by > default. > > This is intentional and is part of the reason why every output format > has its own command: their behaviors are different and attempting to > represent them with the same command-line interface would be more > confusing. The HTML output generates more than one file so it cannot > write to stdout. But that's the exception, not the norm: both report > and report-junit generate single files and print them to stdout. > > The plan is to make report-html write a single file by default (with > an option for chunked output) and write that to stdout. Other than for > consistency reasons, this would resolve some of the concerns with the > current HTML output (aka harder to manage than atf's due to the > multi-file setup.) >