All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bills, Jason M" <jason.m.bills@linux.intel.com>
To: openbmc@lists.ozlabs.org
Subject: Re: peci-pcie CI issues
Date: Wed, 10 Feb 2021 08:07:57 -0800	[thread overview]
Message-ID: <b71222f2-c0dc-cc30-afb8-c3a8669279f8@linux.intel.com> (raw)
In-Reply-To: <YCPPbAlAUHtn+Vv1@heinlein>



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<char, std::char_traits<char>, 
std::allocator<char> >&, unsigned int&, long int&, 
sdbusplus::xyz::openbmc_project::Logging::server::Entry::Level&, 
std::__cxx11::basic_string<char, std::char_traits<char>, 
std::allocator<char> >, std::vector<std::__cxx11::basic_string<char, 
std::char_traits<char>, std::allocator<char> >, 
std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, 
std::allocator<char> > > >, 
std::vector<std::tuple<std::__cxx11::basic_string<char, 
std::char_traits<char>, std::allocator<char> >, 
std::__cxx11::basic_string<char, std::char_traits<char>, 
std::allocator<char> >, std::__cxx11::basic_string<char, 
std::char_traits<char>, std::allocator<char> > >, 
std::allocator<std::tuple<std::__cxx11::basic_string<char, 
std::char_traits<char>, std::allocator<char> >, 
std::__cxx11::basic_string<char, std::char_traits<char>, 
std::allocator<char> >, std::__cxx11::basic_string<char, 
std::char_traits<char>, std::allocator<char> > > > >, const 
std::__cxx11::basic_string<char, std::char_traits<char>, 
std::allocator<char> >&, phosphor::logging::internal::Manager&}; 
typename std::_MakeUniq<_Tp>::__single_object = 
std::unique_ptr<phosphor::logging::Entry>]':
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<char, std::char_traits<char>, 
std::allocator<char> >, long int&, 
phosphor::logging::internal::Manager&}; typename 
std::_MakeUniq<_Tp>::__single_object = 
std::unique_ptr<phosphor::logging::Entry>]':
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

  reply	other threads:[~2021-02-10 16:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-24 15:47 peci-pcie CI issues Andrei Kartashev
2020-12-24 18:05 ` Patrick Williams
2020-12-24 18:23   ` Ed Tanous
2020-12-24 18:34     ` Andrei Kartashev
2020-12-24 18:53       ` Ed Tanous
2021-01-12  0:08         ` Bills, Jason M
2021-01-12 19:10           ` Andrew Geissler
2021-02-10 10:04     ` Andrei Kartashev
2021-02-10 12:19       ` Patrick Williams
2021-02-10 16:07         ` Bills, Jason M [this message]
2021-02-10 16:22           ` Andrei Kartashev
2021-02-11 18:42             ` Andrei Kartashev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b71222f2-c0dc-cc30-afb8-c3a8669279f8@linux.intel.com \
    --to=jason.m.bills@linux.intel.com \
    --cc=openbmc@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.