DPDK CI discussions
 help / color / mirror / Atom feed
From: Brandon Lo <blo@iol.unh.edu>
To: ci@dpdk.org, dpdklab <dpdklab@iol.unh.edu>
Subject: [dpdk-ci] FreeBSD 13 Unit Testing -- Two Tests Failing
Date: Tue, 13 Jul 2021 16:55:49 -0400	[thread overview]
Message-ID: <CAOeXdvZm3D77f57_BaJWBDt3Qwj6deVb01OUT8nBkVfc=cvAbw@mail.gmail.com> (raw)

Hello all,

I am looking to expand the coverage of the community lab by running
DPDK unit tests on FreeBSD 13.
Currently, in the fast tests suite, there are 2 tests failing and
preventing the environment from being put into production:
interrupt_autotest and memory_autotest.
This test was on DPDK main, commit a95bbb72623c310df4d0c8ad45c2ee06f538e01b.

interrupt_autotest fails quite quickly:
stdout:
RTE>>interrupt_autotest
Check unknown valid interrupt full path
callback has not been called
failure occurred during checking unknown valid interrupt full path
Clearing for interrupt tests
Test Failed

memory_autotest fails after dumping memory:
stdout:
RTE>>memory_autotest
Dump memory layout
...
Error getting segment fd's
Test Failed

Could somebody more familiar with the tests confirm if these are real issues?

Thanks,
Brandon

--
Brandon Lo

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

blo@iol.unh.edu

www.iol.unh.edu

             reply	other threads:[~2021-07-13 20:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-13 20:55 Brandon Lo [this message]
2021-07-14 11:37 ` Thomas Monjalon
2021-07-14 12:01   ` Richardson, Bruce
2021-07-16 16:18     ` Brandon Lo
2021-07-16 16:21       ` Richardson, Bruce
2021-08-11 21:00         ` Brandon Lo
2021-09-17 15:11   ` Richardson, Bruce
2021-10-02 14:43     ` David Marchand
2021-10-04  7:46       ` Richardson, Bruce

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='CAOeXdvZm3D77f57_BaJWBDt3Qwj6deVb01OUT8nBkVfc=cvAbw@mail.gmail.com' \
    --to=blo@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=dpdklab@iol.unh.edu \
    /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).