DPDK CI discussions
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@redhat.com>
To: Brandon Lo <blo@iol.unh.edu>
Cc: "dpdklab\@iol.unh.edu" <dpdklab@iol.unh.edu>,
	ci@dpdk.org, dev@dpdk.org, spdk@lists.01.org
Subject: [dpdk-ci] [CI] SPDK compilation failures @ DPDK community lab
Date: Mon, 08 Feb 2021 10:21:08 -0500	[thread overview]
Message-ID: <f7ta6se7fh7.fsf@dhcp-25.97.bos.redhat.com> (raw)

Greetings,

I've noticed that recently SPDK compilation in the UNH community lab
seems to be failing, and I don't see an obvious reason for the failure.
The logs haven't been too helpful - it appears that there is a symbol
that isn't available when linking.

Job details (for example):
https://lab.dpdk.org/results/dashboard/results/results-uploads/test_runs/2363efb43157465db3228c34c00ebd57/log_upload_file/2021/2/dpdk_f6f2d2240153_15524_2021-02-04_22-59-59_NA.zip

Is it possible to turn on more verbose logging during the compilation of
SPDK?  Maybe show the arguments to the compiler for the specific object?
Maybe the SPDK folks can see something obviously wrong?

Thanks,
-Aaron


             reply	other threads:[~2021-02-08 15:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-08 15:21 Aaron Conole [this message]
2021-02-08 16:03 ` [dpdk-ci] [dpdk-dev] " Zawadzki, Tomasz
2021-02-08 16:21   ` Lincoln Lavoie
2021-02-08 17:17     ` Zawadzki, Tomasz
2021-02-09 15:13       ` Aaron Conole
2021-02-09 16:07         ` [dpdk-ci] [dpdklab] " Brandon Lo
2021-02-09 17:54           ` Brandon Lo
2021-02-11 14:02             ` Aaron Conole
2021-02-11 16:25               ` Brandon Lo
2021-02-12  9:18               ` Zawadzki, Tomasz
2021-02-12 17:39                 ` Brandon Lo
2021-02-15 15:28                   ` Aaron Conole
2021-02-17 16:06                     ` Zawadzki, Tomasz
2021-02-18 13:58                       ` Brandon Lo
2021-02-15  9:12                 ` [dpdk-ci] [SPDK] " David Marchand
2021-02-15  9:56                   ` [dpdk-ci] [dpdk-dev] [SPDK] Re: [dpdklab] " Nick Connolly
2021-02-15 10:15                     ` David Marchand

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=f7ta6se7fh7.fsf@dhcp-25.97.bos.redhat.com \
    --to=aconole@redhat.com \
    --cc=blo@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=dev@dpdk.org \
    --cc=dpdklab@iol.unh.edu \
    --cc=spdk@lists.01.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).