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| pw129157 [PATCH] [v2] net/idpf: fix error path processing
Date: Fri, 30 Jun 2023 20:20:36 -0700 (PDT)	[thread overview]
Message-ID: <649f9b84.810a0220.a1137.63f0SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-x86_64-compile-testing
Test-Status: SUCCESS
http://dpdk.org/patch/129157

_Testing PASS_

Submitter: Liu, Mingxia <mingxia.liu@intel.com>
Date: Friday, June 30 2023 18:54:02 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:93a4b3beba4ee611685148917981f846427cafb2

129157 --> testing pass

Test environment and result as below:

+---------------------+--------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Ubuntu 22.04        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| FreeBSD 13          | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Debian Buster       | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 37           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS Stream 9     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS Stream 8     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| RHEL8               | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 38           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Alpine              | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| RHEL 7              | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Debian Bullseye     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS               | PASS                 |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15    | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+


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

FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

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

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

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

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)

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

Alpine
	Kernel: 5.4.0-73-generic
	Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424

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 Bullseye
	Kernel: 5.4.0-122-generic
	Compiler: gcc 10.2.1-6

Windows Server 2019
	Kernel: 10.0
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-07-01  3:20 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-01  3:20 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-02 13:44 dpdklab
2023-07-01  8:44 dpdklab
2023-07-01  8:43 dpdklab
2023-07-01  8:42 dpdklab
2023-07-01  7:56 dpdklab
2023-07-01  7:24 dpdklab
2023-07-01  3:31 dpdklab
2023-07-01  3:19 dpdklab
2023-07-01  0:14 dpdklab
2023-07-01  0:13 dpdklab
2023-07-01  0:10 dpdklab
2023-07-01  0:06 dpdklab
2023-07-01  0:06 dpdklab
2023-07-01  0:05 dpdklab
2023-06-30 23:56 dpdklab
2023-06-30 23:56 dpdklab
2023-06-30 23:56 dpdklab
2023-06-30 23:56 dpdklab
2023-06-30 23:51 dpdklab
2023-06-30 23:45 dpdklab
2023-06-30 23:39 dpdklab
2023-06-30 23:38 dpdklab
2023-06-30 22:54 dpdklab
2023-06-30 22:44 dpdklab
2023-06-30 22:44 dpdklab
2023-06-30 22:44 dpdklab
2023-06-30 22:44 dpdklab
2023-06-30 22:43 dpdklab
2023-06-30 22:35 dpdklab
2023-06-30 22:35 dpdklab
     [not found] <20230630185402.13307-1-mingxia.liu@intel.com>
2023-06-30 10:31 ` |SUCCESS| pw129157 [PATCH v2] " qemudev
2023-06-30 10:35 ` qemudev
2023-06-30 10:36 ` checkpatch
2023-06-30 11:39 ` 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=649f9b84.810a0220.a1137.63f0SMTPIN_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).