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| pw126916 [PATCH] [v4] doc: update ixgbe VF features list
Date: Wed, 17 May 2023 09:07:28 -0700 (PDT)	[thread overview]
Message-ID: <6464fbc0.050a0220.1bd25.f662SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Wednesday, May 17 2023 10:03:37 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a399d7b5a994e335c446d4b15d7622d71dd8848c

126916 --> testing pass

Test environment and result as below:

+------------------+----------+
|   Environment    | abi_test |
+==================+==========+
| openSUSE Leap 15 | PASS     |
+------------------+----------+
| Ubuntu 22.04     | PASS     |
+------------------+----------+
| CentOS Stream 8  | PASS     |
+------------------+----------+
| CentOS Stream 9  | PASS     |
+------------------+----------+
| Debian Bullseye  | PASS     |
+------------------+----------+
| RHEL 7           | PASS     |
+------------------+----------+
| Debian Buster    | PASS     |
+------------------+----------+
| RHEL8            | PASS     |
+------------------+----------+


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

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

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

RHEL 7
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)

Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

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/26255/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-05-17 16:07 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17 16:07 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-17 20:45 dpdklab
2023-05-17 20:44 dpdklab
2023-05-17 20:06 dpdklab
2023-05-17 18:20 dpdklab
2023-05-17 16:04 dpdklab
2023-05-17 15:55 dpdklab
2023-05-17 15:45 dpdklab
2023-05-17 15:44 dpdklab
2023-05-17 15:44 dpdklab
2023-05-17 15:43 dpdklab
2023-05-17 15:41 dpdklab
2023-05-17 15:35 dpdklab
2023-05-17 15:25 dpdklab
2023-05-17 15:20 dpdklab
2023-05-17 15:17 dpdklab
2023-05-17 15:17 dpdklab
2023-05-17 14:43 dpdklab
2023-05-17 14:38 dpdklab
2023-05-17 14:36 dpdklab
2023-05-17 14:29 dpdklab
2023-05-17 14:24 dpdklab
2023-05-17 14:23 dpdklab
2023-05-17 14:18 dpdklab
2023-05-17 14:17 dpdklab
2023-05-17 14:16 dpdklab
2023-05-17 14:15 dpdklab
2023-05-17 14:14 dpdklab
2023-05-17 14:10 dpdklab
     [not found] <20230517100337.552579-1-mingjinx.ye@intel.com>
2023-05-17 10:00 ` |SUCCESS| pw126916 [PATCH v4] " qemudev
2023-05-17 10:04 ` qemudev
2023-05-17 10:12 ` checkpatch
2023-05-17 14:00 ` 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=6464fbc0.050a0220.1bd25.f662SMTPIN_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).