From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw141989 [PATCH] net/mlx5: increase max pattern templates
Date: Mon, 01 Jul 2024 10:46:07 -0700 (PDT) [thread overview]
Message-ID: <6682eb5f.050a0220.fa50.7727SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240701102642.84841-1-getelson@nvidia.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/141989
_Functional Testing PASS_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Monday, July 01 2024 10:26:42
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:0ccf0d5588f7a9d25393351409b4c7497aa8dc74
141989 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: Unknown
Aggregate Results by Test Suite
+-----------------------------+--------+
| Test Suite | Result |
+=============================+========+
| scatter | PASS |
+-----------------------------+--------+
| unit_tests_mbuf | PASS |
+-----------------------------+--------+
| vhost_virtio_user_interrupt | PASS |
+-----------------------------+--------+
| virtio_smoke | PASS |
+-----------------------------+--------+
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: Unknown
Aggregate Results by Test Suite
+-----------------------------+--------+
| Test Suite | Result |
+=============================+========+
| scatter | PASS |
+-----------------------------+--------+
| unit_tests_mbuf | PASS |
+-----------------------------+--------+
| vhost_virtio_user_interrupt | PASS |
+-----------------------------+--------+
| virtio_smoke | PASS |
+-----------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30357/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-07-01 17:46 UTC|newest]
Thread overview: 115+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240701102642.84841-1-getelson@nvidia.com>
2024-07-01 10:00 ` qemudev
2024-07-01 10:05 ` qemudev
2024-07-01 10:28 ` checkpatch
2024-07-01 11:25 ` 0-day Robot
2024-07-01 17:27 ` dpdklab
2024-07-01 17:29 ` |PENDING| " dpdklab
2024-07-01 17:31 ` |SUCCESS| " dpdklab
2024-07-01 17:33 ` |PENDING| " dpdklab
2024-07-01 17:39 ` dpdklab
2024-07-01 17:42 ` |SUCCESS| " dpdklab
2024-07-01 17:42 ` |PENDING| " dpdklab
2024-07-01 17:42 ` dpdklab
2024-07-01 17:46 ` dpdklab [this message]
2024-07-01 17:47 ` |SUCCESS| " dpdklab
2024-07-01 17:47 ` dpdklab
2024-07-01 17:48 ` dpdklab
2024-07-01 17:48 ` dpdklab
2024-07-01 17:53 ` dpdklab
2024-07-01 18:01 ` |PENDING| " dpdklab
2024-07-01 18:05 ` |SUCCESS| " dpdklab
2024-07-01 18:11 ` |PENDING| " dpdklab
2024-07-01 18:16 ` dpdklab
2024-07-01 18:16 ` |SUCCESS| " dpdklab
2024-07-01 18:21 ` dpdklab
2024-07-01 18:26 ` dpdklab
2024-07-01 18:26 ` |PENDING| " dpdklab
2024-07-01 18:26 ` dpdklab
2024-07-01 18:30 ` dpdklab
2024-07-01 18:30 ` |SUCCESS| " dpdklab
2024-07-01 18:32 ` |PENDING| " dpdklab
2024-07-01 18:32 ` dpdklab
2024-07-01 18:32 ` dpdklab
2024-07-01 18:34 ` |SUCCESS| " dpdklab
2024-07-01 18:34 ` |PENDING| " dpdklab
2024-07-01 18:36 ` dpdklab
2024-07-01 18:38 ` dpdklab
2024-07-01 18:47 ` dpdklab
2024-07-01 18:51 ` dpdklab
2024-07-01 18:53 ` dpdklab
2024-07-01 18:53 ` dpdklab
2024-07-01 18:53 ` |SUCCESS| " dpdklab
2024-07-01 18:54 ` |PENDING| " dpdklab
2024-07-01 18:59 ` dpdklab
2024-07-01 18:59 ` dpdklab
2024-07-01 19:00 ` |SUCCESS| " dpdklab
2024-07-01 19:00 ` |PENDING| " dpdklab
2024-07-01 19:10 ` dpdklab
2024-07-01 19:10 ` dpdklab
2024-07-01 19:11 ` dpdklab
2024-07-01 19:13 ` dpdklab
2024-07-01 19:16 ` dpdklab
2024-07-01 19:18 ` dpdklab
2024-07-01 19:19 ` dpdklab
2024-07-01 19:20 ` dpdklab
2024-07-01 19:21 ` dpdklab
2024-07-01 19:26 ` dpdklab
2024-07-01 19:27 ` dpdklab
2024-07-01 19:27 ` dpdklab
2024-07-01 19:27 ` dpdklab
2024-07-01 19:28 ` dpdklab
2024-07-01 19:30 ` dpdklab
2024-07-01 19:30 ` dpdklab
2024-07-01 19:33 ` dpdklab
2024-07-01 19:37 ` dpdklab
2024-07-01 19:39 ` dpdklab
2024-07-01 19:40 ` dpdklab
2024-07-01 19:40 ` dpdklab
2024-07-01 19:41 ` dpdklab
2024-07-01 19:43 ` dpdklab
2024-07-01 19:44 ` dpdklab
2024-07-01 19:44 ` dpdklab
2024-07-01 19:45 ` dpdklab
2024-07-01 19:46 ` dpdklab
2024-07-01 19:47 ` dpdklab
2024-07-01 19:48 ` dpdklab
2024-07-01 19:49 ` dpdklab
2024-07-01 19:51 ` dpdklab
2024-07-01 19:52 ` dpdklab
2024-07-01 19:55 ` dpdklab
2024-07-01 19:56 ` dpdklab
2024-07-01 19:57 ` dpdklab
2024-07-01 19:57 ` |SUCCESS| " dpdklab
2024-07-01 20:01 ` |PENDING| " dpdklab
2024-07-01 20:02 ` |SUCCESS| " dpdklab
2024-07-01 20:05 ` |PENDING| " dpdklab
2024-07-01 20:07 ` dpdklab
2024-07-01 20:09 ` dpdklab
2024-07-01 20:12 ` dpdklab
2024-07-01 20:14 ` dpdklab
2024-07-01 20:15 ` dpdklab
2024-07-01 20:16 ` dpdklab
2024-07-01 20:21 ` dpdklab
2024-07-01 20:22 ` dpdklab
2024-07-01 20:24 ` dpdklab
2024-07-01 20:24 ` dpdklab
2024-07-01 20:30 ` dpdklab
2024-07-01 20:33 ` |SUCCESS| " dpdklab
2024-07-01 20:33 ` |PENDING| " dpdklab
2024-07-01 20:34 ` dpdklab
2024-07-01 20:39 ` dpdklab
2024-07-01 20:40 ` dpdklab
2024-07-01 20:41 ` dpdklab
2024-07-01 21:02 ` dpdklab
2024-07-01 21:07 ` dpdklab
2024-07-01 21:08 ` dpdklab
2024-07-01 21:09 ` |SUCCESS| " dpdklab
2024-07-01 21:10 ` dpdklab
2024-07-01 21:10 ` dpdklab
2024-07-01 21:15 ` |PENDING| " dpdklab
2024-07-01 21:29 ` dpdklab
2024-07-01 21:47 ` dpdklab
2024-07-01 21:50 ` |SUCCESS| " dpdklab
2024-07-02 12:59 ` dpdklab
2024-07-02 13:08 ` dpdklab
2024-07-02 13:21 ` 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=6682eb5f.050a0220.fa50.7727SMTPIN_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).