DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/meson Bug 1589] meson_tests/driver link_bonding_autotest test failed
Date: Thu, 28 Nov 2024 06:57:55 +0000	[thread overview]
Message-ID: <bug-1589-3@http.bugs.dpdk.org/> (raw)

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

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

            Bug ID: 1589
           Summary: meson_tests/driver link_bonding_autotest test failed
           Product: DPDK
           Version: 24.11
          Hardware: x86
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: meson
          Assignee: dev@dpdk.org
          Reporter: hailinx.xu@intel.com
  Target Milestone: ---

Environment
===========
DPDK version: 24.11.0-rc4 a4f455560f747af8cd7fa99db86e757b7ff2fe79
OS: Red Hat Enterprise Linux 9.4 (Plow)/5.14.0-427.13.1.el9_4.x86_64
Compiler:  gcc version 11.4.1 20231218 (Red Hat 11.4.1-3)
Hardware platform: Intel(R) Xeon(R) Gold 6140M CPU @ 2.30GHz
NIC hardware: Ethernet Controller XXV710 for 25GbE SFP28 158b
NIC firmware: 
  FW: 9.50 0x8000f49c 255.65535.255
  Driver: 5.14.0-427.13.1.el9_4.x86_64

Test Setup
Steps to reproduce
==================
1. Bind ports to vfio-pci
./usertools/dpdk-devbind.py -b vfio-pci 0000:af:00.0 0000:af:00.1

2. Launch dpdk-test
./x86_64-native-linuxapp-gcc/app/dpdk-test -c 0xff -a 0000:af:00.0 -a
0000:af:00.1

3. Start link_bonding_autotest test
RTE>>link_bonding_autotest

Show the output from the previous commands.
===========================================
 + ------------------------------------------------------- +
 + Test Suite Summary : Link Bonding Unit Test Suite
 + ------------------------------------------------------- +
 + Tests Total :       65
 + Tests Skipped :      0
 + Tests Executed :    65
 + Tests Unsupported:   0
 + Tests Passed :      27
 + Tests Failed :      38
 + ------------------------------------------------------- +
Test Failed 

Expected Result
===============
 + ------------------------------------------------------- +
 + Test Suite Summary : Link Bonding Unit Test Suite
 + ------------------------------------------------------- +
 + Tests Total :       65
 + Tests Skipped :      0
 + Tests Executed :    65
 + Tests Unsupported:   0
 + Tests Passed :      65
 + Tests Failed :       0
 + ------------------------------------------------------- +
Test OK 

bad commit
**********
commit 112ce3917674b7e316776305d7e27778d17eb1b7 (HEAD)
Author: Stephen Hemminger <stephen@networkplumber.org>
Date:   Thu Nov 21 10:23:22 2024 -0800

    test/bonding: fix loop on members

    Do not use same variable for outer and inner loop in bonding test.
    Since the loop is just freeing the resulting burst use bulk free.

    Link: https://pvs-studio.com/en/blog/posts/cpp/1179/
    Fixes: 92073ef961ee ("bond: unit tests")
    Cc: stable@dpdk.org

    Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
    Acked-by: Bruce Richardson <bruce.richardson@intel.com>
    Acked-by: Chengwen Feng <fengchengwen@huawei.com>

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

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

                 reply	other threads:[~2024-11-28  6:57 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-1589-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).