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| pw140553 [PATCH] app/testpmd: support retrying device stop
Date: Sun, 02 Jun 2024 07:45:34 -0700 (PDT)	[thread overview]
Message-ID: <665c858e.170a0220.126510.8a91SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240602103035.197205-1-mkashani@nvidia.com>

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

_Testing PASS_

Submitter: Maayan Kashani <mkashani@nvidia.com>
Date: Sunday, June 02 2024 10:30:35 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2dbb63594a9a985e2c8639b57f9fcd1468b9de97

140553 --> testing pass

Test environment and result as below:

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


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

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

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

Fedora 39
	Kernel: Depends on container host
	Compiler: clang 17.0.6

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

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

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-02 14:45 UTC|newest]

Thread overview: 93+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240602103035.197205-1-mkashani@nvidia.com>
2024-06-02 10:03 ` qemudev
2024-06-02 10:08 ` qemudev
2024-06-02 10:32 ` checkpatch
2024-06-02 11:23 ` 0-day Robot
2024-06-02 14:34 ` dpdklab
2024-06-02 14:34 ` dpdklab
2024-06-02 14:34 ` dpdklab
2024-06-02 14:35 ` dpdklab
2024-06-02 14:35 ` dpdklab
2024-06-02 14:36 ` dpdklab
2024-06-02 14:36 ` dpdklab
2024-06-02 14:37 ` dpdklab
2024-06-02 14:37 ` |FAILURE| " dpdklab
2024-06-02 14:37 ` |SUCCESS| " dpdklab
2024-06-02 14:37 ` |FAILURE| " dpdklab
2024-06-02 14:38 ` |SUCCESS| " dpdklab
2024-06-02 14:38 ` dpdklab
2024-06-02 14:38 ` dpdklab
2024-06-02 14:38 ` dpdklab
2024-06-02 14:39 ` dpdklab
2024-06-02 14:39 ` dpdklab
2024-06-02 14:40 ` dpdklab
2024-06-02 14:40 ` |FAILURE| " dpdklab
2024-06-02 14:40 ` |SUCCESS| " dpdklab
2024-06-02 14:40 ` dpdklab
2024-06-02 14:41 ` |FAILURE| " dpdklab
2024-06-02 14:41 ` |SUCCESS| " dpdklab
2024-06-02 14:41 ` |FAILURE| " dpdklab
2024-06-02 14:41 ` dpdklab
2024-06-02 14:42 ` |SUCCESS| " dpdklab
2024-06-02 14:42 ` dpdklab
2024-06-02 14:42 ` dpdklab
2024-06-02 14:43 ` dpdklab
2024-06-02 14:43 ` dpdklab
2024-06-02 14:43 ` dpdklab
2024-06-02 14:44 ` dpdklab
2024-06-02 14:44 ` dpdklab
2024-06-02 14:45 ` |FAILURE| " dpdklab
2024-06-02 14:45 ` |SUCCESS| " dpdklab
2024-06-02 14:45 ` dpdklab [this message]
2024-06-02 14:47 ` dpdklab
2024-06-02 14:48 ` |FAILURE| " dpdklab
2024-06-02 14:50 ` |SUCCESS| " dpdklab
2024-06-02 14:50 ` dpdklab
2024-06-02 14:51 ` dpdklab
2024-06-02 14:52 ` |FAILURE| " dpdklab
2024-06-02 14:52 ` dpdklab
2024-06-02 14:55 ` dpdklab
2024-06-02 14:55 ` dpdklab
2024-06-02 14:56 ` dpdklab
2024-06-02 14:58 ` dpdklab
2024-06-02 14:58 ` |SUCCESS| " dpdklab
2024-06-02 15:00 ` dpdklab
2024-06-02 15:00 ` |FAILURE| " dpdklab
2024-06-02 15:00 ` |SUCCESS| " dpdklab
2024-06-02 15:01 ` |FAILURE| " dpdklab
2024-06-02 15:03 ` dpdklab
2024-06-02 15:03 ` dpdklab
2024-06-02 15:04 ` dpdklab
2024-06-02 15:04 ` |SUCCESS| " dpdklab
2024-06-02 15:06 ` dpdklab
2024-06-02 15:07 ` dpdklab
2024-06-02 15:09 ` dpdklab
2024-06-02 15:11 ` dpdklab
2024-06-02 15:12 ` |FAILURE| " dpdklab
2024-06-02 15:12 ` |SUCCESS| " dpdklab
2024-06-02 15:13 ` |FAILURE| " dpdklab
2024-06-02 15:14 ` |SUCCESS| " dpdklab
2024-06-02 15:18 ` dpdklab
2024-06-02 15:18 ` dpdklab
2024-06-02 15:19 ` |FAILURE| " dpdklab
2024-06-02 15:20 ` |SUCCESS| " dpdklab
2024-06-02 15:20 ` dpdklab
2024-06-02 15:22 ` dpdklab
2024-06-02 15:24 ` dpdklab
2024-06-02 15:25 ` dpdklab
2024-06-02 15:26 ` |FAILURE| " dpdklab
2024-06-02 15:27 ` |SUCCESS| " dpdklab
2024-06-02 15:28 ` |FAILURE| " dpdklab
2024-06-02 15:30 ` |SUCCESS| " dpdklab
2024-06-02 15:30 ` |FAILURE| " dpdklab
2024-06-02 15:31 ` dpdklab
2024-06-02 15:34 ` |SUCCESS| " dpdklab
2024-06-02 15:37 ` dpdklab
2024-06-02 15:40 ` dpdklab
2024-06-02 15:47 ` dpdklab
2024-06-02 15:52 ` |FAILURE| " dpdklab
2024-06-02 15:54 ` |SUCCESS| " dpdklab
2024-06-02 16:01 ` dpdklab
2024-06-02 16:03 ` |FAILURE| " dpdklab
2024-06-02 16:03 ` dpdklab
2024-06-02 16:07 ` dpdklab
2024-06-02 16:31 ` 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=665c858e.170a0220.126510.8a91SMTPIN_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).