From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136356-136374 [PATCH] [v7,19/19] log: remove PMD log typ
Date: Mon, 05 Feb 2024 11:53:14 -0800 (PST) [thread overview]
Message-ID: <65c13caa.050a0220.e8c9.0e67SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/136374
_Functional Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Saturday, February 03 2024 04:11:52
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a4ce111cc89f580b8c4aad51bdb061acbdfde86b
136356-136374 --> 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/4
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
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/4
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/29046/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-05 19:53 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 19:53 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-05 21:06 dpdklab
2024-02-05 20:31 dpdklab
2024-02-05 19:55 dpdklab
2024-02-05 19:45 dpdklab
2024-02-05 19:36 dpdklab
2024-02-05 19:27 dpdklab
2024-02-05 19:25 dpdklab
2024-02-05 19:20 dpdklab
2024-02-05 19:20 dpdklab
2024-02-05 19:11 dpdklab
2024-02-03 6:37 dpdklab
2024-02-03 6:35 dpdklab
2024-02-03 6:35 dpdklab
2024-02-03 6:35 dpdklab
2024-02-03 6:34 dpdklab
2024-02-03 6:31 dpdklab
2024-02-03 6:21 dpdklab
2024-02-03 6:01 dpdklab
2024-02-03 5:57 dpdklab
2024-02-03 5:51 dpdklab
2024-02-03 5:50 dpdklab
2024-02-03 5:49 dpdklab
2024-02-03 5:46 dpdklab
2024-02-03 5:45 dpdklab
2024-02-03 5:43 dpdklab
2024-02-03 5:43 dpdklab
2024-02-03 5:41 dpdklab
2024-02-03 5:31 dpdklab
2024-02-03 5:27 dpdklab
2024-02-03 5:26 dpdklab
2024-02-03 5:26 dpdklab
2024-02-03 5:26 dpdklab
2024-02-03 5:26 dpdklab
2024-02-03 5:26 dpdklab
2024-02-03 5:25 dpdklab
2024-02-03 5:25 dpdklab
2024-02-03 5:25 dpdklab
2024-02-03 5:25 dpdklab
2024-02-03 5:25 dpdklab
2024-02-03 5:24 dpdklab
2024-02-03 5:24 dpdklab
2024-02-03 5:23 dpdklab
2024-02-03 5:23 dpdklab
2024-02-03 5:22 dpdklab
2024-02-03 5:22 dpdklab
2024-02-03 5:21 dpdklab
2024-02-03 5:21 dpdklab
2024-02-03 5:21 dpdklab
2024-02-03 5:21 dpdklab
2024-02-03 5:21 dpdklab
2024-02-03 5:20 dpdklab
2024-02-03 5:20 dpdklab
2024-02-03 5:20 dpdklab
2024-02-03 5:20 dpdklab
2024-02-03 5:19 dpdklab
2024-02-03 5:14 dpdklab
2024-02-03 5:14 dpdklab
2024-02-03 5:13 dpdklab
2024-02-03 5:05 dpdklab
2024-02-03 5:05 dpdklab
2024-02-03 5:02 dpdklab
2024-02-03 5:01 dpdklab
2024-02-03 5:00 dpdklab
2024-02-03 5:00 dpdklab
2024-02-03 4:57 dpdklab
2024-02-03 4:56 dpdklab
2024-02-03 4:56 dpdklab
2024-02-03 4:55 dpdklab
2024-02-03 4:54 dpdklab
2024-02-03 4:54 dpdklab
2024-02-03 4:54 dpdklab
2024-02-03 4:53 dpdklab
2024-02-03 4:53 dpdklab
2024-02-03 4:52 dpdklab
2024-02-03 4:52 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=65c13caa.050a0220.e8c9.0e67SMTPIN_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).