From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136241-136245 [PATCH] [v5,5/5] net/gve: add RSS redirect
Date: Wed, 31 Jan 2024 14:49:14 -0800 (PST) [thread overview]
Message-ID: <65bace6a.050a0220.e2fd0.8d1fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136245
_Testing PASS_
Submitter: Joshua Washington <joshwash@google.com>
Date: Wednesday, January 31 2024 22:13:08
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:8e5cbd3d1f6f077abdcb2ef4de027603ba9af5ca
136241-136245 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| CentOS Stream 9 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| FreeBSD 13.2 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| Fedora 38 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 11.3.0
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29007/
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-31 22:49 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 22:49 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-01 0:13 dpdklab
2024-01-31 23:46 dpdklab
2024-01-31 23:34 dpdklab
2024-01-31 23:33 dpdklab
2024-01-31 23:30 dpdklab
2024-01-31 23:29 dpdklab
2024-01-31 23:29 dpdklab
2024-01-31 23:28 dpdklab
2024-01-31 23:28 dpdklab
2024-01-31 23:28 dpdklab
2024-01-31 23:25 dpdklab
2024-01-31 23:24 dpdklab
2024-01-31 23:24 dpdklab
2024-01-31 23:22 dpdklab
2024-01-31 23:19 dpdklab
2024-01-31 23:19 dpdklab
2024-01-31 23:17 dpdklab
2024-01-31 23:14 dpdklab
2024-01-31 23:12 dpdklab
2024-01-31 23:11 dpdklab
2024-01-31 23:11 dpdklab
2024-01-31 23:10 dpdklab
2024-01-31 23:10 dpdklab
2024-01-31 23:10 dpdklab
2024-01-31 23:10 dpdklab
2024-01-31 23:10 dpdklab
2024-01-31 23:10 dpdklab
2024-01-31 23:09 dpdklab
2024-01-31 23:09 dpdklab
2024-01-31 23:08 dpdklab
2024-01-31 23:08 dpdklab
2024-01-31 23:08 dpdklab
2024-01-31 23:08 dpdklab
2024-01-31 23:08 dpdklab
2024-01-31 23:04 dpdklab
2024-01-31 23:03 dpdklab
2024-01-31 23:03 dpdklab
2024-01-31 23:02 dpdklab
2024-01-31 23:02 dpdklab
2024-01-31 23:02 dpdklab
2024-01-31 23:01 dpdklab
2024-01-31 23:01 dpdklab
2024-01-31 23:01 dpdklab
2024-01-31 23:00 dpdklab
2024-01-31 22:59 dpdklab
2024-01-31 22:58 dpdklab
2024-01-31 22:56 dpdklab
2024-01-31 22:56 dpdklab
2024-01-31 22:55 dpdklab
2024-01-31 22:55 dpdklab
2024-01-31 22:54 dpdklab
2024-01-31 22:53 dpdklab
2024-01-31 22:53 dpdklab
2024-01-31 22:52 dpdklab
2024-01-31 22:51 dpdklab
2024-01-31 22:51 dpdklab
2024-01-31 22:51 dpdklab
2024-01-31 22:51 dpdklab
2024-01-31 22:50 dpdklab
2024-01-31 22:50 dpdklab
2024-01-31 22:50 dpdklab
2024-01-31 22:49 dpdklab
2024-01-31 22:49 dpdklab
2024-01-31 22:49 dpdklab
2024-01-31 22:49 dpdklab
2024-01-31 22:48 dpdklab
2024-01-31 22:48 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=65bace6a.050a0220.e2fd0.8d1fSMTPIN_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).