From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw129542 [PATCH] [1/1] net/sfc: add explicit fail path for
Date: Fri, 14 Jul 2023 06:13:17 -0700 (PDT) [thread overview]
Message-ID: <64b149ed.170a0220.d628b.ddb3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/129542
_Functional Testing PASS_
Submitter: Ivan Malov <ivan.malov@arknetworks.am>
Date: Friday, July 14 2023 12:41:02
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:655eb37b18b1b0dc4d106acdf0dfedde01cfb224
129542 --> 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/27075/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-07-14 13:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 13:13 dpdklab [this message]
2023-07-14 13:13 dpdklab
2023-07-14 13:17 dpdklab
2023-07-14 13:18 dpdklab
2023-07-14 13:20 dpdklab
2023-07-14 13:21 dpdklab
2023-07-14 13:22 dpdklab
2023-07-14 13:24 dpdklab
2023-07-14 13:29 dpdklab
2023-07-14 13:30 dpdklab
2023-07-14 13:33 dpdklab
2023-07-14 13:34 dpdklab
2023-07-14 13:34 dpdklab
2023-07-14 13:35 dpdklab
2023-07-14 13:37 dpdklab
2023-07-14 13:57 dpdklab
2023-07-14 13:58 dpdklab
2023-07-14 15:58 dpdklab
2023-07-14 21:34 dpdklab
2023-07-14 21:34 dpdklab
2023-07-15 1:56 dpdklab
2023-07-15 2:00 dpdklab
2023-07-15 2:16 dpdklab
2023-07-15 2:20 dpdklab
2023-07-15 2:25 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=64b149ed.170a0220.d628b.ddb3SMTPIN_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).