From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136412-136415 [PATCH] [v7,4/4] net/mlx5: add compare ite
Date: Tue, 06 Feb 2024 03:23:42 -0800 (PST) [thread overview]
Message-ID: <65c216be.050a0220.b348a.4ac2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136415
_Testing PASS_
Submitter: Suanming Mou <suanmingm@nvidia.com>
Date: Tuesday, February 06 2024 02:06:25
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:f8ecc0053ca52cb2310a9e1834ea583167a793cd
136412-136415 --> testing pass
Test environment and result as below:
+-----------------+----------+
| Environment | abi_test |
+=================+==========+
| Debian Bullseye | PASS |
+-----------------+----------+
| CentOS Stream 8 | PASS |
+-----------------+----------+
| Debian Buster | PASS |
+-----------------+----------+
| CentOS Stream 9 | PASS |
+-----------------+----------+
| Fedora 37 | PASS |
+-----------------+----------+
| Fedora 38 | PASS |
+-----------------+----------+
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
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29052/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-06 11:23 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 11:23 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-06 12:38 dpdklab
2024-02-06 12:33 dpdklab
2024-02-06 12:20 dpdklab
2024-02-06 12:19 dpdklab
2024-02-06 12:13 dpdklab
2024-02-06 12:12 dpdklab
2024-02-06 12:10 dpdklab
2024-02-06 12:09 dpdklab
2024-02-06 12:05 dpdklab
2024-02-06 12:03 dpdklab
2024-02-06 12:01 dpdklab
2024-02-06 11:59 dpdklab
2024-02-06 11:59 dpdklab
2024-02-06 11:57 dpdklab
2024-02-06 11:57 dpdklab
2024-02-06 11:57 dpdklab
2024-02-06 11:57 dpdklab
2024-02-06 11:50 dpdklab
2024-02-06 11:49 dpdklab
2024-02-06 11:49 dpdklab
2024-02-06 11:47 dpdklab
2024-02-06 11:46 dpdklab
2024-02-06 11:45 dpdklab
2024-02-06 11:45 dpdklab
2024-02-06 11:44 dpdklab
2024-02-06 11:43 dpdklab
2024-02-06 11:43 dpdklab
2024-02-06 11:42 dpdklab
2024-02-06 11:42 dpdklab
2024-02-06 11:39 dpdklab
2024-02-06 11:38 dpdklab
2024-02-06 11:36 dpdklab
2024-02-06 11:35 dpdklab
2024-02-06 11:35 dpdklab
2024-02-06 11:35 dpdklab
2024-02-06 11:34 dpdklab
2024-02-06 11:34 dpdklab
2024-02-06 11:33 dpdklab
2024-02-06 11:33 dpdklab
2024-02-06 11:32 dpdklab
2024-02-06 11:31 dpdklab
2024-02-06 11:31 dpdklab
2024-02-06 11:31 dpdklab
2024-02-06 11:30 dpdklab
2024-02-06 11:27 dpdklab
2024-02-06 11:27 dpdklab
2024-02-06 11:27 dpdklab
2024-02-06 11:26 dpdklab
2024-02-06 11:26 dpdklab
2024-02-06 11:25 dpdklab
2024-02-06 11:25 dpdklab
2024-02-06 11:25 dpdklab
2024-02-06 11:24 dpdklab
2024-02-06 11:24 dpdklab
2024-02-06 11:23 dpdklab
2024-02-06 11:23 dpdklab
2024-02-06 11:22 dpdklab
2024-02-06 11:22 dpdklab
2024-02-06 11:22 dpdklab
2024-02-06 11:21 dpdklab
2024-02-06 11:20 dpdklab
2024-02-06 11:20 dpdklab
2024-02-06 11:19 dpdklab
2024-02-06 11:19 dpdklab
2024-02-06 11:19 dpdklab
2024-02-06 11:18 dpdklab
2024-02-06 11:09 dpdklab
2024-02-06 11:00 dpdklab
2024-02-06 10:59 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=65c216be.050a0220.b348a.4ac2SMTPIN_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).