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| pw135902 [PATCH] maintainers: updated for Intel drivers
Date: Wed, 17 Jan 2024 19:55:33 -0800 (PST)	[thread overview]
Message-ID: <65a8a135.920a0220.53529.59d8SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Qiming Yang <qiming.yang@intel.com>
Date: Wednesday, January 17 2024 10:17:49 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:d4af9a82063e4c39568191eaa12955d3ca39581a

135902 --> testing pass

Test environment and result as below:

+------------------+----------+
|   Environment    | abi_test |
+==================+==========+
| Debian Buster    | PASS     |
+------------------+----------+
| CentOS Stream 8  | PASS     |
+------------------+----------+
| openSUSE Leap 15 | PASS     |
+------------------+----------+
| Ubuntu 22.04     | PASS     |
+------------------+----------+
| Fedora 38        | PASS     |
+------------------+----------+


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

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

Ubuntu 22.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.0

Fedora 38
	Kernel: Depends on container host
	Compiler: clang 16.0.3

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-18  3:55 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18  3:55 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-18 13:13 dpdklab
2024-01-18  6:43 dpdklab
2024-01-18  6:00 dpdklab
2024-01-18  5:49 dpdklab
2024-01-18  5:15 dpdklab
2024-01-18  5:14 dpdklab
2024-01-18  5:06 dpdklab
2024-01-18  4:59 dpdklab
2024-01-18  4:55 dpdklab
2024-01-18  4:55 dpdklab
2024-01-18  4:54 dpdklab
2024-01-18  4:54 dpdklab
2024-01-18  4:53 dpdklab
2024-01-18  4:48 dpdklab
2024-01-18  4:48 dpdklab
2024-01-18  4:45 dpdklab
2024-01-18  4:45 dpdklab
2024-01-18  4:44 dpdklab
2024-01-18  4:44 dpdklab
2024-01-18  4:44 dpdklab
2024-01-18  4:43 dpdklab
2024-01-18  4:42 dpdklab
2024-01-18  4:42 dpdklab
2024-01-18  4:42 dpdklab
2024-01-18  4:40 dpdklab
2024-01-18  4:40 dpdklab
2024-01-18  4:39 dpdklab
2024-01-18  4:39 dpdklab
2024-01-18  4:37 dpdklab
2024-01-18  4:37 dpdklab
2024-01-18  4:36 dpdklab
2024-01-18  4:36 dpdklab
2024-01-18  4:36 dpdklab
2024-01-18  4:36 dpdklab
2024-01-18  4:36 dpdklab
2024-01-18  4:35 dpdklab
2024-01-18  4:35 dpdklab
2024-01-18  4:31 dpdklab
2024-01-18  4:29 dpdklab
2024-01-18  4:28 dpdklab
2024-01-18  4:26 dpdklab
2024-01-18  4:26 dpdklab
2024-01-18  4:24 dpdklab
2024-01-18  4:24 dpdklab
2024-01-18  4:24 dpdklab
2024-01-18  4:16 dpdklab
2024-01-18  4:15 dpdklab
2024-01-18  4:15 dpdklab
2024-01-18  4:14 dpdklab
2024-01-18  3:55 dpdklab
2024-01-18  3:53 dpdklab
2024-01-18  3:52 dpdklab
2024-01-18  3:51 dpdklab
2024-01-18  3:48 dpdklab
2024-01-18  3:46 dpdklab
2024-01-18  3:45 dpdklab
2024-01-18  3:43 dpdklab
2024-01-18  3:42 dpdklab
2024-01-18  3:38 dpdklab
2024-01-18  3:34 dpdklab
2024-01-18  3:25 dpdklab
2024-01-18  3:18 dpdklab
2024-01-18  3:15 dpdklab
2024-01-18  3:14 dpdklab
2024-01-18  3:07 dpdklab
2024-01-18  3:06 dpdklab
2024-01-18  3:05 dpdklab
2024-01-18  3:04 dpdklab
2024-01-18  3:03 dpdklab
     [not found] <20240117101749.257581-1-qiming.yang@intel.com>
2024-01-17  2:03 ` qemudev
2024-01-17  2:07 ` qemudev
2024-01-17  2:23 ` checkpatch
2024-01-17  3:15 ` 0-day Robot

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=65a8a135.920a0220.53529.59d8SMTPIN_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).