From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw154968 [PATCH] build/x86: fix support for older compiler
Date: Tue, 08 Jul 2025 11:34:24 -0700 (PDT) [thread overview]
Message-ID: <686d64b0.050a0220.1c6806.d7c1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250702155129.3440210-1-bruce.richardson@intel.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/154968
_Functional Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Wednesday, July 02 2025 15:51:29
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:5d47e73e5f4f2eb69bd73f642cfd72b49436bf96
154968 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#235741
Test environment and result as below:
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/33569/
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-07-08 18:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250702155129.3440210-1-bruce.richardson@intel.com>
2025-07-02 15:17 ` |SUCCESS| pw154968 [PATCH] build/x86: fix support for older compilers qemudev
2025-07-02 15:21 ` qemudev
2025-07-02 15:50 ` checkpatch
2025-07-08 18:34 ` dpdklab [this message]
2025-07-08 18:37 ` |FAILURE| pw154968 [PATCH] build/x86: fix support for older compiler dpdklab
2025-07-08 18:40 ` |SUCCESS| " dpdklab
2025-07-08 18:42 ` dpdklab
2025-07-08 18:55 ` |FAILURE| " dpdklab
2025-07-08 19:21 ` |PENDING| " dpdklab
2025-07-08 19:22 ` |SUCCESS| " dpdklab
2025-07-08 19:22 ` |FAILURE| " dpdklab
2025-07-08 19:26 ` dpdklab
2025-07-08 20:01 ` |WARNING| " dpdklab
2025-07-08 20:01 ` dpdklab
2025-07-08 20:02 ` dpdklab
2025-07-08 20:02 ` dpdklab
2025-07-08 20:09 ` |FAILURE| " dpdklab
2025-07-08 20:10 ` dpdklab
2025-07-08 20:11 ` dpdklab
2025-07-08 20:11 ` dpdklab
2025-07-08 20:13 ` dpdklab
2025-07-08 20:14 ` dpdklab
2025-07-08 20:15 ` dpdklab
2025-07-08 20:15 ` dpdklab
2025-07-08 21:12 ` |PENDING| " dpdklab
2025-07-08 21:43 ` |SUCCESS| " dpdklab
2025-07-08 21:58 ` |WARNING| " dpdklab
2025-07-08 22:49 ` |FAILURE| " dpdklab
2025-07-09 1:52 ` |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=686d64b0.050a0220.1c6806.d7c1SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@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).