automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Dariusz Sosnowski <dsosnowski@nvidia.com>
Subject: |SUCCESS| pw137456 [PATCH] app/testpmd: fix async flow create failur
Date: Wed, 28 Feb 2024 18:31:07 -0800 (PST)	[thread overview]
Message-ID: <65dfec6b.170a0220.5741d.04dbSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240228185707.186522-1-dsosnowski@nvidia.com>

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

_Testing PASS_

Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Wednesday, February 28 2024 18:57:07 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:f60df26faa3c90fc66d356e16347acd046971441

137456 --> testing pass

Test environment and result as below:

+-----------------+----------+
|   Environment   | abi_test |
+=================+==========+
| CentOS Stream 9 | PASS     |
+-----------------+----------+
| Fedora 37       | PASS     |
+-----------------+----------+
| Fedora 38       | PASS     |
+-----------------+----------+
| CentOS Stream 8 | PASS     |
+-----------------+----------+
| Debian Bullseye | PASS     |
+-----------------+----------+


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

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

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

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

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-02-29  2:31 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240228185707.186522-1-dsosnowski@nvidia.com>
2024-02-28 18:35 ` |SUCCESS| pw137456 [PATCH] app/testpmd: fix async flow create failure handling qemudev
2024-02-28 18:39 ` qemudev
2024-02-28 18:57 ` checkpatch
2024-02-28 19:45 ` 0-day Robot
2024-02-29  2:01 ` |SUCCESS| pw137456 [PATCH] app/testpmd: fix async flow create failur dpdklab
2024-02-29  2:02 ` dpdklab
2024-02-29  2:12 ` dpdklab
2024-02-29  2:12 ` dpdklab
2024-02-29  2:15 ` dpdklab
2024-02-29  2:19 ` dpdklab
2024-02-29  2:20 ` dpdklab
2024-02-29  2:21 ` dpdklab
2024-02-29  2:21 ` dpdklab
2024-02-29  2:21 ` dpdklab
2024-02-29  2:22 ` dpdklab
2024-02-29  2:22 ` dpdklab
2024-02-29  2:22 ` dpdklab
2024-02-29  2:23 ` dpdklab
2024-02-29  2:23 ` dpdklab
2024-02-29  2:23 ` dpdklab
2024-02-29  2:23 ` dpdklab
2024-02-29  2:24 ` dpdklab
2024-02-29  2:25 ` dpdklab
2024-02-29  2:25 ` dpdklab
2024-02-29  2:25 ` dpdklab
2024-02-29  2:26 ` dpdklab
2024-02-29  2:26 ` dpdklab
2024-02-29  2:26 ` dpdklab
2024-02-29  2:27 ` dpdklab
2024-02-29  2:27 ` dpdklab
2024-02-29  2:27 ` dpdklab
2024-02-29  2:27 ` dpdklab
2024-02-29  2:27 ` dpdklab
2024-02-29  2:29 ` dpdklab
2024-02-29  2:29 ` dpdklab
2024-02-29  2:29 ` dpdklab
2024-02-29  2:31 ` dpdklab [this message]
2024-02-29  2:31 ` dpdklab
2024-02-29  2:31 ` dpdklab
2024-02-29  2:32 ` dpdklab
2024-02-29  2:32 ` dpdklab
2024-02-29  2:33 ` dpdklab
2024-02-29  2:34 ` dpdklab
2024-02-29  2:36 ` dpdklab
2024-02-29  2:36 ` dpdklab
2024-02-29  2:38 ` dpdklab
2024-02-29  2:38 ` dpdklab
2024-02-29  2:38 ` dpdklab
2024-02-29  2:39 ` dpdklab
2024-02-29  2:41 ` dpdklab
2024-02-29  2:42 ` dpdklab
2024-02-29  2:48 ` dpdklab
2024-02-29  2:48 ` dpdklab
2024-02-29  2:49 ` dpdklab
2024-02-29  2:49 ` dpdklab
2024-02-29  2:49 ` dpdklab
2024-02-29  2:49 ` dpdklab
2024-02-29  2:50 ` dpdklab
2024-02-29  2:55 ` dpdklab
2024-02-29  3:01 ` dpdklab
2024-02-29  3:01 ` dpdklab
2024-02-29  3:02 ` dpdklab
2024-02-29  3:03 ` dpdklab
2024-02-29  3:14 ` dpdklab
2024-02-29  3:20 ` dpdklab
2024-02-29  5:18 ` dpdklab
2024-03-01  2:14 ` |FAILURE| " dpdklab
2024-03-01  2:15 ` |SUCCESS| " dpdklab
2024-03-01  2:18 ` dpdklab
2024-03-01  2:20 ` dpdklab
2024-03-01 18:55 ` dpdklab
2024-03-02 10:13 ` |FAILURE| " dpdklab
2024-03-02 10:45 ` |SUCCESS| " dpdklab
2024-03-02 11:18 ` dpdklab
2024-03-06  3:57 ` |FAILURE| " 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=65dfec6b.170a0220.5741d.04dbSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dsosnowski@nvidia.com \
    --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).