From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138483 [PATCH] [v3] net/netvsc: fix number Tx queues > R
Date: Tue, 19 Mar 2024 12:52:14 -0700 (PDT) [thread overview]
Message-ID: <65f9ecee.050a0220.7502a.d89bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <PA4PR83MB0526053A870E8358B7CB3643972C2@PA4PR83MB0526.EURPRD83.prod.outlook.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138483
_Testing PASS_
Submitter: Alan Elder <alan.elder@microsoft.com>
Date: Tuesday, March 19 2024 14:16:46
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:53483ccd6dee01b8930e7a8c391472453bbe642d
138483 --> testing pass
Test environment and result as below:
+--------------+----------------------+
| Environment | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | PASS |
+--------------+----------------------+
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29596/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-19 19:52 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <PA4PR83MB0526053A870E8358B7CB3643972C2@PA4PR83MB0526.EURPRD83.prod.outlook.com>
2024-03-19 13:53 ` |SUCCESS| pw138483 [PATCH v3] net/netvsc: fix number Tx queues > Rx queues qemudev
2024-03-19 13:58 ` qemudev
2024-03-19 14:18 ` checkpatch
2024-03-19 15:03 ` 0-day Robot
2024-03-19 17:25 ` |SUCCESS| pw138483 [PATCH] [v3] net/netvsc: fix number Tx queues > R dpdklab
2024-03-19 17:27 ` dpdklab
2024-03-19 17:30 ` dpdklab
2024-03-19 17:31 ` dpdklab
2024-03-19 17:31 ` dpdklab
2024-03-19 17:32 ` dpdklab
2024-03-19 17:35 ` dpdklab
2024-03-19 17:35 ` dpdklab
2024-03-19 17:36 ` dpdklab
2024-03-19 17:41 ` dpdklab
2024-03-19 17:41 ` dpdklab
2024-03-19 17:41 ` dpdklab
2024-03-19 17:42 ` dpdklab
2024-03-19 17:52 ` dpdklab
2024-03-19 18:07 ` dpdklab
2024-03-19 18:08 ` dpdklab
2024-03-19 18:17 ` dpdklab
2024-03-19 18:18 ` dpdklab
2024-03-19 18:19 ` dpdklab
2024-03-19 18:19 ` dpdklab
2024-03-19 18:20 ` dpdklab
2024-03-19 18:20 ` dpdklab
2024-03-19 18:20 ` dpdklab
2024-03-19 18:21 ` dpdklab
2024-03-19 18:21 ` dpdklab
2024-03-19 18:22 ` dpdklab
2024-03-19 18:22 ` dpdklab
2024-03-19 18:23 ` dpdklab
2024-03-19 18:23 ` dpdklab
2024-03-19 18:24 ` dpdklab
2024-03-19 18:24 ` dpdklab
2024-03-19 18:25 ` dpdklab
2024-03-19 18:25 ` dpdklab
2024-03-19 18:25 ` dpdklab
2024-03-19 18:26 ` dpdklab
2024-03-19 18:30 ` dpdklab
2024-03-19 18:32 ` dpdklab
2024-03-19 18:32 ` dpdklab
2024-03-19 18:37 ` dpdklab
2024-03-19 18:37 ` dpdklab
2024-03-19 18:37 ` dpdklab
2024-03-19 18:39 ` dpdklab
2024-03-19 18:45 ` dpdklab
2024-03-19 18:45 ` dpdklab
2024-03-19 18:50 ` dpdklab
2024-03-19 18:55 ` dpdklab
2024-03-19 18:56 ` dpdklab
2024-03-19 18:56 ` dpdklab
2024-03-19 18:57 ` dpdklab
2024-03-19 18:57 ` dpdklab
2024-03-19 18:57 ` dpdklab
2024-03-19 18:59 ` dpdklab
2024-03-19 19:00 ` dpdklab
2024-03-19 19:00 ` dpdklab
2024-03-19 19:01 ` dpdklab
2024-03-19 19:02 ` dpdklab
2024-03-19 19:03 ` dpdklab
2024-03-19 19:04 ` dpdklab
2024-03-19 19:04 ` dpdklab
2024-03-19 19:11 ` dpdklab
2024-03-19 19:12 ` dpdklab
2024-03-19 19:13 ` dpdklab
2024-03-19 19:14 ` dpdklab
2024-03-19 19:24 ` dpdklab
2024-03-19 19:25 ` dpdklab
2024-03-19 19:29 ` dpdklab
2024-03-19 19:37 ` dpdklab
2024-03-19 19:38 ` dpdklab
2024-03-19 19:38 ` dpdklab
2024-03-19 19:40 ` dpdklab
2024-03-19 19:43 ` dpdklab
2024-03-19 19:52 ` dpdklab [this message]
2024-03-19 19:57 ` dpdklab
2024-03-19 20:01 ` dpdklab
2024-03-21 6:31 ` dpdklab
2024-03-21 7:28 ` 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=65f9ecee.050a0220.7502a.d89bSMTPIN_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).