From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.5 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 946E2C33C9E for ; Tue, 14 Jan 2020 16:51:59 +0000 (UTC) Received: from dpdk.org (dpdk.org [92.243.14.124]) by mail.kernel.org (Postfix) with ESMTP id 2FD9E214AF for ; Tue, 14 Jan 2020 16:51:59 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="fC14UKeq" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 2FD9E214AF Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dev-bounces@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id C49311C11F; Tue, 14 Jan 2020 17:51:53 +0100 (CET) Received: from us-smtp-delivery-1.mimecast.com (us-smtp-2.mimecast.com [207.211.31.81]) by dpdk.org (Postfix) with ESMTP id E2B581C11C for ; Tue, 14 Jan 2020 17:51:51 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1579020711; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=3NDf8tKYjk9zV0P9xTBtvI/2UbtP1mUW5ArwavBwSbg=; b=fC14UKeq4ZyCOnCPKBTkNLhzk/KHPm2NaaMzMeZIZL4A0pse/4EKB0n7lscZVsQ7gVHOov MP5Z09Hxnrxc2+Is7MHO7rtqLKt37qhTfxDRUkiqvsjOTBDZEGL4oomEmNR+eYvUbEPLL/ fMtz0n0KIE2+2kjzT62n3sR3S2LfnhA= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-349-fLnlA9BOOiONjWDv1fG49A-1; Tue, 14 Jan 2020 11:51:49 -0500 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id EBA981141695; Tue, 14 Jan 2020 16:51:47 +0000 (UTC) Received: from dhcp-25.97.bos.redhat.com (unknown [10.18.25.108]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 36D4880A48; Tue, 14 Jan 2020 16:51:47 +0000 (UTC) From: Aaron Conole To: Aaron Conole Cc: Honnappa Nagarahalli , test-report@dpdk.org, ci@dpdk.org, dev@dpdk.org References: <20200113172518.37815-7-honnappa.nagarahalli@arm.com> <1578977880-13011-1-git-send-email-robot@bytheb.org> Date: Tue, 14 Jan 2020 11:51:46 -0500 In-Reply-To: (Aaron Conole's message of "Tue, 14 Jan 2020 10:12:53 -0500") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-MC-Unique: fLnlA9BOOiONjWDv1fG49A-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-dev] FW: || pw64572 lib/eventdev: use custom element size ring for event rings 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" Aaron Conole writes: > Honnappa Nagarahalli writes: > >> Hi Aaron, >> I am not able to understand the error, looks like there is no >> particular error. Can you please take a look? > > Gladly. A number of the systems that were running the build stopped > their output for an unknown reason (looks like this was a 1-time > thing). See the error: > > [2164/2165] Compiling C object 'app/te...st@@dpdk-test@exe/test_ring_pe= rf.c.o'. > > No output has been received in the last 10m0s, this potentially > indicates a stalled build or something wrong with the build itself. I see this continually happening (I've kicked it off a number of times). This patch might need more investigation, since it's always failing when building 2164/2165 object. I'll note that it seems to be clang related, rather than gcc related. > My guess is some kind of infrastructure change happened during the > build? Maybe compiling the test_ring_perf.c object has been pushed out > too far. I've restarted one of the jobs to see if it will successfully > execute. If so, it's just a fluke. > > As for the fluke part, the intent is to enhance the robot to detect > these "error" conditions and issue a restart for the travis build > (rather than not report a valid state). That's work TBD (but patches > are welcome - see https://github.com/orgcandman/pw-ci for all the bot > code). > >> Thank you, >> Honnappa >> >> -----Original Message----- >> From: 0-day Robot >> Sent: Monday, January 13, 2020 10:58 PM >> To: test-report@dpdk.org >> Cc: Honnappa Nagarahalli ; robot@bytheb.or= g >> Subject: || pw64572 lib/eventdev: use custom element size ring for event= rings >> >> From: robot@bytheb.org >> >> Test-Label: travis-robot >> Test-Status: >> http://dpdk.org/patch/64572 >> >> _Travis build: errored_ >> Build URL: https://travis-ci.com/ovsrobot/dpdk/builds/144202958 >> IMPORTANT NOTICE: The contents of this email and any attachments are >> confidential and may also be privileged. If you are not the intended >> recipient, please notify the sender immediately and do not disclose >> the contents to any other person, use it for any purpose, or store or >> copy the information in any medium. Thank you. >> IMPORTANT NOTICE: The contents of this email and any attachments are >> confidential and may also be privileged. If you are not the intended >> recipient, please notify the sender immediately and do not disclose >> the contents to any other person, use it for any purpose, or store or >> copy the information in any medium. Thank you.