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: |PENDING| pw142009 [PATCH] baseband/la12xx: fix issue with secondary
Date: Tue, 02 Jul 2024 06:04:18 -0700 (PDT)	[thread overview]
Message-ID: <6683fad2.050a0220.e191a.4000SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240702060921.3660623-1-hemant.agrawal@nxp.com>

Test-Label: iol-unit-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/142009

_Testing pending_

Submitter: Hemant Agrawal <hemant.agrawal@nxp.com>
Date: Tuesday, July 02 2024 06:09:21 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e195680f6f1c109cd7812b1ef6f2a38cea70ea9b

142009 --> testing pending

Test environment and result as below:

+-------------------+----------------+
|    Environment    | dpdk_unit_test |
+===================+================+
| CentOS Stream 9   | PASS           |
+-------------------+----------------+
| CentOS Stream 8   | PASS           |
+-------------------+----------------+
| Debian 12         | PASS           |
+-------------------+----------------+
| Fedora 38         | PASS           |
+-------------------+----------------+
| Fedora 37         | PASS           |
+-------------------+----------------+
| Fedora 38 (Clang) | PASS           |
+-------------------+----------------+
| Fedora 39         | PEND           |
+-------------------+----------------+
| Fedora 39 (Clang) | PEND           |
+-------------------+----------------+
| Fedora 40         | PASS           |
+-------------------+----------------+
| Fedora 40 (Clang) | PEND           |
+-------------------+----------------+
| RHEL8             | PEND           |
+-------------------+----------------+
| openSUSE Leap 15  | PEND           |
+-------------------+----------------+
| RHEL9             | PEND           |
+-------------------+----------------+
| Ubuntu 20.04      | PEND           |
+-------------------+----------------+
| Ubuntu 22.04      | PEND           |
+-------------------+----------------+
| Ubuntu 24.04      | PEND           |
+-------------------+----------------+
| Debian Bullseye   | PEND           |
+-------------------+----------------+


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

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

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

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

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

Fedora 38 (Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.6

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

Fedora 39 (Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.1.1

Fedora 40 (Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.6

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

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

RHEL9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1

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

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

Ubuntu 24.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 13.2.0

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-07-02 13:04 UTC|newest]

Thread overview: 117+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240702060921.3660623-1-hemant.agrawal@nxp.com>
2024-07-02  5:43 ` |SUCCESS| pw142009 [PATCH] baseband/la12xx: fix issue with secondary process qemudev
2024-07-02  5:48 ` qemudev
2024-07-02  6:10 ` checkpatch
2024-07-02  7:05 ` 0-day Robot
2024-07-02  7:56 ` |PENDING| pw142009 [PATCH] baseband/la12xx: fix issue with secondary dpdklab
2024-07-02  8:02 ` dpdklab
2024-07-02  8:10 ` |SUCCESS| " dpdklab
2024-07-02  8:13 ` dpdklab
2024-07-02  8:16 ` dpdklab
2024-07-02  8:18 ` dpdklab
2024-07-02  8:21 ` dpdklab
2024-07-02  8:22 ` |PENDING| " dpdklab
2024-07-02  8:25 ` dpdklab
2024-07-02  8:27 ` dpdklab
2024-07-02  8:38 ` dpdklab
2024-07-02  8:42 ` dpdklab
2024-07-02  8:48 ` dpdklab
2024-07-02  8:48 ` dpdklab
2024-07-02  8:48 ` |SUCCESS| " dpdklab
2024-07-02  8:51 ` |PENDING| " dpdklab
2024-07-02  8:53 ` dpdklab
2024-07-02  8:56 ` dpdklab
2024-07-02  8:56 ` dpdklab
2024-07-02  8:58 ` dpdklab
2024-07-02  8:58 ` |SUCCESS| " dpdklab
2024-07-02  9:10 ` |PENDING| " dpdklab
2024-07-02  9:19 ` dpdklab
2024-07-02  9:23 ` |SUCCESS| " dpdklab
2024-07-02  9:28 ` dpdklab
2024-07-02  9:29 ` dpdklab
2024-07-02  9:48 ` dpdklab
2024-07-02  9:53 ` dpdklab
2024-07-02 10:00 ` dpdklab
2024-07-02 11:23 ` |PENDING| " dpdklab
2024-07-02 11:23 ` dpdklab
2024-07-02 11:24 ` dpdklab
2024-07-02 11:27 ` dpdklab
2024-07-02 11:28 ` dpdklab
2024-07-02 11:29 ` |SUCCESS| " dpdklab
2024-07-02 11:30 ` dpdklab
2024-07-02 11:57 ` |PENDING| " dpdklab
2024-07-02 12:43 ` dpdklab
2024-07-02 12:44 ` dpdklab
2024-07-02 12:47 ` dpdklab
2024-07-02 12:49 ` dpdklab
2024-07-02 12:55 ` dpdklab
2024-07-02 13:00 ` dpdklab
2024-07-02 13:04 ` dpdklab [this message]
2024-07-02 13:05 ` dpdklab
2024-07-02 13:11 ` dpdklab
2024-07-02 13:12 ` dpdklab
2024-07-02 13:17 ` dpdklab
2024-07-02 13:17 ` dpdklab
2024-07-02 13:18 ` dpdklab
2024-07-02 13:21 ` dpdklab
2024-07-02 13:23 ` dpdklab
2024-07-02 13:24 ` dpdklab
2024-07-02 13:33 ` |SUCCESS| " dpdklab
2024-07-02 14:17 ` dpdklab
2024-07-02 14:56 ` |PENDING| " dpdklab
2024-07-02 15:04 ` dpdklab
2024-07-02 15:05 ` dpdklab
2024-07-02 15:07 ` dpdklab
2024-07-02 15:08 ` dpdklab
2024-07-02 15:13 ` dpdklab
2024-07-02 15:14 ` dpdklab
2024-07-02 15:16 ` dpdklab
2024-07-02 15:16 ` dpdklab
2024-07-02 15:19 ` dpdklab
2024-07-02 15:20 ` dpdklab
2024-07-02 15:22 ` dpdklab
2024-07-02 15:24 ` dpdklab
2024-07-02 15:24 ` dpdklab
2024-07-02 15:27 ` dpdklab
2024-07-02 15:28 ` dpdklab
2024-07-02 15:28 ` dpdklab
2024-07-02 15:28 ` dpdklab
2024-07-02 15:30 ` dpdklab
2024-07-02 15:30 ` dpdklab
2024-07-02 15:30 ` dpdklab
2024-07-02 15:34 ` dpdklab
2024-07-02 15:38 ` dpdklab
2024-07-02 15:42 ` dpdklab
2024-07-02 15:47 ` dpdklab
2024-07-02 15:49 ` dpdklab
2024-07-02 15:50 ` dpdklab
2024-07-02 15:54 ` |SUCCESS| " dpdklab
2024-07-02 15:54 ` dpdklab
2024-07-02 15:54 ` dpdklab
2024-07-02 15:59 ` |PENDING| " dpdklab
2024-07-02 16:01 ` dpdklab
2024-07-02 16:05 ` dpdklab
2024-07-02 16:09 ` dpdklab
2024-07-02 16:16 ` dpdklab
2024-07-02 16:18 ` dpdklab
2024-07-02 16:23 ` dpdklab
2024-07-02 16:25 ` dpdklab
2024-07-02 16:31 ` dpdklab
2024-07-02 16:39 ` |SUCCESS| " dpdklab
2024-07-02 16:39 ` |PENDING| " dpdklab
2024-07-02 16:41 ` dpdklab
2024-07-02 16:52 ` dpdklab
2024-07-02 16:56 ` dpdklab
2024-07-02 16:58 ` dpdklab
2024-07-02 17:06 ` dpdklab
2024-07-02 17:09 ` dpdklab
2024-07-02 17:17 ` dpdklab
2024-07-02 17:25 ` dpdklab
2024-07-02 17:30 ` dpdklab
2024-07-02 17:31 ` dpdklab
2024-07-02 17:36 ` |SUCCESS| " dpdklab
2024-07-02 18:14 ` dpdklab
2024-07-02 19:15 ` dpdklab
2024-07-02 19:22 ` dpdklab
2024-07-02 19:36 ` dpdklab
2024-07-02 19:51 ` dpdklab
2024-07-02 20:30 ` 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=6683fad2.050a0220.e191a.4000SMTPIN_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).