From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw128450 [PATCH] net/nfp: fix set IPv6 flow action can't g
Date: Fri, 09 Jun 2023 01:14:52 -0700 (PDT) [thread overview]
Message-ID: <6482df7c.170a0220.fc363.4d71SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/128450
_Functional Testing PASS_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Friday, June 09 2023 06:19:19
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2125ed73e10ec028dd1b5fd6105aef80456e659e
128450 --> 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/26603/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-06-09 8:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 8:14 dpdklab [this message]
2023-06-09 8:15 dpdklab
2023-06-09 8:16 dpdklab
2023-06-09 8:23 dpdklab
2023-06-09 8:23 dpdklab
2023-06-09 8:24 dpdklab
2023-06-09 8:38 dpdklab
2023-06-09 8:50 dpdklab
2023-06-09 8:57 dpdklab
2023-06-09 9:10 dpdklab
2023-06-09 9:12 dpdklab
2023-06-09 9:13 dpdklab
2023-06-09 9:14 dpdklab
2023-06-09 9:17 dpdklab
2023-06-09 9:18 dpdklab
2023-06-09 9:20 dpdklab
2023-06-09 9:21 dpdklab
2023-06-09 9:32 dpdklab
2023-06-09 9:32 dpdklab
2023-06-09 12:46 dpdklab
2023-06-09 12:47 dpdklab
2023-06-09 18:00 dpdklab
2023-06-09 18:05 dpdklab
2023-06-09 18:21 dpdklab
2023-06-09 18:25 dpdklab
2023-06-09 18:36 dpdklab
2023-06-10 19:22 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=6482df7c.170a0220.fc363.4d71SMTPIN_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).