From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw124716 [PATCH] net/ice: fix incorrect Rx timestamp for E822
Date: Fri, 3 Mar 2023 20:55:05 +0000 (UTC) [thread overview]
Message-ID: <20230303205505.AC5C2600AF@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/124716
_Functional Testing PASS_
Submitter: Simei Su <simei.su@intel.com>
Date: Thursday, March 02 2023 13:45:01
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4ef69b2877a24ddb89afaf4bb6f4e73bb52a605b
124716 --> functional testing pass
Test environment and result as below:
Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-137-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
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/2
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/2
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/25596/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-03-03 20:55 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 20:55 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-06 2:44 dpdklab
2023-03-06 2:39 dpdklab
2023-03-06 2:36 dpdklab
2023-03-05 11:57 dpdklab
2023-03-05 11:57 dpdklab
2023-03-05 11:55 dpdklab
2023-03-05 11:51 dpdklab
2023-03-05 11:50 dpdklab
2023-03-05 11:47 dpdklab
2023-03-05 11:45 dpdklab
2023-03-05 11:44 dpdklab
2023-03-05 11:42 dpdklab
2023-03-05 11:42 dpdklab
2023-03-05 11:41 dpdklab
2023-03-05 11:39 dpdklab
2023-03-05 11:34 dpdklab
2023-03-05 11:30 dpdklab
2023-03-05 11:05 dpdklab
2023-03-05 11:05 dpdklab
2023-03-05 11:02 dpdklab
2023-03-05 11:01 dpdklab
2023-03-05 11:00 dpdklab
2023-03-05 10:58 dpdklab
2023-03-05 10:57 dpdklab
2023-03-05 10:54 dpdklab
2023-03-05 10:53 dpdklab
2023-03-05 10:52 dpdklab
2023-03-05 10:49 dpdklab
2023-03-05 10:48 dpdklab
2023-03-05 10:39 dpdklab
2023-03-05 10:38 dpdklab
2023-03-04 14:57 dpdklab
2023-03-04 13:56 dpdklab
2023-03-04 12:31 dpdklab
2023-03-04 11:28 dpdklab
2023-03-04 6:32 dpdklab
2023-03-04 3:36 dpdklab
2023-03-03 21:56 dpdklab
2023-03-03 21:27 dpdklab
2023-03-03 21:21 dpdklab
2023-03-03 21:17 dpdklab
2023-03-03 21:15 dpdklab
2023-03-03 21:14 dpdklab
2023-03-03 21:13 dpdklab
2023-03-03 21:08 dpdklab
2023-03-03 21:06 dpdklab
2023-03-03 21:04 dpdklab
2023-03-03 21:01 dpdklab
2023-03-03 20:55 dpdklab
2023-03-03 20:44 dpdklab
2023-03-03 20:42 dpdklab
2023-03-03 20:34 dpdklab
2023-03-03 20:32 dpdklab
2023-03-03 20:31 dpdklab
2023-03-03 20:30 dpdklab
2023-03-03 20:27 dpdklab
2023-03-03 20:26 dpdklab
2023-03-03 20:23 dpdklab
2023-03-03 20:20 dpdklab
2023-03-03 20:15 dpdklab
2023-03-03 20:13 dpdklab
[not found] <20230302134501.201032-1-simei.su@intel.com>
2023-03-02 13:46 ` checkpatch
2023-03-02 15:59 ` 0-day Robot
2023-03-06 7:18 ` qemudev
2023-03-06 7:19 ` qemudev
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=20230303205505.AC5C2600AF@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--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).