DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 761] Unit tests fail on FreeBSD
Date: Fri, 23 Jul 2021 13:20:52 +0000	[thread overview]
Message-ID: <bug-761-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=761

            Bug ID: 761
           Summary: Unit tests fail on FreeBSD
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: FreeBSD
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: lylavoie@iol.unh.edu
  Target Milestone: ---

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

From discussions on the CI mailing list, it has been reproduced and needs
further debugging to resolve the issues.  Bug here is for tracking the fixes
within DPDK, https://mails.dpdk.org/archives/ci/2021-July/001267.html

Once a patch is available, please let the CI team know.

-- 
You are receiving this mail because:
You are the assignee for the bug.

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

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-761-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --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).