From users-return-3704-apmail-buildr-users-archive=buildr.apache.org@buildr.apache.org Wed Apr 17 03:28:10 2013 Return-Path: X-Original-To: apmail-buildr-users-archive@www.apache.org Delivered-To: apmail-buildr-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B4734FCD3 for ; Wed, 17 Apr 2013 03:28:10 +0000 (UTC) Received: (qmail 4427 invoked by uid 500); 17 Apr 2013 03:28:10 -0000 Delivered-To: apmail-buildr-users-archive@buildr.apache.org Received: (qmail 4207 invoked by uid 500); 17 Apr 2013 03:28:07 -0000 Mailing-List: contact users-help@buildr.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@buildr.apache.org Delivered-To: mailing list users@buildr.apache.org Received: (qmail 4125 invoked by uid 99); 17 Apr 2013 03:28:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Apr 2013 03:28:06 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of peter.j.donald@gmail.com designates 74.125.82.179 as permitted sender) Received: from [74.125.82.179] (HELO mail-we0-f179.google.com) (74.125.82.179) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Apr 2013 03:28:02 +0000 Received: by mail-we0-f179.google.com with SMTP id p43so878678wea.10 for ; Tue, 16 Apr 2013 20:27:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=MHSFoMXOtc6oGboltxrvsMpaf9JMfwqCtk2FlJUjXRU=; b=rW60jR4BbddnHWvf5Qn+e8NxgBIrWCkhuJIeROdx9WIhr9zlB1YlaphLcGVPGerZUj Q38nsRQSHQx3oc5FFyUS8HgAvTLVsoFtZ61zKzpt6bA+H1DiXpwkzXywEaWAyIe4/hU3 wQutf8ujotiGtugimNhTgT0C774bwrfyRPHU9MD+nz2d+hf5V5Bgs7hZZbIRWkV0k+09 8VyouNfkBycPABulMhHUBMEB/Z1Q05O3zSJhEHqXdXqYsdixaQ2vXuSIiuSlWKfE2eHY qTxXswtfulvCQzJOviamxZRfOYHIXZDstXg16YgH6LGR3NtA72EaDnoFqbQSwLrn2BI7 Ua1w== MIME-Version: 1.0 X-Received: by 10.194.82.104 with SMTP id h8mr4270106wjy.3.1366169260757; Tue, 16 Apr 2013 20:27:40 -0700 (PDT) Sender: peter.j.donald@gmail.com Received: by 10.194.43.132 with HTTP; Tue, 16 Apr 2013 20:27:40 -0700 (PDT) In-Reply-To: References: Date: Wed, 17 Apr 2013 13:27:40 +1000 X-Google-Sender-Auth: Ec16geMXgazFeCWo2186sszqcws Message-ID: Subject: Re: switching junit standard output buffering off? From: Peter Donald To: users@buildr.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Apr 16, 2013 at 11:59 PM, Jason Hoogland wrote: > If the jvm during junit tests forks abnormally, standard output won;t be > shown becaused its buffered. Apparently this can be switched off (e.g. > http://comments.gmane.org/gmane.comp.apache.maven.issues/28714, > http://grokbase.com/t/hadoop/zookeeper-user/10b4h71k09/junit-tests-do-not-produce-logs-if-the-jvm-crashes > ). > > Any ideas on whether/how this might be done with buildr? Have you observed buffering in Buildr? I would not have thought this is a problem with the Junit integration built in as it uses the default reports and not any of the ones the buffering. Even if that was the cvase you can pass system properties and jvm parameters to the test JVM that will control this behavior. test.using :properties => {"myvar" => "x"}, :java_args => :{"myvar" => "x"} -- Cheers, Peter Donald