From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dan.rpsys.net (5751f4a1.skybroadband.com [87.81.244.161]) by mail.openembedded.org (Postfix) with ESMTP id 80A6D756CB for ; Tue, 2 Jun 2015 11:30:51 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id t52BUnT5001438; Tue, 2 Jun 2015 12:30:49 +0100 Received: from dan.rpsys.net ([127.0.0.1]) by localhost (dan.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id p40TYanIPS6b; Tue, 2 Jun 2015 12:30:49 +0100 (BST) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by dan.rpsys.net (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id t52BUag2001435 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT); Tue, 2 Jun 2015 12:30:47 +0100 Message-ID: <1433244636.404.191.camel@linuxfoundation.org> From: Richard Purdie To: "Musat, George L" Date: Tue, 02 Jun 2015 12:30:36 +0100 In-Reply-To: <042E875E1B5D414CA9BB78B7D4FA691C2671384A@IRSMSX107.ger.corp.intel.com> References: <1432898941-1148-1-git-send-email-george.l.musat@intel.com> <1433021213.404.150.camel@linuxfoundation.org> <042E875E1B5D414CA9BB78B7D4FA691C2671384A@IRSMSX107.ger.corp.intel.com> X-Mailer: Evolution 3.12.10-0ubuntu1~14.10.1 Mime-Version: 1.0 Cc: "openembedded-core@lists.openembedded.org" Subject: Re: [PATCH] oeqa/parselogs: Added another batch of errors to the whitelist. X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jun 2015 11:30:55 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Tue, 2015-06-02 at 09:50 +0000, Musat, George L wrote: > Hi Richard, > > Are you sure it's this patches fault for that? I only added some more > errors to the lists. Also I tested the patch locally and runs fine on > qemux86 master. For the Centos it looks like a network problem > occurred half way into the tests. I saw the same error locally, when I reverted the patch it went away so I'm pretty sure it was from this patch, yes. Cheers, Richard