From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130704-130730 [PATCH] [27/27] net/nfp: extend the usage
Date: Thu, 24 Aug 2023 23:39:54 -0700 (PDT) [thread overview]
Message-ID: <64e84cba.0d0a0220.36fe0.5f81SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/130730
_Functional Testing PASS_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Thursday, August 24 2023 11:09:56
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:934c0ccbfe881d861d749a9f8fb146d5f134c04c
130704-130730 --> functional testing pass
Test environment and result as below:
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
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27438/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-25 6:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 6:39 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-25 17:40 dpdklab
2023-08-25 17:24 dpdklab
2023-08-25 9:01 dpdklab
2023-08-25 8:44 dpdklab
2023-08-25 8:40 dpdklab
2023-08-25 8:29 dpdklab
2023-08-25 8:23 dpdklab
2023-08-25 7:20 dpdklab
2023-08-25 7:13 dpdklab
2023-08-25 7:07 dpdklab
2023-08-25 6:56 dpdklab
2023-08-25 6:54 dpdklab
2023-08-25 6:53 dpdklab
2023-08-25 6:53 dpdklab
2023-08-25 6:43 dpdklab
2023-08-25 6:41 dpdklab
2023-08-25 6:39 dpdklab
2023-08-25 6:38 dpdklab
2023-08-25 6:36 dpdklab
2023-08-25 6:31 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=64e84cba.0d0a0220.36fe0.5f81SMTPIN_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).