All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/meson Bug 1579] [dpdk-24.11-rc2] meson_tests/fasts malloc_autotest test failed on i40e
Date: Fri, 15 Nov 2024 03:22:17 +0000	[thread overview]
Message-ID: <bug-1579-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 1518 bytes --]

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

            Bug ID: 1579
           Summary: [dpdk-24.11-rc2] meson_tests/fasts malloc_autotest
                    test failed on i40e
           Product: DPDK
           Version: 24.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: meson
          Assignee: dev@dpdk.org
          Reporter: hailinx.xu@intel.com
  Target Milestone: ---

ENV
----------
DPDK version: dpdk-24.11-rc2 c5df7a373ad07413d9652479272cd16adf989b06
OS: Ubuntu 24.04.1 LTS/6.8.0-48-generic
Compiler: gcc version 13.2.0
Hardware platform: Intel(R) Xeon(R) Gold 6140M CPU @ 2.30GHz
NIC hardware: Ethernet Controller XXV710 for 25GbE SFP28 158b
NIC firmware: 
  driver: i40e-5.14.0-427.13.1.el9_4.x86_64 / i40e-2.26.8
  firmware-version: 9.50 0x8000f49c 255.65535.255

Test Setup
----------
Steps to reproduce

1. bind ports to dpdk
./usertools/dpdk-devbind.py -b vfio-pci 0000:af:00.0 0000:af:00.1
2. launch app
./x86_64-native-linuxapp-gcc/app/dpdk-test -c 0xff -a 0000:af:00.0 -a
0000:af:00.1
3. start test
RTE>>malloc_autotest

Show the output from the previous commands.
-------------------------------------------
Incorrect heap statistics: Allocated size
test_multi_alloc_statistics() failed
Test Failed
RTE>> 

Expected Result
---------------
Test Successful.

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

[-- Attachment #2: Type: text/html, Size: 3411 bytes --]

                 reply	other threads:[~2024-11-15  3:22 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-1579-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.