From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137277-137292 [PATCH] [v3,16/16] ip_frag: stop using var
Date: Tue, 27 Feb 2024 20:23:11 -0800 (PST) [thread overview]
Message-ID: <65deb52f.170a0220.dca08.5dc0SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1708978786-6740-17-git-send-email-roretzla@linux.microsoft.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/137292
_Functional Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Monday, February 26 2024 20:19:46
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137277-137292 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29272/
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:[~2024-02-28 4:23 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1708978786-6740-17-git-send-email-roretzla@linux.microsoft.com>
2024-02-26 19:59 ` |SUCCESS| pw137277-137292 [PATCH v3 16/16] ip_frag: stop using variadic argument pack extension qemudev
2024-02-26 20:03 ` qemudev
2024-02-26 20:23 ` |SUCCESS| pw137292 " checkpatch
2024-02-26 21:25 ` 0-day Robot
2024-02-28 4:22 ` |SUCCESS| pw137277-137292 [PATCH] [v3,16/16] ip_frag: stop using var dpdklab
2024-02-28 4:23 ` dpdklab [this message]
2024-02-28 4:26 ` dpdklab
2024-02-28 4:31 ` dpdklab
2024-02-26 21:02 dpdklab
2024-02-26 21:03 dpdklab
2024-02-26 21:10 dpdklab
2024-02-26 21:10 dpdklab
2024-02-26 21:11 dpdklab
2024-02-26 21:12 dpdklab
2024-02-26 21:12 dpdklab
2024-02-26 21:12 dpdklab
2024-02-26 21:14 dpdklab
2024-02-26 21:15 dpdklab
2024-02-26 21:15 dpdklab
2024-02-26 21:18 dpdklab
2024-02-26 21:19 dpdklab
2024-02-26 21:22 dpdklab
2024-02-26 21:24 dpdklab
2024-02-26 21:27 dpdklab
2024-02-26 21:27 dpdklab
2024-02-26 21:27 dpdklab
2024-02-26 21:28 dpdklab
2024-02-26 21:30 dpdklab
2024-02-26 21:31 dpdklab
2024-02-26 21:31 dpdklab
2024-02-26 21:32 dpdklab
2024-02-26 21:34 dpdklab
2024-02-26 21:34 dpdklab
2024-02-26 21:34 dpdklab
2024-02-26 21:36 dpdklab
2024-02-26 21:37 dpdklab
2024-02-26 21:38 dpdklab
2024-02-26 21:39 dpdklab
2024-02-26 21:40 dpdklab
2024-02-26 21:40 dpdklab
2024-02-26 21:41 dpdklab
2024-02-26 21:41 dpdklab
2024-02-26 21:42 dpdklab
2024-02-26 21:42 dpdklab
2024-02-26 21:43 dpdklab
2024-02-26 21:43 dpdklab
2024-02-26 21:43 dpdklab
2024-02-26 21:44 dpdklab
2024-02-26 21:44 dpdklab
2024-02-26 21:44 dpdklab
2024-02-26 21:45 dpdklab
2024-02-26 21:47 dpdklab
2024-02-26 21:48 dpdklab
2024-02-26 21:48 dpdklab
2024-02-26 21:49 dpdklab
2024-02-26 21:49 dpdklab
2024-02-26 21:49 dpdklab
2024-02-26 21:49 dpdklab
2024-02-26 21:52 dpdklab
2024-02-26 21:56 dpdklab
2024-02-26 22:12 dpdklab
2024-02-26 22:19 dpdklab
2024-02-26 22:21 dpdklab
2024-02-26 22:32 dpdklab
2024-02-26 22:37 dpdklab
2024-02-26 22:42 dpdklab
2024-02-26 22:42 dpdklab
2024-02-26 22:44 dpdklab
2024-02-26 22:51 dpdklab
2024-02-26 23:39 dpdklab
2024-02-26 23:48 dpdklab
2024-02-27 0:01 dpdklab
2024-02-27 0:08 dpdklab
2024-02-27 0:22 dpdklab
2024-02-27 6:34 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=65deb52f.170a0220.dca08.5dc0SMTPIN_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).