From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Thomas Monjalon <thomas@monjalon.net>
Subject: |FAILURE| pw155849-155851 [PATCH] [3/3] bbdev: wrong fix for MinGW 1
Date: Wed, 13 Aug 2025 23:45:51 -0700 (PDT) [thread overview]
Message-ID: <689d861f.050a0220.374677.8d70SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250813152829.457463-4-thomas@monjalon.net>
Test-Label: iol-intel-Functional
Test-Status: FAILURE
http://dpdk.org/patch/155851
_Functional Testing issues_
Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Wednesday, August 13 2025 15:25:25
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:38543d33bd47fc0ee21f59db80a8763620741879
155849-155851 --> functional testing issues
Upstream job id: Template-DTS-Pipeline#240312
Test environment and result as below:
Ubuntu 24.04 LTS
Kernel: 6.8.0-44-generic
Compiler: gcc 13.2.0
NIC: Intel Corporation Ethernet Controller XL710 for 40GbE QSFP+ 40 Mbps
Aggregate Results by Test Suite
+--------------------+--------+
| Test Suite | Result |
+====================+========+
| blocklist | PASS |
+--------------------+--------+
| pmd_buffer_scatter | PASS |
+--------------------+--------+
| promisc_support | PASS |
+--------------------+--------+
| uni_pkt | PASS |
+--------------------+--------+
| checksum_offload | PASS |
+--------------------+--------+
| dynamic_config | FAIL |
+--------------------+--------+
| dynamic_queue_conf | PASS |
+--------------------+--------+
| hello_world | PASS |
+--------------------+--------+
| l2fwd | PASS |
+--------------------+--------+
| softnic | PASS |
+--------------------+--------+
| vlan | PASS |
+--------------------+--------+
Ubuntu 24.04
Kernel: 6.8
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
NIC: Intel Corporation 4xxx Series QAT 0 Mbps
Aggregate Results by Test Suite
+----------------------------+--------+
| Test Suite | Result |
+============================+========+
| crypto_perf_cryptodev_perf | PASS |
+----------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33874/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2025-08-14 6:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250813152829.457463-4-thomas@monjalon.net>
2025-08-13 14:55 ` |SUCCESS| pw155849-155851 [PATCH 3/3] bbdev: wrong fix for MinGW 13 qemudev
2025-08-13 15:00 ` qemudev
2025-08-13 15:27 ` |SUCCESS| pw155851 " checkpatch
2025-08-13 16:35 ` 0-day Robot
2025-08-14 6:10 ` |SUCCESS| pw155849-155851 [PATCH] [3/3] bbdev: wrong fix for MinGW 1 dpdklab
2025-08-14 6:38 ` dpdklab
2025-08-14 6:45 ` dpdklab [this message]
2025-08-14 6:49 ` dpdklab
2025-08-14 6:54 ` |PENDING| " dpdklab
2025-08-14 6:57 ` |SUCCESS| " dpdklab
2025-08-14 6:57 ` |FAILURE| " dpdklab
2025-08-14 7:02 ` |SUCCESS| " dpdklab
2025-08-14 7:07 ` |PENDING| " dpdklab
2025-08-14 7:13 ` |FAILURE| " dpdklab
2025-08-14 7:14 ` dpdklab
2025-08-14 7:23 ` dpdklab
2025-08-14 7:38 ` dpdklab
2025-08-14 8:26 ` |SUCCESS| " dpdklab
2025-08-14 8:39 ` dpdklab
2025-08-14 8:50 ` |FAILURE| " dpdklab
2025-08-15 15:36 ` |SUCCESS| " dpdklab
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=689d861f.050a0220.374677.8d70SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).