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=-10.5 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 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 BD037C433E6 for ; Wed, 10 Feb 2021 16:10:13 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id EBDBF64E57 for ; Wed, 10 Feb 2021 16:10:12 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org EBDBF64E57 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linux.intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=openbmc-bounces+openbmc=archiver.kernel.org@lists.ozlabs.org Received: from bilbo.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 4DbPqQ0y7DzDwg7 for ; Thu, 11 Feb 2021 03:10:10 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; spf=none (no SPF record) smtp.mailfrom=linux.intel.com (client-ip=134.134.136.126; helo=mga18.intel.com; envelope-from=jason.m.bills@linux.intel.com; receiver=) Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4DbPn16kwMzDvrC for ; Thu, 11 Feb 2021 03:08:04 +1100 (AEDT) IronPort-SDR: mTODe754zRzMGEs1bVPEsTFfRlZXwx5tZoRJMiACNTqdbei803bRwLkKUYi1XsqMWcAvYlU73o 3HFxn/34dZmQ== X-IronPort-AV: E=McAfee;i="6000,8403,9891"; a="169774274" X-IronPort-AV: E=Sophos;i="5.81,168,1610438400"; d="scan'208";a="169774274" Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 10 Feb 2021 08:07:59 -0800 IronPort-SDR: EMjDNRAIcReWPdMU1b2eOWlk6FGvOVieVWTyyAvC9OHJvIoKtsF2ldY4tu5FPIV0HGqyYz5ef1 rGaznhySVRKA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.81,168,1610438400"; d="scan'208";a="578456993" Received: from linux.intel.com ([10.54.29.200]) by orsmga005.jf.intel.com with ESMTP; 10 Feb 2021 08:07:58 -0800 Received: from [10.209.46.5] (jmbills-MOBL.amr.corp.intel.com [10.209.46.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by linux.intel.com (Postfix) with ESMTPS id 6F5605808AB for ; Wed, 10 Feb 2021 08:07:58 -0800 (PST) Subject: Re: peci-pcie CI issues To: openbmc@lists.ozlabs.org References: <6c2c44435e704f6eee95b7e35cbc39ccfae32b62.camel@yadro.com> <27dbc305c6c53c338b5eefec68fbcda38ff44672.camel@yadro.com> From: "Bills, Jason M" Message-ID: Date: Wed, 10 Feb 2021 08:07:57 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: openbmc-bounces+openbmc=archiver.kernel.org@lists.ozlabs.org Sender: "openbmc" On 2/10/2021 4:19 AM, Patrick Williams wrote: > On Wed, Feb 10, 2021 at 01:04:41PM +0300, Andrei Kartashev wrote: >> As far as I can see, boost was updated to 1.75.0, but looks like it >> didn't help, CI still failed to build peci-pcie: >> https://jenkins.openbmc.org/job/ci-repository/12229/console >> > > Hi Andrei, > > Repository-level CI isn't done with bitbake but under a docker build we > have set up. Jason put up a patch yesterday to update that to use Boost > 1.75[1]. Once that is merged then the `ci-repository` job will use the > desired Boost version. > > 1. https://gerrit.openbmc-project.xyz/c/openbmc/openbmc-build-scripts/+/40426 > It looks like there is a new failure after the boost 1.75 update. Does anyone know what this error means? I also see this error on another repo: https://jenkins.openbmc.org/job/ci-repository/12253/. CXX xyz/openbmc_project/Logging/Internal/Manager/phosphor_log_manager-server.o In file included from /usr/include/c++/10/memory:83, from /usr/local/include/sdbusplus/message.hpp:11, from /usr/local/include/sdbusplus/bus.hpp:7, from /usr/local/include/sdbusplus/server.hpp:3, from /usr/local/include/xyz/openbmc_project/Logging/ErrorBlocksTransition/server.hpp:5, from elog_block.hpp:5, from log_manager.hpp:3, from log_manager.cpp:3: /usr/include/c++/10/bits/unique_ptr.h: In instantiation of 'typename std::_MakeUniq<_Tp>::__single_object std::make_unique(_Args&& ...) [with _Tp = phosphor::logging::Entry; _Args = {sdbusplus::bus::bus&, std::__cxx11::basic_string, std::allocator >&, unsigned int&, long int&, sdbusplus::xyz::openbmc_project::Logging::server::Entry::Level&, std::__cxx11::basic_string, std::allocator >, std::vector, std::allocator >, std::allocator, std::allocator > > >, std::vector, std::allocator >, std::__cxx11::basic_string, std::allocator >, std::__cxx11::basic_string, std::allocator > >, std::allocator, std::allocator >, std::__cxx11::basic_string, std::allocator >, std::__cxx11::basic_string, std::allocator > > > >, const std::__cxx11::basic_string, std::allocator >&, phosphor::logging::internal::Manager&}; typename std::_MakeUniq<_Tp>::__single_object = std::unique_ptr]': log_manager.cpp:235:74: required from here /usr/include/c++/10/bits/unique_ptr.h:962:30: error: invalid new-expression of abstract class type 'phosphor::logging::Entry' 962 | { return unique_ptr<_Tp>(new _Tp(std::forward<_Args>(__args)...)); } | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In file included from log_manager.hpp:4, from log_manager.cpp:3: elog_entry.hpp:38:7: note: because the following virtual functions are pure within 'phosphor::logging::Entry': 38 | class Entry : public EntryIfaces | ^~~~~ In file included from elog_entry.hpp:3, from log_manager.hpp:4, from log_manager.cpp:3: /usr/local/include/xyz/openbmc_project/Logging/Entry/server.hpp:92:45: note: 'virtual sdbusplus::message::unix_fd sdbusplus::xyz::openbmc_project::Logging::server::Entry::getEntry()' 92 | virtual sdbusplus::message::unix_fd getEntry( | ^~~~~~~~ In file included from /usr/include/c++/10/memory:83, from /usr/local/include/sdbusplus/message.hpp:11, from /usr/local/include/sdbusplus/bus.hpp:7, from /usr/local/include/sdbusplus/server.hpp:3, from /usr/local/include/xyz/openbmc_project/Logging/ErrorBlocksTransition/server.hpp:5, from elog_block.hpp:5, from log_manager.hpp:3, from log_manager.cpp:3: /usr/include/c++/10/bits/unique_ptr.h: In instantiation of 'typename std::_MakeUniq<_Tp>::__single_object std::make_unique(_Args&& ...) [with _Tp = phosphor::logging::Entry; _Args = {sdbusplus::bus::bus&, std::__cxx11::basic_string, std::allocator >, long int&, phosphor::logging::internal::Manager&}; typename std::_MakeUniq<_Tp>::__single_object = std::unique_ptr]': log_manager.cpp:571:68: required from here /usr/include/c++/10/bits/unique_ptr.h:962:30: error: invalid new-expression of abstract class type 'phosphor::logging::Entry' 962 | { return unique_ptr<_Tp>(new _Tp(std::forward<_Args>(__args)...)); } | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ CXXLD libphosphor_logging.la CXXLD logging-test CXXLD callout-test make[2]: Leaving directory '/phosphor-logging-b50c705c3bb3738673f98cd371b408a5b48e629a' make[2]: *** [Makefile:1631: phosphor_log_manager-log_manager.o] Error 1 make[1]: *** [Makefile:2013: all-recursive] Error 1 make[1]: Leaving directory '/phosphor-logging-b50c705c3bb3738673f98cd371b408a5b48e629a' make: *** [Makefile:910: all] Error 2 The command '/bin/sh -c curl -L https://github.com/openbmc/phosphor-logging/archive/b50c705c3bb3738673f98cd371b408a5b48e629a.tar.gz | tar -xz && cd phosphor-logging-* && ./bootstrap.sh && ./configure --prefix=/usr/local --enable-metadata-processing YAML_DIR=/usr/local/share/phosphor-dbus-yaml/yaml && make -j80 && make install' returned a non-zero code: 2 Thanks, -Jason