From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id A1D86A0548 for ; Mon, 8 Feb 2021 16:21:25 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 96E471606CC; Mon, 8 Feb 2021 16:21:25 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) by mails.dpdk.org (Postfix) with ESMTP id 46E0A40147 for ; Mon, 8 Feb 2021 16:21:24 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1612797683; 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; bh=WN8WGIM995oxLEYgZxnqKTfxUZ6N40NWux9iYK9WxhA=; b=ZZBoByWrlGHFV0GzfV5SU3H6MCwRFEnGamLRxfPfmSKMNwPLb0jREQsJBSxb6RWyVsFFJn e5TW+C0npeXGAbTBKbVTM361I7Xq8o4CYLbdMvUZJDixCKSnla3jeDP9d+sY/QnsBYSakB 7D3SPhc/X93ZedNBmHhOhJLm0mwZtKA= 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-490-91UzI1kDOAOfWyvGdCeFhA-1; Mon, 08 Feb 2021 10:21:12 -0500 X-MC-Unique: 91UzI1kDOAOfWyvGdCeFhA-1 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 C04FCC73A0; Mon, 8 Feb 2021 15:21:10 +0000 (UTC) Received: from dhcp-25.97.bos.redhat.com (ovpn-114-243.rdu2.redhat.com [10.10.114.243]) by smtp.corp.redhat.com (Postfix) with ESMTPS id D564E189CE; Mon, 8 Feb 2021 15:21:09 +0000 (UTC) From: Aaron Conole To: Brandon Lo Cc: "dpdklab\@iol.unh.edu" , ci@dpdk.org, dev@dpdk.org, spdk@lists.01.org Date: Mon, 08 Feb 2021 10:21:08 -0500 Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=aconole@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain Subject: [dpdk-ci] [CI] SPDK compilation failures @ DPDK community lab X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org Sender: "ci" Greetings, I've noticed that recently SPDK compilation in the UNH community lab seems to be failing, and I don't see an obvious reason for the failure. The logs haven't been too helpful - it appears that there is a symbol that isn't available when linking. Job details (for example): https://lab.dpdk.org/results/dashboard/results/results-uploads/test_runs/2363efb43157465db3228c34c00ebd57/log_upload_file/2021/2/dpdk_f6f2d2240153_15524_2021-02-04_22-59-59_NA.zip Is it possible to turn on more verbose logging during the compilation of SPDK? Maybe show the arguments to the compiler for the specific object? Maybe the SPDK folks can see something obviously wrong? Thanks, -Aaron