From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136843 [PATCH] [v6] net/netvsc: fix parsing of VLAN meta
Date: Fri, 16 Feb 2024 07:48:46 -0800 (PST) [thread overview]
Message-ID: <65cf83de.b00a0220.a14dc.078fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/136843
_Functional Testing PASS_
Submitter: Alan Elder <alan.elder@microsoft.com>
Date: Friday, February 16 2024 09:43:00
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:31d9d436f263a3f4313ad4c029a9905d6be6cbd6
136843 --> 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 XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
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/3
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29169/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-16 15:48 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 15:48 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-17 2:53 dpdklab
2024-02-16 12:05 dpdklab
2024-02-16 12:02 dpdklab
2024-02-16 11:58 dpdklab
2024-02-16 11:50 dpdklab
2024-02-16 11:31 dpdklab
2024-02-16 11:26 dpdklab
2024-02-16 11:16 dpdklab
2024-02-16 11:15 dpdklab
2024-02-16 11:13 dpdklab
2024-02-16 11:13 dpdklab
2024-02-16 11:13 dpdklab
2024-02-16 11:11 dpdklab
2024-02-16 11:10 dpdklab
2024-02-16 11:10 dpdklab
2024-02-16 11:10 dpdklab
2024-02-16 11:09 dpdklab
2024-02-16 11:08 dpdklab
2024-02-16 11:07 dpdklab
2024-02-16 11:07 dpdklab
2024-02-16 11:07 dpdklab
2024-02-16 11:06 dpdklab
2024-02-16 11:06 dpdklab
2024-02-16 11:06 dpdklab
2024-02-16 11:05 dpdklab
2024-02-16 11:05 dpdklab
2024-02-16 11:04 dpdklab
2024-02-16 11:03 dpdklab
2024-02-16 10:58 dpdklab
2024-02-16 10:56 dpdklab
2024-02-16 10:51 dpdklab
2024-02-16 10:50 dpdklab
2024-02-16 10:50 dpdklab
2024-02-16 10:50 dpdklab
2024-02-16 10:50 dpdklab
2024-02-16 10:49 dpdklab
2024-02-16 10:48 dpdklab
2024-02-16 10:47 dpdklab
2024-02-16 10:47 dpdklab
2024-02-16 10:47 dpdklab
2024-02-16 10:47 dpdklab
2024-02-16 10:40 dpdklab
2024-02-16 10:40 dpdklab
2024-02-16 10:39 dpdklab
2024-02-16 10:39 dpdklab
2024-02-16 10:38 dpdklab
2024-02-16 10:37 dpdklab
2024-02-16 10:37 dpdklab
2024-02-16 10:37 dpdklab
2024-02-16 10:36 dpdklab
2024-02-16 10:36 dpdklab
2024-02-16 10:35 dpdklab
2024-02-16 10:33 dpdklab
2024-02-16 10:30 dpdklab
2024-02-16 10:30 dpdklab
2024-02-16 10:29 dpdklab
2024-02-16 10:28 dpdklab
2024-02-16 10:27 dpdklab
2024-02-16 10:26 dpdklab
2024-02-16 10:25 dpdklab
2024-02-16 10:25 dpdklab
2024-02-16 10:25 dpdklab
2024-02-16 10:21 dpdklab
2024-02-16 10:21 dpdklab
2024-02-16 10:20 dpdklab
2024-02-16 10:19 dpdklab
2024-02-16 10:16 dpdklab
2024-02-16 10:16 dpdklab
2024-02-16 10:16 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=65cf83de.b00a0220.a14dc.078fSMTPIN_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).