From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 3A487A00E6 for ; Mon, 5 Aug 2019 16:18:59 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 026B61BDE9; Mon, 5 Aug 2019 16:18:59 +0200 (CEST) Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id A16FB1BDE8 for ; Mon, 5 Aug 2019 16:18:57 +0200 (CEST) Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 1170B793EC; Mon, 5 Aug 2019 14:18:57 +0000 (UTC) Received: from dhcp-25.97.bos.redhat.com (unknown [10.18.25.67]) by smtp.corp.redhat.com (Postfix) with ESMTPS id B795060C83; Mon, 5 Aug 2019 14:18:53 +0000 (UTC) From: Aaron Conole To: Michael Santana Francisco Cc: David Marchand , Aaron Conole , dev , Bruce Richardson , Ferruh Yigit , Luca Boccassi , Thomas Monjalon References: <20190731145030.19956-1-aconole@redhat.com> <20190802212552.8879-1-aconole@redhat.com> <1865053.T8TvltaDb9@xps> Date: Mon, 05 Aug 2019 10:18:52 -0400 In-Reply-To: (Michael Santana Francisco's message of "Mon, 5 Aug 2019 09:56:27 -0400") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.25]); Mon, 05 Aug 2019 14:18:57 +0000 (UTC) Subject: Re: [dpdk-dev] [PATCH v2 0/2] Enable fast-unit tests under travis X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Michael Santana Francisco writes: > On Mon, Aug 5, 2019 at 8:52 AM David Marchand wrote: >> >> On Mon, Aug 5, 2019 at 8:26 AM David Marchand wrote: >> > >> > On Sat, Aug 3, 2019 at 12:00 AM Thomas Monjalon wrote: >> > > >> > > 02/08/2019 23:25, Aaron Conole: >> > > > This series turns the fast unit tests on for a limited set of >> > > > builds under the travis build system. An example run is available >> > > > at: >> > > > >> > > > https://travis-ci.org/orgcandman/dpdk/builds/565991679 >> > > > >> > > > The builds which execute the unit tests may be distinguished by the >> > > > "RUN_TESTS" parameter. >> > > > >> > > > Aaron Conole (1): >> > > > ci: enable unit tests under travis-ci >> > > > >> > > > Michael Santana (1): >> > > > tests: Fix unit tests for shared builds >> > > >> > > Applied with change in comments of first patch, as described in this thread. >> > > Thanks >> > >> > Not sure I understand this error: >> > https://travis-ci.com/DPDK/dpdk/jobs/222141682 >> > >> > The 'static' config worked fine: >> > https://travis-ci.com/DPDK/dpdk/jobs/222141683 >> > >> > >> > Maybe a network issue ? But I would expect some kind of related >> > warning/error message. > It's either that or some other issue with the travis infrastructure. > There is nothing wrong in our end which is the frustrating part. I am > being hopeful and optimistic that it's _just a hiccup_ and it will go > away on its own. If it really keeps happening then we might need to > report the issue to travis >> > >> >> Ah something like those messages: >> https://travis-ci.com/DPDK/dpdk/jobs/222407326 >> https://travis-ci.com/DPDK/dpdk/jobs/222417471 >> >> Is there a way to retry builds? > Yes, at the very top, to the right there is a 'Restart job' button. > You have to be logged in as the owner of the repo to be able to see it > and click on it. That will restart the job from the very start. >> Automatically? > That's the million dollar question. We'll have to investigate if it's > possible It's possible. I need to get the robot polling travis correctly still. At the moment it can poll, but we don't have enough of the data recorded. It's coming though. One thing I notice is that some of the tests are still failing 'sporadically' and that's difficult to discern. So we might just use the robot as 'warn' rather than 'error' for now and maintainers will have to make a best determination. >> >> >> -- >> David Marchand