From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137514 [PATCH] net/tap: allow more that 4 queues
Date: Sun, 03 Mar 2024 17:24:12 -0800 (PST) [thread overview]
Message-ID: <65e522bc.050a0220.ef289.f4fbSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240229175620.122949-1-stephen@networkplumber.org>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137514
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, February 29 2024 17:56:18
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:f60df26faa3c90fc66d356e16347acd046971441
137514 --> testing pass
Test environment and result as below:
+--------------+----------------------+
| Environment | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | PASS |
+--------------+----------------------+
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29346/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
prev parent reply other threads:[~2024-03-04 1:24 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240229175620.122949-1-stephen@networkplumber.org>
2024-02-29 17:34 ` qemudev
2024-02-29 17:38 ` qemudev
2024-02-29 17:57 ` checkpatch
2024-02-29 20:44 ` 0-day Robot
2024-02-29 21:59 ` dpdklab
2024-02-29 22:13 ` dpdklab
2024-02-29 22:14 ` dpdklab
2024-02-29 22:14 ` dpdklab
2024-02-29 22:15 ` dpdklab
2024-02-29 22:16 ` dpdklab
2024-02-29 22:20 ` dpdklab
2024-02-29 22:20 ` dpdklab
2024-02-29 22:36 ` dpdklab
2024-02-29 22:50 ` dpdklab
2024-02-29 22:51 ` dpdklab
2024-02-29 22:51 ` dpdklab
2024-02-29 22:55 ` dpdklab
2024-02-29 23:02 ` dpdklab
2024-02-29 23:03 ` dpdklab
2024-02-29 23:08 ` dpdklab
2024-02-29 23:09 ` dpdklab
2024-02-29 23:36 ` dpdklab
2024-03-01 1:42 ` dpdklab
2024-03-01 1:44 ` dpdklab
2024-03-01 1:49 ` dpdklab
2024-03-01 1:50 ` dpdklab
2024-03-01 1:52 ` dpdklab
2024-03-01 1:54 ` dpdklab
2024-03-01 1:56 ` dpdklab
2024-03-01 1:56 ` dpdklab
2024-03-01 2:04 ` dpdklab
2024-03-01 2:07 ` dpdklab
2024-03-01 2:07 ` dpdklab
2024-03-01 2:07 ` dpdklab
2024-03-01 2:09 ` dpdklab
2024-03-01 2:10 ` dpdklab
2024-03-01 2:10 ` dpdklab
2024-03-01 2:10 ` dpdklab
2024-03-01 2:10 ` dpdklab
2024-03-01 2:10 ` dpdklab
2024-03-01 2:10 ` dpdklab
2024-03-01 2:12 ` dpdklab
2024-03-01 2:13 ` dpdklab
2024-03-01 2:13 ` dpdklab
2024-03-01 2:13 ` dpdklab
2024-03-01 2:14 ` dpdklab
2024-03-01 2:14 ` dpdklab
2024-03-01 2:14 ` dpdklab
2024-03-01 2:15 ` dpdklab
2024-03-01 2:15 ` dpdklab
2024-03-01 2:15 ` dpdklab
2024-03-01 2:15 ` dpdklab
2024-03-01 2:16 ` dpdklab
2024-03-01 2:16 ` dpdklab
2024-03-01 2:17 ` dpdklab
2024-03-01 2:17 ` dpdklab
2024-03-01 2:18 ` dpdklab
2024-03-01 2:18 ` dpdklab
2024-03-01 2:18 ` dpdklab
2024-03-01 2:21 ` dpdklab
2024-03-01 2:22 ` dpdklab
2024-03-01 2:23 ` dpdklab
2024-03-01 2:47 ` dpdklab
2024-03-01 3:00 ` dpdklab
2024-03-01 3:02 ` dpdklab
2024-03-01 3:43 ` dpdklab
2024-03-01 8:07 ` dpdklab
2024-03-01 11:58 ` dpdklab
2024-03-01 12:00 ` dpdklab
2024-03-01 12:04 ` dpdklab
2024-03-01 12:07 ` dpdklab
2024-03-02 12:26 ` dpdklab
2024-03-04 0:16 ` dpdklab
2024-03-04 0:48 ` dpdklab
2024-03-04 1:24 ` dpdklab [this message]
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=65e522bc.050a0220.ef289.f4fbSMTPIN_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).