automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135823-135829 [PATCH] [v8,7/7] dts: add pmd_buffer_scatt
Date: Wed, 10 Jan 2024 07:34:14 -0800 (PST)	[thread overview]
Message-ID: <659eb8f6.9f0a0220.d992.98f2SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135829

_Testing PASS_

Submitter: Jeremy Spewock <jspewock@iol.unh.edu>
Date: Wednesday, January 10 2024 14:42:49 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:6ef07151aac4b4d9601d547f94a996d1c71b3871

135823-135829 --> testing pass

Test environment and result as below:

+-----------------+----------+
|   Environment   | abi_test |
+=================+==========+
| CentOS Stream 8 | PASS     |
+-----------------+----------+
| Fedora 37       | PASS     |
+-----------------+----------+
| Fedora 38       | PASS     |
+-----------------+----------+


CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

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

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28841/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2024-01-10 15:34 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10 15:34 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-10 18:20 dpdklab
2024-01-10 16:22 dpdklab
2024-01-10 16:15 dpdklab
2024-01-10 16:04 dpdklab
2024-01-10 16:01 dpdklab
2024-01-10 15:57 dpdklab
2024-01-10 15:57 dpdklab
2024-01-10 15:56 dpdklab
2024-01-10 15:55 dpdklab
2024-01-10 15:55 dpdklab
2024-01-10 15:54 dpdklab
2024-01-10 15:52 dpdklab
2024-01-10 15:51 dpdklab
2024-01-10 15:50 dpdklab
2024-01-10 15:50 dpdklab
2024-01-10 15:48 dpdklab
2024-01-10 15:47 dpdklab
2024-01-10 15:47 dpdklab
2024-01-10 15:45 dpdklab
2024-01-10 15:43 dpdklab
2024-01-10 15:43 dpdklab
2024-01-10 15:41 dpdklab
2024-01-10 15:40 dpdklab
2024-01-10 15:38 dpdklab
2024-01-10 15:37 dpdklab
2024-01-10 15:36 dpdklab
2024-01-10 15:34 dpdklab
2024-01-10 15:34 dpdklab
2024-01-10 15:33 dpdklab
2024-01-10 15:33 dpdklab
2024-01-10 15:33 dpdklab
2024-01-10 15:33 dpdklab
2024-01-10 15:33 dpdklab
2024-01-10 15:32 dpdklab
2024-01-10 15:32 dpdklab
2024-01-10 15:32 dpdklab
2024-01-10 15:32 dpdklab
2024-01-10 15:32 dpdklab
2024-01-10 15:32 dpdklab
2024-01-10 15:31 dpdklab
2024-01-10 15:31 dpdklab
2024-01-10 15:31 dpdklab
2024-01-10 15:31 dpdklab
2024-01-10 15:31 dpdklab
2024-01-10 15:30 dpdklab
2024-01-10 15:30 dpdklab
2024-01-10 15:30 dpdklab
2024-01-10 15:29 dpdklab
2024-01-10 15:29 dpdklab
2024-01-10 15:29 dpdklab
2024-01-10 15:29 dpdklab
2024-01-10 15:29 dpdklab
2024-01-10 15:28 dpdklab
2024-01-10 15:28 dpdklab
2024-01-10 15:28 dpdklab
2024-01-10 15:27 dpdklab
2024-01-10 15:27 dpdklab
2024-01-10 15:27 dpdklab
2024-01-10 15:26 dpdklab
2024-01-10 15:26 dpdklab
2024-01-10 15:25 dpdklab
2024-01-10 15:25 dpdklab
2024-01-10 15:25 dpdklab
2024-01-10 15:24 dpdklab
2024-01-10 15:23 dpdklab
2024-01-10 15:23 dpdklab
2024-01-10 15:22 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=659eb8f6.9f0a0220.d992.98f2SMTPIN_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).