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| pw142454 [PATCH] vdpa: update used->flags in used ring rel
Date: Tue, 16 Jul 2024 21:14:52 -0700 (PDT)	[thread overview]
Message-ID: <6697453c.050a0220.25fd20.55a5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240717032447.39723-1-xiangwencheng@dayudpu.com>

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

_Testing pending_

Submitter: BillXiang <xiangwencheng@dayudpu.com>
Date: Wednesday, July 17 2024 03:24:47 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:9cbdb606e5d04de04be3d9f70f0e76551e8c9a36

142454 --> testing pending

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 39 (ARM Clang)              | PEND               |
+------------------------------------+--------------------+
| Fedora 39 (ARM)                    | PEND               |
+------------------------------------+--------------------+
| Fedora 38 (ARM Clang)              | PEND               |
+------------------------------------+--------------------+
| Fedora 38 (ARM)                    | PEND               |
+------------------------------------+--------------------+
| Fedora 40 (ARM Clang)              | PEND               |
+------------------------------------+--------------------+
| Fedora 40 (ARM)                    | PEND               |
+------------------------------------+--------------------+
| Ubuntu 22.04 (ARM)                 | PEND               |
+------------------------------------+--------------------+
| Ubuntu 20.04 (ARM)                 | PEND               |
+------------------------------------+--------------------+
| Ubuntu 24.04 (ARM)                 | PEND               |
+------------------------------------+--------------------+


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

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

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

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

Fedora 39 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

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

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

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

Fedora 40 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 14.1.1

Ubuntu 22.04 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.4.0

Ubuntu 20.04 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 9.4.0

Ubuntu 24.04 (ARM)
	Kernel: 5.4.0-167-generic
	Compiler: gcc 13.2.0

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

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-17  4:14 UTC|newest]

Thread overview: 115+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240717032447.39723-1-xiangwencheng@dayudpu.com>
2024-07-17  3:05 ` |SUCCESS| pw142454 [PATCH] vdpa: update used->flags in used ring relay qemudev
2024-07-17  3:09 ` qemudev
2024-07-17  3:27 ` checkpatch
2024-07-17  3:58 ` |PENDING| pw142454 [PATCH] vdpa: update used->flags in used ring rel dpdklab
2024-07-17  4:00 ` dpdklab
2024-07-17  4:04 ` dpdklab
2024-07-17  4:06 ` dpdklab
2024-07-17  4:06 ` |SUCCESS| " dpdklab
2024-07-17  4:08 ` dpdklab
2024-07-17  4:08 ` dpdklab
2024-07-17  4:10 ` |PENDING| " dpdklab
2024-07-17  4:11 ` dpdklab
2024-07-17  4:12 ` dpdklab
2024-07-17  4:14 ` dpdklab
2024-07-17  4:14 ` dpdklab [this message]
2024-07-17  4:15 ` dpdklab
2024-07-17  4:16 ` dpdklab
2024-07-17  4:16 ` |SUCCESS| " dpdklab
2024-07-17  4:17 ` |PENDING| " dpdklab
2024-07-17  4:19 ` dpdklab
2024-07-17  4:20 ` dpdklab
2024-07-17  4:21 ` |SUCCESS| " dpdklab
2024-07-17  4:22 ` |PENDING| " dpdklab
2024-07-17  4:22 ` dpdklab
2024-07-17  4:22 ` dpdklab
2024-07-17  4:23 ` dpdklab
2024-07-17  4:24 ` |SUCCESS| pw142454 [PATCH] vdpa: update used->flags in used ring relay 0-day Robot
2024-07-17  4:24 ` |PENDING| pw142454 [PATCH] vdpa: update used->flags in used ring rel dpdklab
2024-07-17  4:24 ` dpdklab
2024-07-17  4:25 ` dpdklab
2024-07-17  4:25 ` |SUCCESS| " dpdklab
2024-07-17  4:25 ` |PENDING| " dpdklab
2024-07-17  4:25 ` dpdklab
2024-07-17  4:26 ` dpdklab
2024-07-17  4:26 ` |SUCCESS| " dpdklab
2024-07-17  4:27 ` |PENDING| " dpdklab
2024-07-17  4:27 ` dpdklab
2024-07-17  4:28 ` dpdklab
2024-07-17  4:28 ` dpdklab
2024-07-17  4:28 ` dpdklab
2024-07-17  4:29 ` dpdklab
2024-07-17  4:29 ` dpdklab
2024-07-17  4:30 ` dpdklab
2024-07-17  4:30 ` dpdklab
2024-07-17  4:32 ` dpdklab
2024-07-17  4:32 ` dpdklab
2024-07-17  4:33 ` dpdklab
2024-07-17  4:34 ` |SUCCESS| " dpdklab
2024-07-17  4:35 ` dpdklab
2024-07-17  4:36 ` |PENDING| " dpdklab
2024-07-17  4:40 ` dpdklab
2024-07-17  4:40 ` dpdklab
2024-07-17  4:42 ` dpdklab
2024-07-17  4:42 ` dpdklab
2024-07-17  4:43 ` dpdklab
2024-07-17  4:44 ` dpdklab
2024-07-17  4:48 ` dpdklab
2024-07-17  4:51 ` dpdklab
2024-07-17  4:51 ` dpdklab
2024-07-17  4:51 ` dpdklab
2024-07-17  4:55 ` dpdklab
2024-07-17  4:56 ` dpdklab
2024-07-17  4:56 ` dpdklab
2024-07-17  4:57 ` dpdklab
2024-07-17  4:58 ` dpdklab
2024-07-17  4:59 ` dpdklab
2024-07-17  4:59 ` dpdklab
2024-07-17  5:02 ` dpdklab
2024-07-17  5:05 ` dpdklab
2024-07-17  5:05 ` dpdklab
2024-07-17  5:06 ` dpdklab
2024-07-17  5:07 ` dpdklab
2024-07-17  5:07 ` dpdklab
2024-07-17  5:08 ` dpdklab
2024-07-17  5:08 ` dpdklab
2024-07-17  5:08 ` dpdklab
2024-07-17  5:09 ` dpdklab
2024-07-17  5:09 ` dpdklab
2024-07-17  5:11 ` |SUCCESS| " dpdklab
2024-07-17  5:11 ` |PENDING| " dpdklab
2024-07-17  5:12 ` dpdklab
2024-07-17  5:14 ` |SUCCESS| " dpdklab
2024-07-17  5:14 ` dpdklab
2024-07-17  5:14 ` |PENDING| " dpdklab
2024-07-17  5:14 ` |SUCCESS| " dpdklab
2024-07-17  5:15 ` |PENDING| " dpdklab
2024-07-17  5:15 ` |SUCCESS| " dpdklab
2024-07-17  5:15 ` dpdklab
2024-07-17  5:18 ` |PENDING| " dpdklab
2024-07-17  5:20 ` dpdklab
2024-07-17  5:21 ` dpdklab
2024-07-17  5:22 ` |SUCCESS| " dpdklab
2024-07-17  5:23 ` |PENDING| " dpdklab
2024-07-17  5:24 ` dpdklab
2024-07-17  5:24 ` dpdklab
2024-07-17  5:26 ` |SUCCESS| " dpdklab
2024-07-17  5:27 ` dpdklab
2024-07-17  5:30 ` |PENDING| " dpdklab
2024-07-17  5:31 ` |SUCCESS| " dpdklab
2024-07-17  5:32 ` |PENDING| " dpdklab
2024-07-17  5:36 ` |SUCCESS| " dpdklab
2024-07-17  5:37 ` |PENDING| " dpdklab
2024-07-17  5:37 ` dpdklab
2024-07-17  5:39 ` dpdklab
2024-07-17  5:42 ` dpdklab
2024-07-17  5:43 ` dpdklab
2024-07-17  5:44 ` dpdklab
2024-07-17  5:44 ` dpdklab
2024-07-17  5:45 ` |SUCCESS| " dpdklab
2024-07-17  5:46 ` |PENDING| " dpdklab
2024-07-17  5:48 ` dpdklab
2024-07-17  5:49 ` dpdklab
2024-07-17  5:52 ` dpdklab
2024-07-17  5:59 ` dpdklab
2024-07-17  6:03 ` |SUCCESS| " 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=6697453c.050a0220.25fd20.55a5SMTPIN_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).