All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Venture <venture@google.com>
To: Kun Yi <kunyi@google.com>
Cc: William Kennington <wak@google.com>,
	Brad Bishop <bradleyb@fuzziesquirrel.com>,
	 OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	Matt Spinler <mspinler@linux.ibm.com>,
	 Andrew Geissler <geissonator@yahoo.com>,
	wangkair@cn.ibm.com
Subject: Re: unit test build failure in phosphor-hwmon
Date: Mon, 7 Oct 2019 13:29:14 -0700	[thread overview]
Message-ID: <CAO=notwGr6KV6aSqoBMRH+X=jVakOWBCr86K9OA4MCC0ph6KbA@mail.gmail.com> (raw)
In-Reply-To: <CAGMNF6VCJxS_ewJkpvGAUwtiJrgVUSp2ajeVeN+k7hZoiXj8gg@mail.gmail.com>

On Mon, Oct 7, 2019 at 1:22 PM Kun Yi <kunyi@google.com> wrote:
>
> What's the test build error message with meson?
>
> On Mon, Oct 7, 2019 at 1:05 PM William Kennington <wak@google.com> wrote:
> >
> > Well, the unit test environment is using gcc 9.x.x for what that's worth.
> >
> > On Mon, Oct 7, 2019 at 1:02 PM Brad Bishop <bradleyb@fuzziesquirrel.com> wrote:
> > >
> > > I was trying to get meson going in phosphor-hwmon today and I stumbled on a
> > > unit test that doesn’t build under gcc 9.1.0.  The failing test is the
> > > average test.
> > >
> > > I just thought I’d quick throw this out there in case anyone feels like
> > > having a look.  Also, I think this means our repository CI environment has
> > > gotten out of sync with upstream Yocto?
> > >
> > > I realize “patches welcome” applies here for both issues :-) but I just
> > > wanted to broadcast them.
> > >
> > > thx -brad
>

I don't see your patches on gerrit.  I don't mind building against
experimental patches :)

>
>
> --
> Regards,
> Kun

  reply	other threads:[~2019-10-07 20:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-07 20:01 unit test build failure in phosphor-hwmon Brad Bishop
2019-10-07 20:04 ` William Kennington
2019-10-07 20:22   ` Kun Yi
2019-10-07 20:29     ` Patrick Venture [this message]
2019-10-07 20:52       ` Brad Bishop
2019-10-07 20:31     ` Brad Bishop
2019-10-07 20:42       ` Patrick Venture
2019-10-07 20:43         ` William Kennington
2019-10-07 22:16           ` Brad Bishop
2019-10-07 20:43         ` Patrick Venture

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='CAO=notwGr6KV6aSqoBMRH+X=jVakOWBCr86K9OA4MCC0ph6KbA@mail.gmail.com' \
    --to=venture@google.com \
    --cc=bradleyb@fuzziesquirrel.com \
    --cc=geissonator@yahoo.com \
    --cc=kunyi@google.com \
    --cc=mspinler@linux.ibm.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=wak@google.com \
    --cc=wangkair@cn.ibm.com \
    /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.