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| pw127155 [PATCH] net/ice: fix data length check
Date: Mon, 22 May 2023 03:58:17 -0700 (PDT)	[thread overview]
Message-ID: <646b4ac9.250a0220.55dea.267eSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Qi Zhang <qi.z.zhang@intel.com>
Date: Monday, May 22 2023 18:14:47 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a399d7b5a994e335c446d4b15d7622d71dd8848c

127155 --> testing pass

Test environment and result as below:

+-----------------+----------+
|   Environment   | abi_test |
+=================+==========+
| RHEL8           | PASS     |
+-----------------+----------+
| CentOS Stream 9 | PASS     |
+-----------------+----------+
| Debian Buster   | PASS     |
+-----------------+----------+
| CentOS Stream 8 | PASS     |
+-----------------+----------+


RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-05-22 10:58 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22 10:58 dpdklab [this message]
     [not found] <20230522181447.2747713-1-qi.z.zhang@intel.com>
2023-05-22  9:56 ` checkpatch
2023-05-23 11:24 ` qemudev
2023-05-23 11:24 ` qemudev
  -- strict thread matches above, loose matches on Subject: below --
2023-05-22 11:21 dpdklab
2023-05-22 11:15 dpdklab
2023-05-22 11:10 dpdklab
2023-05-22 11:10 dpdklab
2023-05-22 11:04 dpdklab
2023-05-22 11:04 dpdklab
2023-05-22 10:59 dpdklab
2023-05-22 10:57 dpdklab
2023-05-22 10:55 dpdklab
2023-05-22 10:52 dpdklab
2023-05-22 10:50 dpdklab
2023-05-22 10:46 dpdklab
2023-05-22 10:43 dpdklab
2023-05-22 10:38 dpdklab
2023-05-22 10:32 dpdklab
2023-05-22 10:32 dpdklab
2023-05-22 10:31 dpdklab
2023-05-22 10:31 dpdklab
2023-05-22 10:30 dpdklab
2023-05-22 10:30 dpdklab
2023-05-22 10:24 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=646b4ac9.250a0220.55dea.267eSMTPIN_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).