From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw132635 [PATCH] event/cnxk: update fc check to use SQEs
Date: Mon, 16 Oct 2023 13:35:21 -0700 (PDT) [thread overview]
Message-ID: <652d9e89.050a0220.7a40c.01a1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/132635
_Functional Testing PASS_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Monday, October 16 2023 15:10:55
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:441e777b85f1ea1eb6a2a970ff5d5c8e027f520c
132635 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27943/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-16 20:35 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 20:35 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-18 20:58 dpdklab
2023-10-18 0:12 dpdklab
2023-10-18 0:07 dpdklab
2023-10-17 0:39 dpdklab
2023-10-16 22:04 dpdklab
2023-10-16 21:13 dpdklab
2023-10-16 21:12 dpdklab
2023-10-16 21:11 dpdklab
2023-10-16 21:11 dpdklab
2023-10-16 21:10 dpdklab
2023-10-16 21:08 dpdklab
2023-10-16 21:01 dpdklab
2023-10-16 20:56 dpdklab
2023-10-16 20:56 dpdklab
2023-10-16 20:54 dpdklab
2023-10-16 20:53 dpdklab
2023-10-16 20:52 dpdklab
2023-10-16 20:50 dpdklab
2023-10-16 20:49 dpdklab
2023-10-16 20:49 dpdklab
2023-10-16 20:47 dpdklab
2023-10-16 20:46 dpdklab
2023-10-16 20:45 dpdklab
2023-10-16 20:45 dpdklab
2023-10-16 20:45 dpdklab
2023-10-16 20:44 dpdklab
2023-10-16 20:44 dpdklab
2023-10-16 20:44 dpdklab
2023-10-16 20:44 dpdklab
2023-10-16 20:44 dpdklab
2023-10-16 20:43 dpdklab
2023-10-16 20:43 dpdklab
2023-10-16 20:42 dpdklab
2023-10-16 20:41 dpdklab
2023-10-16 20:40 dpdklab
2023-10-16 20:39 dpdklab
2023-10-16 20:39 dpdklab
2023-10-16 20:39 dpdklab
2023-10-16 20:39 dpdklab
2023-10-16 20:38 dpdklab
2023-10-16 20:38 dpdklab
2023-10-16 20:38 dpdklab
2023-10-16 20:37 dpdklab
2023-10-16 20:37 dpdklab
2023-10-16 20:36 dpdklab
2023-10-16 20:34 dpdklab
2023-10-16 20:30 dpdklab
[not found] <20231016151055.2436-1-pbhagavatula@marvell.com>
2023-10-16 14:51 ` qemudev
2023-10-16 14:56 ` qemudev
2023-10-16 15:59 ` 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=652d9e89.050a0220.7a40c.01a1SMTPIN_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).