From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135810-135816 [PATCH] [v7,7/7] dts: add pmd_buffer_scatt
Date: Tue, 09 Jan 2024 08:38:34 -0800 (PST) [thread overview]
Message-ID: <659d768a.170a0220.bd806.25beSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135816
_Testing PASS_
Submitter: Jeremy Spewock <jspewock@iol.unh.edu>
Date: Tuesday, January 09 2024 15:36:33
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6ef07151aac4b4d9601d547f94a996d1c71b3871
135810-135816 --> testing pass
Test environment and result as below:
+-----------------+----------+
| Environment | abi_test |
+=================+==========+
| CentOS Stream 9 | PASS |
+-----------------+----------+
| Debian Bullseye | PASS |
+-----------------+----------+
| Fedora 37 | PASS |
+-----------------+----------+
| Fedora 38 | PASS |
+-----------------+----------+
| Debian Buster | PASS |
+-----------------+----------+
| CentOS Stream 8 | PASS |
+-----------------+----------+
| RHEL8 | PASS |
+-----------------+----------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
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
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28836/
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:38 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 16:38 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-09 17:43 dpdklab
2024-01-09 17:23 dpdklab
2024-01-09 17:06 dpdklab
2024-01-09 17:05 dpdklab
2024-01-09 17:02 dpdklab
2024-01-09 17:01 dpdklab
2024-01-09 16:57 dpdklab
2024-01-09 16:56 dpdklab
2024-01-09 16:55 dpdklab
2024-01-09 16:55 dpdklab
2024-01-09 16:55 dpdklab
2024-01-09 16:54 dpdklab
2024-01-09 16:49 dpdklab
2024-01-09 16:44 dpdklab
2024-01-09 16:43 dpdklab
2024-01-09 16:43 dpdklab
2024-01-09 16:43 dpdklab
2024-01-09 16:42 dpdklab
2024-01-09 16:40 dpdklab
2024-01-09 16:40 dpdklab
2024-01-09 16:40 dpdklab
2024-01-09 16:40 dpdklab
2024-01-09 16:39 dpdklab
2024-01-09 16:38 dpdklab
2024-01-09 16:38 dpdklab
2024-01-09 16:37 dpdklab
2024-01-09 16:37 dpdklab
2024-01-09 16:37 dpdklab
2024-01-09 16:37 dpdklab
2024-01-09 16:36 dpdklab
2024-01-09 16:36 dpdklab
2024-01-09 16:36 dpdklab
2024-01-09 16:36 dpdklab
2024-01-09 16:35 dpdklab
2024-01-09 16:35 dpdklab
2024-01-09 16:32 dpdklab
2024-01-09 16:31 dpdklab
2024-01-09 16:31 dpdklab
2024-01-09 16:31 dpdklab
2024-01-09 16:31 dpdklab
2024-01-09 16:31 dpdklab
2024-01-09 16:30 dpdklab
2024-01-09 16:30 dpdklab
2024-01-09 16:30 dpdklab
2024-01-09 16:29 dpdklab
2024-01-09 16:29 dpdklab
2024-01-09 16:29 dpdklab
2024-01-09 16:28 dpdklab
2024-01-09 16:28 dpdklab
2024-01-09 16:27 dpdklab
2024-01-09 16:27 dpdklab
2024-01-09 16:27 dpdklab
2024-01-09 16:26 dpdklab
2024-01-09 16:26 dpdklab
2024-01-09 16:26 dpdklab
2024-01-09 16:25 dpdklab
2024-01-09 16:25 dpdklab
2024-01-09 16:24 dpdklab
2024-01-09 16:18 dpdklab
2024-01-09 16:18 dpdklab
2024-01-09 16:18 dpdklab
2024-01-09 16:18 dpdklab
2024-01-09 16:18 dpdklab
2024-01-09 16:16 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=659d768a.170a0220.bd806.25beSMTPIN_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).