test suite reviews and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dts@dpdk.org
Subject: [DTS/framework Bug 1718] send_packets_and_capture docs vary from randomness
Date: Wed, 04 Jun 2025 18:48:28 +0000	[thread overview]
Message-ID: <bug-1718-433@http.bugs.dpdk.org/> (raw)

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

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

            Bug ID: 1718
           Summary: send_packets_and_capture docs vary from randomness
           Product: DTS
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: framework
          Assignee: dts@dpdk.org
          Reporter: dpdkorgbmw@lsmod.de
  Target Milestone: ---

While working on reproducible builds for openSUSE, I found that
our dpdk-stable-24.11.1 package varies in every build because
/usr/share/doc/packages/dpdk/html/dts/framework.testbed_model.traffic_generator.capturing_traffic_generator.html

contains HTML that (when converted to text) looks like this:
 send_packets_and_capture(packets: list[scapy.packet.Packet], send_port: Port,
receive_port: Port, filter_config: PacketFilteringConfig, duration: float,
capture_name: str = '5e567378-734d-4380-84aa-f1d7f3a45ea1') →
list[scapy.packet.Packet]

Here the capture_name is random because of
dpdk-stable-24.11.1/dts/framework/testbed_model/traffic_generator/capturing_traffic_generator.py
line 27:
def _get_default_capture_name() -> str:
    return str(uuid.uuid4())

Please ensure that all build outputs are deterministic.
I think, there is a way to hide or override certain parameters in Sphinx docs.

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

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

             reply	other threads:[~2025-06-04 18:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-04 18:48 bugzilla [this message]
2025-06-06  8:45 ` bugzilla

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-1718-433@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dts@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).