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| pw142025-142026 [PATCH] [v2,2/2] net/cnxk: fix to avoid NP
Date: Tue, 02 Jul 2024 23:35:39 -0700 (PDT)	[thread overview]
Message-ID: <6684f13b.170a0220.c1c38.8f73SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240702144033.3345075-2-rbhansali@marvell.com>

Test-Label: iol-compile-arm64-testing
Test-Status: PENDING
http://dpdk.org/patch/142026

_Testing pending_

Submitter: Rahul Bhansali <rbhansali@marvell.com>
Date: Tuesday, July 02 2024 14:40:33 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:362db0a4d230fbe43c2da1d6e34ecd0f2f946903

142025-142026 --> testing pending

Test environment and result as below:

+------------------------------------+--------------------+
|            Environment             | dpdk_meson_compile |
+====================================+====================+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS               |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE               | PASS               |
+------------------------------------+--------------------+
| RHEL9 (ARM)                        | PEND               |
+------------------------------------+--------------------+
| Debian 12 with MUSDK               | PEND               |
+------------------------------------+--------------------+
| Fedora 37 (ARM)                    | PEND               |
+------------------------------------+--------------------+


Ubuntu 20.04 ARM GCC Cross Compile
	Kernel: 5.4.0-167-generic
	Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-167-generic
	Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0

RHEL9 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 11.4.1

Debian 12 with MUSDK
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

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

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-03  6:35 UTC|newest]

Thread overview: 114+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240702144033.3345075-2-rbhansali@marvell.com>
2024-07-02 14:17 ` |SUCCESS| pw142025-142026 [PATCH v2 2/2] net/cnxk: fix to avoid NPC Rx and MCAM disable qemudev
2024-07-02 14:22 ` qemudev
2024-07-02 14:41 ` |SUCCESS| pw142026 " checkpatch
2024-07-02 15:45 ` 0-day Robot
2024-07-02 23:06 ` |PENDING| pw142025-142026 [PATCH] [v2,2/2] net/cnxk: fix to avoid NP dpdklab
2024-07-02 23:12 ` dpdklab
2024-07-02 23:18 ` |SUCCESS| " dpdklab
2024-07-02 23:25 ` dpdklab
2024-07-02 23:26 ` dpdklab
2024-07-02 23:32 ` dpdklab
2024-07-02 23:40 ` dpdklab
2024-07-02 23:40 ` dpdklab
2024-07-02 23:44 ` dpdklab
2024-07-02 23:49 ` dpdklab
2024-07-02 23:53 ` dpdklab
2024-07-02 23:54 ` dpdklab
2024-07-02 23:58 ` dpdklab
2024-07-03  0:05 ` dpdklab
2024-07-03  0:12 ` dpdklab
2024-07-03  0:21 ` |PENDING| " dpdklab
2024-07-03  0:25 ` dpdklab
2024-07-03  0:28 ` dpdklab
2024-07-03  0:32 ` dpdklab
2024-07-03  0:36 ` dpdklab
2024-07-03  0:36 ` dpdklab
2024-07-03  0:40 ` |SUCCESS| " dpdklab
2024-07-03  0:41 ` |PENDING| " dpdklab
2024-07-03  0:44 ` dpdklab
2024-07-03  0:45 ` dpdklab
2024-07-03  0:48 ` dpdklab
2024-07-03  0:49 ` dpdklab
2024-07-03  0:50 ` dpdklab
2024-07-03  0:51 ` dpdklab
2024-07-03  0:54 ` dpdklab
2024-07-03  0:58 ` |SUCCESS| " dpdklab
2024-07-03  2:17 ` |PENDING| " dpdklab
2024-07-03  2:18 ` dpdklab
2024-07-03  2:21 ` dpdklab
2024-07-03  2:23 ` |SUCCESS| " dpdklab
2024-07-03  2:23 ` dpdklab
2024-07-03  3:00 ` |PENDING| " dpdklab
2024-07-03  6:02 ` dpdklab
2024-07-03  6:02 ` dpdklab
2024-07-03  6:04 ` dpdklab
2024-07-03  6:09 ` dpdklab
2024-07-03  6:12 ` dpdklab
2024-07-03  6:19 ` dpdklab
2024-07-03  6:21 ` dpdklab
2024-07-03  6:22 ` dpdklab
2024-07-03  6:22 ` dpdklab
2024-07-03  6:33 ` dpdklab
2024-07-03  6:34 ` dpdklab
2024-07-03  6:34 ` dpdklab
2024-07-03  6:35 ` dpdklab [this message]
2024-07-03  6:38 ` dpdklab
2024-07-03  6:38 ` dpdklab
2024-07-03  6:40 ` dpdklab
2024-07-03  6:41 ` dpdklab
2024-07-03  6:45 ` dpdklab
2024-07-03  6:46 ` dpdklab
2024-07-03  6:52 ` dpdklab
2024-07-03  6:55 ` dpdklab
2024-07-03  6:55 ` dpdklab
2024-07-03  6:58 ` dpdklab
2024-07-03  6:58 ` dpdklab
2024-07-03  7:02 ` dpdklab
2024-07-03  7:03 ` dpdklab
2024-07-03  7:04 ` dpdklab
2024-07-03  7:05 ` dpdklab
2024-07-03  7:06 ` dpdklab
2024-07-03  7:06 ` dpdklab
2024-07-03  7:06 ` |SUCCESS| " dpdklab
2024-07-03  7:08 ` |PENDING| " dpdklab
2024-07-03  7:10 ` dpdklab
2024-07-03  7:11 ` dpdklab
2024-07-03  7:16 ` dpdklab
2024-07-03  7:16 ` dpdklab
2024-07-03  7:20 ` dpdklab
2024-07-03  7:21 ` dpdklab
2024-07-03  7:21 ` dpdklab
2024-07-03  7:24 ` dpdklab
2024-07-03  7:24 ` dpdklab
2024-07-03  7:28 ` dpdklab
2024-07-03  7:33 ` dpdklab
2024-07-03  7:34 ` dpdklab
2024-07-03  7:34 ` dpdklab
2024-07-03  7:36 ` |SUCCESS| " dpdklab
2024-07-03  7:41 ` |PENDING| " dpdklab
2024-07-03  7:56 ` dpdklab
2024-07-03  7:58 ` dpdklab
2024-07-03  8:01 ` dpdklab
2024-07-03  8:15 ` dpdklab
2024-07-03  8:18 ` dpdklab
2024-07-03  8:26 ` dpdklab
2024-07-03  8:29 ` |SUCCESS| " dpdklab
2024-07-03  8:54 ` dpdklab
2024-07-03 10:30 ` |PENDING| " dpdklab
2024-07-03 10:40 ` dpdklab
2024-07-03 10:51 ` dpdklab
2024-07-03 10:54 ` dpdklab
2024-07-03 11:00 ` dpdklab
2024-07-03 11:07 ` dpdklab
2024-07-03 11:24 ` dpdklab
2024-07-03 11:32 ` dpdklab
2024-07-03 11:38 ` dpdklab
2024-07-03 11:50 ` dpdklab
2024-07-03 11:56 ` dpdklab
2024-07-03 12:03 ` dpdklab
2024-07-03 12:08 ` dpdklab
2024-07-03 12:11 ` dpdklab
2024-07-03 12:15 ` dpdklab
2024-07-03 12:18 ` |SUCCESS| " dpdklab
2024-07-03 18:07 ` |FAILURE| " dpdklab
2024-07-03 18:21 ` 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=6684f13b.170a0220.c1c38.8f73SMTPIN_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).