From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135809 [PATCH] net/vmxnet3: fix use of interrupts on Fre
Date: Tue, 09 Jan 2024 08:58:59 -0800 (PST) [thread overview]
Message-ID: <659d7b53.810a0220.4f6b7.80b3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135809
_Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Tuesday, January 09 2024 14:23:43
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6ef07151aac4b4d9601d547f94a996d1c71b3871
135809 --> testing pass
Test environment and result as below:
+---------------------+--------------------+
| Environment | dpdk_meson_compile |
+=====================+====================+
| Windows Server 2022 | PASS |
+---------------------+--------------------+
| FreeBSD 13 | PASS |
+---------------------+--------------------+
| CentOS Stream 8 | PASS |
+---------------------+--------------------+
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
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/28835/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-09 16:59 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 16:58 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-09 19:48 dpdklab
2024-01-09 18:15 dpdklab
2024-01-09 17:46 dpdklab
2024-01-09 17:45 dpdklab
2024-01-09 17:41 dpdklab
2024-01-09 17:31 dpdklab
2024-01-09 17:29 dpdklab
2024-01-09 17:29 dpdklab
2024-01-09 17:28 dpdklab
2024-01-09 17:27 dpdklab
2024-01-09 17:26 dpdklab
2024-01-09 17:24 dpdklab
2024-01-09 17:22 dpdklab
2024-01-09 17:22 dpdklab
2024-01-09 17:21 dpdklab
2024-01-09 17:19 dpdklab
2024-01-09 17:18 dpdklab
2024-01-09 17:18 dpdklab
2024-01-09 17:18 dpdklab
2024-01-09 17:16 dpdklab
2024-01-09 17:16 dpdklab
2024-01-09 17:15 dpdklab
2024-01-09 17:13 dpdklab
2024-01-09 17:12 dpdklab
2024-01-09 17:12 dpdklab
2024-01-09 17:12 dpdklab
2024-01-09 17:10 dpdklab
2024-01-09 17:10 dpdklab
2024-01-09 17:09 dpdklab
2024-01-09 17:09 dpdklab
2024-01-09 17:08 dpdklab
2024-01-09 17:07 dpdklab
2024-01-09 17:07 dpdklab
2024-01-09 17:07 dpdklab
2024-01-09 17:06 dpdklab
2024-01-09 17:06 dpdklab
2024-01-09 17:06 dpdklab
2024-01-09 17:05 dpdklab
2024-01-09 17:04 dpdklab
2024-01-09 17:03 dpdklab
2024-01-09 17:03 dpdklab
2024-01-09 17:02 dpdklab
2024-01-09 17:01 dpdklab
2024-01-09 17:01 dpdklab
2024-01-09 17:01 dpdklab
2024-01-09 17:01 dpdklab
2024-01-09 17:01 dpdklab
2024-01-09 17:01 dpdklab
2024-01-09 17:00 dpdklab
2024-01-09 17:00 dpdklab
2024-01-09 17:00 dpdklab
2024-01-09 17:00 dpdklab
2024-01-09 16:59 dpdklab
2024-01-09 16:58 dpdklab
2024-01-09 16:58 dpdklab
2024-01-09 16:57 dpdklab
2024-01-09 16:57 dpdklab
2024-01-09 16:57 dpdklab
2024-01-09 16:56 dpdklab
2024-01-09 16:56 dpdklab
2024-01-09 16:55 dpdklab
2024-01-09 16:54 dpdklab
2024-01-09 16:45 dpdklab
2024-01-09 16:42 dpdklab
2024-01-09 16:40 dpdklab
2024-01-09 16:40 dpdklab
2024-01-09 16:39 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=659d7b53.810a0220.4f6b7.80b3SMTPIN_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).