automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135627 [PATCH] net/hns3: don't support QinQ insert for V
Date: Thu, 28 Dec 2023 05:03:03 -0800 (PST)	[thread overview]
Message-ID: <658d7207.050a0220.3a5f5.52e7SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/135627

_Functional Testing PASS_

Submitter: Jie Hai <haijie1@huawei.com>
Date: Thursday, December 28 2023 12:14:28 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:6ef07151aac4b4d9601d547f94a996d1c71b3871

135627 --> 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 82599ES 10000 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 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/28751/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2023-12-28 13:03 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-28 13:03 dpdklab [this message]
2023-12-28 13:03 dpdklab
2023-12-28 13:03 dpdklab
2023-12-28 13:04 dpdklab
2023-12-28 13:04 dpdklab
2023-12-28 13:04 dpdklab
2023-12-28 13:05 dpdklab
2023-12-28 13:06 dpdklab
2023-12-28 13:10 dpdklab
2023-12-28 13:10 dpdklab
2023-12-28 13:11 dpdklab
2023-12-28 13:11 dpdklab
2023-12-28 13:11 dpdklab
2023-12-28 13:11 dpdklab
2023-12-28 13:11 dpdklab
2023-12-28 13:11 dpdklab
2023-12-28 13:12 dpdklab
2023-12-28 13:12 dpdklab
2023-12-28 13:12 dpdklab
2023-12-28 13:12 dpdklab
2023-12-28 13:13 dpdklab
2023-12-28 13:13 dpdklab
2023-12-28 13:13 dpdklab
2023-12-28 13:15 dpdklab
2023-12-28 13:15 dpdklab
2023-12-28 13:15 dpdklab
2023-12-28 13:15 dpdklab
2023-12-28 13:16 dpdklab
2023-12-28 13:16 dpdklab
2023-12-28 13:16 dpdklab
2023-12-28 13:16 dpdklab
2023-12-28 13:17 dpdklab
2023-12-28 13:17 dpdklab
2023-12-28 13:17 dpdklab
2023-12-28 13:17 dpdklab
2023-12-28 13:17 dpdklab
2023-12-28 13:17 dpdklab
2023-12-28 13:17 dpdklab
2023-12-28 13:18 dpdklab
2023-12-28 13:18 dpdklab
2023-12-28 13:19 dpdklab
2023-12-28 13:19 dpdklab
2023-12-28 13:19 dpdklab
2023-12-28 13:19 dpdklab
2023-12-28 13:39 dpdklab
2023-12-28 13:40 dpdklab
2023-12-28 13:40 dpdklab
2023-12-28 13:41 dpdklab
2023-12-28 13:41 dpdklab
2023-12-28 13:41 dpdklab
2023-12-28 13:42 dpdklab
2023-12-28 13:45 dpdklab
2023-12-28 13:46 dpdklab
2023-12-28 13:46 dpdklab
2023-12-28 13:47 dpdklab
2023-12-28 13:47 dpdklab
2023-12-28 13:48 dpdklab
2023-12-28 13:48 dpdklab
2023-12-28 13:49 dpdklab
2023-12-28 13:49 dpdklab
2023-12-28 13:50 dpdklab
2023-12-28 13:51 dpdklab
2023-12-28 13:52 dpdklab
2023-12-28 13:52 dpdklab
2023-12-28 13:57 dpdklab
2023-12-28 14:01 dpdklab
2023-12-28 14:02 dpdklab
2023-12-28 14:29 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=658d7207.050a0220.3a5f5.52e7SMTPIN_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).