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| pw144785-144790 [PATCH] [v3,6/6] examples: use eventdev pr
Date: Tue, 01 Oct 2024 05:42:13 -0700 (PDT)	[thread overview]
Message-ID: <66fbee25.050a0220.376e7c.ea65SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241001061411.2537-7-pbhagavatula@marvell.com>

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

_Testing pending_

Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Tuesday, October 01 2024 06:14:11 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:52a4028e4c33df32c691aa88751a659534b9ef02

144785-144790 --> testing pending

Upstream job id: Generic-DPDK-Compile-Meson#308026

Test environment and result as below:

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


RHEL9 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

Ubuntu 20.04 ARM GCC Cross Compile
	Kernel: Depends on container host
	Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

Ubuntu 20.04 ARM SVE
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0

Debian 12 with MUSDK
	Kernel: Depends on container host
	Compiler: gcc (Debian 12.2.0-14) 12.2.0

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1 20230508 (Red Hat 12.3.1-1)

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.2.1 20240316 (Red Hat 13.2.1-7)

Fedora 38 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.6 (Fedora 16.0.6-4.fc38)

Fedora 39 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.3.1 20240522 (Red Hat 13.3.1-1)

Fedora 39 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6 (Fedora 17.0.6-2.fc39)

Fedora 40 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240801 (Red Hat 14.2.1-1)

Fedora 40 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 18.1.6 (Fedora 18.1.6-3.fc40)

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-10-01 12:42 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241001061411.2537-7-pbhagavatula@marvell.com>
2024-10-01  5:47 ` |SUCCESS| pw144785-144790 [PATCH v3 6/6] examples: use eventdev pre-scheduling qemudev
2024-10-01  5:52 ` qemudev
2024-10-01  6:16 ` |SUCCESS| pw144790 " checkpatch
2024-10-01  7:04 ` |FAILURE| " 0-day Robot
2024-10-01 11:03 ` |SUCCESS| pw144785-144790 [PATCH] [v3,6/6] examples: use eventdev pr dpdklab
2024-10-01 11:11 ` dpdklab
2024-10-01 11:13 ` |PENDING| " dpdklab
2024-10-01 11:16 ` |SUCCESS| " dpdklab
2024-10-01 11:22 ` dpdklab
2024-10-01 11:33 ` dpdklab
2024-10-01 11:37 ` dpdklab
2024-10-01 11:48 ` |PENDING| " dpdklab
2024-10-01 11:56 ` dpdklab
2024-10-01 12:08 ` |SUCCESS| " dpdklab
2024-10-01 12:09 ` dpdklab
2024-10-01 12:11 ` |WARNING| " dpdklab
2024-10-01 12:23 ` |FAILURE| " dpdklab
2024-10-01 12:24 ` dpdklab
2024-10-01 12:26 ` dpdklab
2024-10-01 12:28 ` dpdklab
2024-10-01 12:33 ` dpdklab
2024-10-01 12:36 ` |SUCCESS| " dpdklab
2024-10-01 12:36 ` |FAILURE| " dpdklab
2024-10-01 12:42 ` dpdklab [this message]
2024-10-01 12:42 ` dpdklab
2024-10-01 12:44 ` |WARNING| " dpdklab
2024-10-01 12:45 ` |FAILURE| " dpdklab
2024-10-01 12:48 ` dpdklab
2024-10-01 12:49 ` dpdklab
2024-10-01 12:50 ` dpdklab
2024-10-01 12:51 ` dpdklab
2024-10-01 12:54 ` dpdklab
2024-10-01 12:56 ` |WARNING| " dpdklab
2024-10-01 13:10 ` |FAILURE| " dpdklab
2024-10-01 13:24 ` |SUCCESS| " dpdklab
2024-10-01 16:08 ` dpdklab
2024-10-01 16:24 ` 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=66fbee25.050a0220.376e7c.ea65SMTPIN_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).