From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135878 [PATCH] net/mlx5: fix GENEVE TLV option managemen
Date: Mon, 15 Jan 2024 05:39:58 -0800 (PST) [thread overview]
Message-ID: <65a535ae.050a0220.ba004.d381SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135878
_Testing PASS_
Submitter: Michael Baum <michaelba@nvidia.com>
Date: Monday, January 15 2024 12:13:26
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:30468d404a3447cae8797576e885b9831bb88391
135878 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
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/28866/
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-15 13:40 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 13:39 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-16 20:31 dpdklab
2024-01-15 14:12 dpdklab
2024-01-15 13:58 dpdklab
2024-01-15 13:57 dpdklab
2024-01-15 13:54 dpdklab
2024-01-15 13:52 dpdklab
2024-01-15 13:51 dpdklab
2024-01-15 13:50 dpdklab
2024-01-15 13:49 dpdklab
2024-01-15 13:46 dpdklab
2024-01-15 13:45 dpdklab
2024-01-15 13:45 dpdklab
2024-01-15 13:44 dpdklab
2024-01-15 13:43 dpdklab
2024-01-15 13:43 dpdklab
2024-01-15 13:41 dpdklab
2024-01-15 13:41 dpdklab
2024-01-15 13:40 dpdklab
2024-01-15 13:40 dpdklab
2024-01-15 13:38 dpdklab
2024-01-15 13:38 dpdklab
2024-01-15 13:30 dpdklab
2024-01-15 13:29 dpdklab
2024-01-15 13:21 dpdklab
2024-01-15 13:21 dpdklab
2024-01-15 13:20 dpdklab
2024-01-15 13:20 dpdklab
2024-01-15 13:20 dpdklab
2024-01-15 13:20 dpdklab
2024-01-15 13:19 dpdklab
2024-01-15 13:19 dpdklab
2024-01-15 13:18 dpdklab
2024-01-15 13:17 dpdklab
2024-01-15 13:17 dpdklab
2024-01-15 13:17 dpdklab
2024-01-15 13:16 dpdklab
2024-01-15 13:15 dpdklab
2024-01-15 13:14 dpdklab
2024-01-15 13:13 dpdklab
2024-01-15 13:13 dpdklab
2024-01-15 13:12 dpdklab
2024-01-15 13:07 dpdklab
2024-01-15 13:07 dpdklab
2024-01-15 13:07 dpdklab
2024-01-15 13:07 dpdklab
2024-01-15 13:06 dpdklab
2024-01-15 13:06 dpdklab
2024-01-15 13:06 dpdklab
2024-01-15 13:06 dpdklab
2024-01-15 13:06 dpdklab
2024-01-15 13:05 dpdklab
2024-01-15 13:05 dpdklab
2024-01-15 13:05 dpdklab
2024-01-15 13:04 dpdklab
2024-01-15 13:03 dpdklab
2024-01-15 13:03 dpdklab
2024-01-15 13:03 dpdklab
2024-01-15 13:02 dpdklab
2024-01-15 13:02 dpdklab
2024-01-15 13:02 dpdklab
2024-01-15 13:01 dpdklab
2024-01-15 13:01 dpdklab
2024-01-15 13:00 dpdklab
2024-01-15 12:55 dpdklab
2024-01-15 12:53 dpdklab
2024-01-15 12:53 dpdklab
2024-01-15 12:52 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=65a535ae.050a0220.ba004.d381SMTPIN_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).