From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130838 [PATCH] [v2] net/netvsc: set the correct queue st
Date: Tue, 29 Aug 2023 20:32:04 -0700 (PDT) [thread overview]
Message-ID: <64eeb834.050a0220.64433.7fe7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130838
_Testing PASS_
Submitter: Long Li <longli@linuxonhyperv.com>
Date: Tuesday, August 29 2023 18:29:29
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b7b8de26f34d39c8aaded44d8a468da5e68f19da
130838 --> testing pass
Test environment and result as below:
+-----------------+----------------+
| Environment | dpdk_unit_test |
+=================+================+
| Debian Buster | PASS |
+-----------------+----------------+
| Debian Bullseye | PASS |
+-----------------+----------------+
| CentOS Stream 8 | PASS |
+-----------------+----------------+
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27464/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-30 3:32 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 3:32 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-30 7:39 dpdklab
2023-08-30 7:34 dpdklab
2023-08-30 7:29 dpdklab
2023-08-30 7:25 dpdklab
2023-08-30 7:09 dpdklab
2023-08-30 4:51 dpdklab
2023-08-30 4:14 dpdklab
2023-08-30 4:02 dpdklab
2023-08-30 3:57 dpdklab
2023-08-30 3:53 dpdklab
2023-08-30 3:49 dpdklab
2023-08-30 3:49 dpdklab
2023-08-30 3:45 dpdklab
2023-08-30 3:42 dpdklab
2023-08-30 3:41 dpdklab
2023-08-30 3:40 dpdklab
2023-08-30 3:39 dpdklab
2023-08-30 3:39 dpdklab
2023-08-30 3:38 dpdklab
2023-08-30 3:37 dpdklab
2023-08-30 3:37 dpdklab
2023-08-30 3:36 dpdklab
2023-08-30 3:36 dpdklab
2023-08-30 3:35 dpdklab
2023-08-30 3:35 dpdklab
2023-08-30 3:34 dpdklab
2023-08-30 3:33 dpdklab
2023-08-30 3:32 dpdklab
2023-08-30 3:32 dpdklab
2023-08-30 3:32 dpdklab
2023-08-30 3:32 dpdklab
2023-08-30 3:32 dpdklab
2023-08-30 3:32 dpdklab
2023-08-30 3:31 dpdklab
2023-08-30 3:31 dpdklab
2023-08-30 3:31 dpdklab
2023-08-30 3:31 dpdklab
2023-08-30 3:31 dpdklab
2023-08-30 3:30 dpdklab
2023-08-30 3:30 dpdklab
2023-08-30 3:30 dpdklab
2023-08-30 3:30 dpdklab
2023-08-30 3:29 dpdklab
2023-08-30 3:29 dpdklab
2023-08-30 3: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=64eeb834.050a0220.64433.7fe7SMTPIN_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).