DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Non-deterministic build failure in rte_ethdev.h:4287:10 on Taishan ARM server
Date: Mon, 1 Jun 2020 12:45:24 +0000	[thread overview]
Message-ID: <b541ad8242834f50a3ebd0a0639cf8dd@pantheon.tech> (raw)

Hi DPDK devs,

I'm hitting a build failure with dpdk 20.02.1 with rte_ethdev.h that's happening seemingly at random:
make install T=arm64-armv8a-linuxapp-gcc -j
In file included from /tmp/openvpp-testing/dpdk/lib/librte_ethdev/rte_class_eth.c:13:0:
/tmp/openvpp-testing/dpdk/lib/librte_ethdev/rte_ethdev.h:4287:10: fatal error: rte_ethdev_core.h: No such file or directory
#include <rte_ethdev_core.h>
          ^~~~~~~~~~~~~~~~~~~
compilation terminated.
make[5]: *** [rte_class_eth.o] Error 1
make[5]: *** Waiting for unfinished jobs....
make[4]: *** [librte_ethdev] Error 2
make[3]: *** [lib] Error 2
make[2]: *** [all] Error 2
make[1]: *** [pre_install] Error 2
make: *** [install] Error 2

Full log here: https://logs.fd.io/production/vex-yul-rot-jenkins-1/csit-dpdk-perf-verify-master-3n-tsh/11/archives/log.html.gz

This doesn't happen every time. It took me five builds on two machines (for a total of 10 builds) to hit this issue, but it did eventually happen. I tried this with 20.02 at first and it seemed to be happening more frequently, but I don't have enough data to really tell if there's an actual difference in frequency.

We're not doing anything special, just downloading and extracting the archive, then setting CONFIG_RTE_LIBRTE_MLX5_PMD and CONFIG_RTE_LIBRTE_I40E_16BYTE_RX_DESC to y in config/common_base and then running make install T=arm64-armv8a-linuxapp-gcc -j. As mentioned in the subject, the build server is a Taishan ARM server.

Any ideas on how to fix (or workaround) this? Is there a chance meson build would fix this? If so, how do we make sure we build testpmd with mxl5 support and how do we set CONFIG_RTE_LIBRTE_I40E_16BYTE_RX_DESC with meson build?

Thanks,
Juraj

             reply	other threads:[~2020-06-01 12:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-01 12:45 Juraj Linkeš [this message]
2020-06-01 14:36 ` Jerin Jacob
2020-06-02  7:13   ` Juraj Linkeš
2020-06-02  9:08     ` Jerin Jacob

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=b541ad8242834f50a3ebd0a0639cf8dd@pantheon.tech \
    --to=juraj.linkes@pantheon.tech \
    --cc=dev@dpdk.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 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).