From: Patrick Williams <patrick@stwcx.xyz>
To: "i.kononenko" <i.kononenko@yadro.com>
Cc: "Brad Bishop \(Code Review\)" <gerrit@openbmc-project.xyz>,
OpenBMC MailList OZLabs <openbmc@lists.ozlabs.org>
Subject: Re: phosphor-misc: CI Build failure
Date: Wed, 27 Apr 2022 11:13:06 -0500 [thread overview]
Message-ID: <Ymlrkt3HmnHuY1Ag@heinlein.stwcx.org.github.beta.tailscale.net> (raw)
In-Reply-To: <7a071d50-b581-2623-d439-d134f805f228@yadro.com>
[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]
On Wed, Apr 27, 2022 at 04:39:01PM +0300, i.kononenko wrote:
> Hello.
>
> Today I was received notice of the phosphor-misc CI build failed due to
> many `shellcheck` verify failed. The last build (where CI fail was
> found) related to the gerrit change [1] according add support RNDIS and
> EEM network feature, but `shellchek` raise too many error about another
> code that hasn't been changed.
I took a look at the failure and it is not due to shellcheck. We run
shellcheck every where but it only fails the build if the .shellcheck
file is present, which this repo does not have[1].
The failure here is that a more recent version of Meson is upset if
options are passed which are not supported. This appears to be the case
in this repo:
```
/data0/jenkins/workspace/ci-repository/openbmc/phosphor-misc > meson configure build -Db_sanitize=address,undefined -Db_lundef=false
ERROR: Unknown options: "b_lundef, b_sanitize"
```
We'll need to clean up whatever is going on with the meson calls here.
1. https://github.com/openbmc/openbmc-build-scripts/blob/ac5915f07d3b796f224c85477763ca7fe893dcc2/scripts/format-code.sh#L64
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-04-27 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 13:39 phosphor-misc: CI Build failure i.kononenko
2022-04-27 16:13 ` Patrick Williams [this message]
2022-04-27 17:26 ` i.kononenko
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=Ymlrkt3HmnHuY1Ag@heinlein.stwcx.org.github.beta.tailscale.net \
--to=patrick@stwcx.xyz \
--cc=gerrit@openbmc-project.xyz \
--cc=i.kononenko@yadro.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.