From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137082 [PATCH] maintainers: update for graph libraries
Date: Fri, 23 Feb 2024 18:25:21 -0800 (PST) [thread overview]
Message-ID: <65d95391.050a0220.4c5b2.0a6fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/137082
_Functional Testing PASS_
Submitter: Zhirun Yan <zhirun.yan@intel.com>
Date: Friday, February 23 2024 07:42:10
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137082 --> functional testing pass
Test environment and result as below:
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 XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4
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/29236/
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-24 2:25 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 2:25 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-24 15:43 dpdklab
2024-02-24 15:24 dpdklab
2024-02-24 14:56 dpdklab
2024-02-24 10:45 dpdklab
2024-02-24 6:49 dpdklab
2024-02-24 5:08 dpdklab
2024-02-24 4:36 dpdklab
2024-02-24 4:34 dpdklab
2024-02-24 4:29 dpdklab
2024-02-24 4:25 dpdklab
2024-02-24 4:24 dpdklab
2024-02-24 4:06 dpdklab
2024-02-24 4:06 dpdklab
2024-02-24 4:05 dpdklab
2024-02-24 4:05 dpdklab
2024-02-24 4:05 dpdklab
2024-02-24 4:04 dpdklab
2024-02-24 4:04 dpdklab
2024-02-24 4:04 dpdklab
2024-02-24 4:03 dpdklab
2024-02-24 4:01 dpdklab
2024-02-24 4:01 dpdklab
2024-02-24 4:00 dpdklab
2024-02-24 3:59 dpdklab
2024-02-24 3:58 dpdklab
2024-02-24 3:57 dpdklab
2024-02-24 3:57 dpdklab
2024-02-24 3:56 dpdklab
2024-02-24 3:56 dpdklab
2024-02-24 3:56 dpdklab
2024-02-24 3:56 dpdklab
2024-02-24 3:51 dpdklab
2024-02-24 3:49 dpdklab
2024-02-24 3:49 dpdklab
2024-02-24 3:48 dpdklab
2024-02-24 3:48 dpdklab
2024-02-24 3:48 dpdklab
2024-02-24 3:48 dpdklab
2024-02-24 3:47 dpdklab
2024-02-24 3:47 dpdklab
2024-02-24 3:47 dpdklab
2024-02-24 3:47 dpdklab
2024-02-24 3:47 dpdklab
2024-02-24 3:46 dpdklab
2024-02-24 3:45 dpdklab
2024-02-24 2:40 dpdklab
2024-02-24 2:38 dpdklab
2024-02-24 2:38 dpdklab
2024-02-24 2:37 dpdklab
2024-02-24 2:36 dpdklab
2024-02-24 2:36 dpdklab
2024-02-24 2:27 dpdklab
2024-02-24 2:24 dpdklab
2024-02-24 2:24 dpdklab
2024-02-24 2:22 dpdklab
2024-02-24 2:21 dpdklab
2024-02-24 2:19 dpdklab
2024-02-24 2:18 dpdklab
2024-02-24 2:15 dpdklab
2024-02-24 2:09 dpdklab
2024-02-24 2:05 dpdklab
2024-02-24 2:03 dpdklab
2024-02-24 2:02 dpdklab
2024-02-24 1:58 dpdklab
2024-02-24 1:38 dpdklab
2024-02-24 1:38 dpdklab
[not found] <20240223074210.907813-1-zhirun.yan@intel.com>
2024-02-23 7:19 ` qemudev
2024-02-23 7:23 ` qemudev
2024-02-23 7:42 ` checkpatch
2024-02-23 8:45 ` 0-day Robot
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=65d95391.050a0220.4c5b2.0a6fSMTPIN_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).