From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Owen Hilyard <ohilyard@iol.unh.edu>
Cc: Narcisa Ana Maria Vasile <navasile@linux.microsoft.com>,
dev <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>,
Khoa To <khot@microsoft.com>,
navasile@microsoft.com, Dmitry Malloy <dmitrym@microsoft.com>,
Tyler Retzlaff <roretzla@microsoft.com>,
talshn@nvidia.com, Omar Cardona <ocardona@microsoft.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
David Marchand <david.marchand@redhat.com>,
pallavi.kadam@intel.com, ci@dpdk.org
Subject: Re: [dpdk-ci] [dpdk-dev] [PATCH v12 01/10] eal: add basic threading functions
Date: Tue, 3 Aug 2021 18:38:08 +0300 [thread overview]
Message-ID: <20210803183808.04b7af83@sovereign> (raw)
In-Reply-To: <CAHx6DYA7XF7sBiZWqg+u-rJqi2qLoXa6+EZJMqn+ubquo2E+2w@mail.gmail.com>
2021-08-03 11:11 (UTC-0400), Owen Hilyard:
> It seems like meson encountered an error when building
>
> app/test/meson.build:472:11: ERROR: Index 1 out of bounds of array of size
> > 1.
> >
> > A full log can be found at
> > /home-local/jenkins-local/jenkins-agent/workspace/Apply-Custom-Patch-Set/dpdk/build/meson-logs/meson-log.txt
> > ninja: error: loading 'build.ninja': No such file or directory
> >
>
> I can also reproduce the issue building locally (Meson version: 0.58.1):
Meson 0.58+ has a known issue on Windows:
https://github.com/mesonbuild/meson/issues/8981
The last known good version is 0.57.2.
> 1. Get the DPDK main branch (f12b844b54f4ea7908ecb08ade04c7366ede031d)
> 2. apply all patches
> 3. meson $BUILD_DIR
>
> Meson doesn't really give any extra information aside from that, but
> looking at the build file, it looks like one of the fast_tests has no
> arguments and at least one is expected.
>
> On Mon, Aug 2, 2021 at 5:37 PM Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
> wrote:
>
> > + ci@dpdk.org
> >
> > 2021-08-02 14:08 (UTC-0700), Narcisa Ana Maria Vasile:
> > > On Mon, Aug 02, 2021 at 10:32:17AM -0700, Narcisa Ana Maria Vasile wrote:
> > > > From: Narcisa Vasile <navasile@microsoft.com>
> > > >
> > > > Use a portable, type-safe representation for the thread identifier.
> > > > Add functions for comparing thread ids and obtaining the thread id
> > > > for the current thread.
> > > >
> > > > Signed-off-by: Narcisa Vasile <navasile@microsoft.com>
> > > > ---
> > > > lib/eal/common/meson.build | 1 +
> > > > lib/eal/{unix => common}/rte_thread.c | 57 ++++++++++++++++-----------
> > > > lib/eal/include/rte_thread.h | 48 +++++++++++++++++-----
> > > > lib/eal/unix/meson.build | 1 -
> > > > lib/eal/version.map | 3 ++
> > > > lib/eal/windows/rte_thread.c | 17 ++++++++
> > > > 6 files changed, 95 insertions(+), 32 deletions(-)
> > > > rename lib/eal/{unix => common}/rte_thread.c (66%)
> > > >
> > > > diff --git a/lib/eal/common/meson.build b/lib/eal/common/meson.build
> > >
> > > Hello,
> > >
> > > I see the following error on this patch:
> > >
> > > ninja: error: loading 'build.ninja': No such file or directory
> > >
> > > https://lab.dpdk.org/results/dashboard/patchsets/18090/
> > >
> > > Locally, the build succeedes.
> > > How can I see more information about this build error?
> >
next prev parent reply other threads:[~2021-08-03 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1627684312-28630-1-git-send-email-navasile@linux.microsoft.com>
[not found] ` <1627925546-29982-1-git-send-email-navasile@linux.microsoft.com>
[not found] ` <1627925546-29982-2-git-send-email-navasile@linux.microsoft.com>
[not found] ` <20210802210811.GA29249@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
2021-08-02 21:37 ` Dmitry Kozlyuk
2021-08-03 15:11 ` Owen Hilyard
2021-08-03 15:38 ` Dmitry Kozlyuk [this message]
2021-08-03 15:57 ` Owen Hilyard
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=20210803183808.04b7af83@sovereign \
--to=dmitry.kozliuk@gmail.com \
--cc=bruce.richardson@intel.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dmitrym@microsoft.com \
--cc=khot@microsoft.com \
--cc=navasile@linux.microsoft.com \
--cc=navasile@microsoft.com \
--cc=ocardona@microsoft.com \
--cc=ohilyard@iol.unh.edu \
--cc=pallavi.kadam@intel.com \
--cc=roretzla@microsoft.com \
--cc=talshn@nvidia.com \
--cc=thomas@monjalon.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).