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| pw138768 [PATCH] graph: avoid id collisions
Date: Mon, 25 Mar 2024 10:30:12 -0700 (PDT)	[thread overview]
Message-ID: <6601b4a4.170a0220.1ccbf.8355SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240325155354.770676-2-rjarry@redhat.com>

Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138768

_Testing PASS_

Submitter: Robin Jarry <rjarry@redhat.com>
Date: Monday, March 25 2024 15:53:55 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:0b82b5139fefe6eb5ec1a0b489fd193e8a99ab73

138768 --> testing pass

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| Windows Server 2022 | PASS           |
+---------------------+----------------+
| Debian 11 (arm)     | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| Fedora 37           | PASS           |
+---------------------+----------------+
| Ubuntu 20.04        | PASS           |
+---------------------+----------------+
| RHEL8               | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+
| Ubuntu 22.04        | PASS           |
+---------------------+----------------+
| openSUSE Leap 15    | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+


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

Debian Bullseye
	Kernel: 5.4.0-167-generic
	Compiler: gcc 10.2.1-6

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9

Debian 11 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

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

Ubuntu 20.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

RHEL8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)

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

Ubuntu 22.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.0

openSUSE Leap 15
	Kernel: 5.4.0-167-generic
	Compiler: gcc 7.5.0

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-25 17:30 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240325155354.770676-2-rjarry@redhat.com>
2024-03-25 15:31 ` qemudev
2024-03-25 15:35 ` qemudev
2024-03-25 15:55 ` checkpatch
2024-03-25 16:34 ` dpdklab
2024-03-25 16:35 ` dpdklab
2024-03-25 16:35 ` dpdklab
2024-03-25 16:35 ` dpdklab
2024-03-25 16:35 ` dpdklab
2024-03-25 16:35 ` dpdklab
2024-03-25 16:36 ` dpdklab
2024-03-25 16:36 ` dpdklab
2024-03-25 16:36 ` dpdklab
2024-03-25 16:36 ` dpdklab
2024-03-25 16:36 ` dpdklab
2024-03-25 16:36 ` dpdklab
2024-03-25 16:37 ` dpdklab
2024-03-25 16:37 ` dpdklab
2024-03-25 16:37 ` dpdklab
2024-03-25 16:37 ` dpdklab
2024-03-25 16:37 ` dpdklab
2024-03-25 16:37 ` dpdklab
2024-03-25 16:38 ` dpdklab
2024-03-25 16:38 ` dpdklab
2024-03-25 16:38 ` dpdklab
2024-03-25 16:38 ` dpdklab
2024-03-25 16:44 ` dpdklab
2024-03-25 16:44 ` 0-day Robot
2024-03-25 16:47 ` dpdklab
2024-03-25 16:47 ` dpdklab
2024-03-25 16:47 ` dpdklab
2024-03-25 16:49 ` dpdklab
2024-03-25 16:50 ` dpdklab
2024-03-25 16:50 ` dpdklab
2024-03-25 16:50 ` dpdklab
2024-03-25 16:51 ` dpdklab
2024-03-25 16:51 ` dpdklab
2024-03-25 16:52 ` dpdklab
2024-03-25 16:52 ` dpdklab
2024-03-25 16:53 ` dpdklab
2024-03-25 17:06 ` dpdklab
2024-03-25 17:12 ` dpdklab
2024-03-25 17:12 ` dpdklab
2024-03-25 17:12 ` dpdklab
2024-03-25 17:13 ` dpdklab
2024-03-25 17:13 ` dpdklab
2024-03-25 17:13 ` dpdklab
2024-03-25 17:13 ` dpdklab
2024-03-25 17:14 ` dpdklab
2024-03-25 17:14 ` dpdklab
2024-03-25 17:19 ` dpdklab
2024-03-25 17:19 ` dpdklab
2024-03-25 17:19 ` dpdklab
2024-03-25 17:20 ` dpdklab
2024-03-25 17:20 ` dpdklab
2024-03-25 17:21 ` dpdklab
2024-03-25 17:22 ` dpdklab
2024-03-25 17:22 ` dpdklab
2024-03-25 17:23 ` dpdklab
2024-03-25 17:23 ` dpdklab
2024-03-25 17:23 ` dpdklab
2024-03-25 17:23 ` dpdklab
2024-03-25 17:23 ` dpdklab
2024-03-25 17:24 ` dpdklab
2024-03-25 17:25 ` dpdklab
2024-03-25 17:29 ` dpdklab
2024-03-25 17:30 ` dpdklab [this message]
2024-03-25 17:30 ` dpdklab
2024-03-25 17:30 ` dpdklab
2024-03-25 17:31 ` dpdklab
2024-03-25 17:32 ` dpdklab
2024-03-25 17:49 ` dpdklab
2024-03-25 18:04 ` dpdklab
2024-03-25 18:05 ` dpdklab
2024-03-25 18:08 ` dpdklab
2024-03-25 18:12 ` dpdklab
2024-04-01 14:30 ` dpdklab
2024-04-01 14:34 ` dpdklab
2024-04-01 14:38 ` dpdklab
2024-04-01 14:42 ` dpdklab
2024-04-01 15:01 ` 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=6601b4a4.170a0220.1ccbf.8355SMTPIN_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).