From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26870 invoked by alias); 1 Aug 2013 19:45:07 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 26861 invoked by uid 89); 1 Aug 2013 19:45:07 -0000 X-Spam-SWARE-Status: No, score=-5.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,RDNS_NONE,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.1 Received: from Unknown (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Thu, 01 Aug 2013 19:45:06 +0000 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r71JitKY022479 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 1 Aug 2013 15:44:56 -0400 Received: from barimba (ovpn-113-128.phx2.redhat.com [10.3.113.128]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r71JirfK006807 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 1 Aug 2013 15:44:54 -0400 From: Tom Tromey To: Yao Qi Cc: Subject: Re: [PATCH 2/4] introduce parallel mode References: <1374073124-23602-1-git-send-email-tromey@redhat.com> <1374073124-23602-3-git-send-email-tromey@redhat.com> <51E7E27E.5030800@codesourcery.com> <87txjsc7mw.fsf@fleche.redhat.com> <51E86A71.3000301@codesourcery.com> Date: Thu, 01 Aug 2013 19:45:00 -0000 In-Reply-To: <51E86A71.3000301@codesourcery.com> (Yao Qi's message of "Fri, 19 Jul 2013 06:21:37 +0800") Message-ID: <878v0lfb62.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2013-08/txt/msg00047.txt.bz2 >>>>> "Yao" == Yao Qi writes: Yao> Probably, we can send the output to the log, for example Yao> inotify_[pid].log, and check whether there is something written into Yao> the log in the test somewhere. If there is, emit a FAIL, which would Yao> be more attractive, like: I am not sure about emitting a FAIL. There won't be a corresponding PASS. It would be more noticeable, which is a plus; but in the absence of a conflict it isn't clearly a FAIL-worthy bug -- even after my series we'll have a few of these. So for now I am just teeing the output to the log file: set inotify_pid [exec inotifywait -r -m -e move,create,delete . \ --exclude $exclusion_re \ |& tee -a $outdir/$tool.log &] This way it will show up in on the terminal but also in the log. I'm open to discussion about your idea though. I'm really not sure. Tom