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| pw143120 [PATCH] net/tap: avoid memcpy with NULL arg
Date: Tue, 13 Aug 2024 21:14:42 -0700 (PDT)	[thread overview]
Message-ID: <66bc2f32.170a0220.2b251.8d51SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240814023426.124491-1-stephen@networkplumber.org>

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

_Testing pending_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, August 14 2024 02:34:16 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e0f7ebe88ab4588dd352e9ec14270ce4e3b1470b

143120 --> testing pending

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

Test environment and result as below:

+------------------------------------+--------------------+
|            Environment             | dpdk_meson_compile |
+====================================+====================+
| RHEL9 (ARM)                        | PASS               |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PEND               |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE               | PASS               |
+------------------------------------+--------------------+
| Debian 12 with MUSDK               | PASS               |
+------------------------------------+--------------------+
| Fedora 38 (ARM Clang)              | PEND               |
+------------------------------------+--------------------+
| Fedora 37 (ARM)                    | PEND               |
+------------------------------------+--------------------+
| Fedora 39 (ARM)                    | PEND               |
+------------------------------------+--------------------+
| Fedora 38 (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 38 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.6

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

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

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-08-14  4:14 UTC|newest]

Thread overview: 95+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240814023426.124491-1-stephen@networkplumber.org>
2024-08-14  2:22 ` |SUCCESS| " qemudev
2024-08-14  2:26 ` qemudev
2024-08-14  2:35 ` checkpatch
2024-08-14  3:22 ` 0-day Robot
2024-08-14  3:49 ` dpdklab
2024-08-14  3:51 ` dpdklab
2024-08-14  3:54 ` dpdklab
2024-08-14  3:54 ` |PENDING| " dpdklab
2024-08-14  3:57 ` |SUCCESS| " dpdklab
2024-08-14  3:57 ` dpdklab
2024-08-14  3:59 ` |PENDING| " dpdklab
2024-08-14  3:59 ` dpdklab
2024-08-14  4:00 ` dpdklab
2024-08-14  4:03 ` dpdklab
2024-08-14  4:05 ` dpdklab
2024-08-14  4:05 ` dpdklab
2024-08-14  4:06 ` dpdklab
2024-08-14  4:06 ` dpdklab
2024-08-14  4:06 ` dpdklab
2024-08-14  4:07 ` dpdklab
2024-08-14  4:08 ` |SUCCESS| " dpdklab
2024-08-14  4:08 ` |PENDING| " dpdklab
2024-08-14  4:11 ` dpdklab
2024-08-14  4:11 ` |SUCCESS| " dpdklab
2024-08-14  4:12 ` |PENDING| " dpdklab
2024-08-14  4:12 ` dpdklab
2024-08-14  4:12 ` dpdklab
2024-08-14  4:13 ` dpdklab
2024-08-14  4:14 ` |SUCCESS| " dpdklab
2024-08-14  4:14 ` |PENDING| " dpdklab
2024-08-14  4:14 ` dpdklab [this message]
2024-08-14  4:14 ` dpdklab
2024-08-14  4:15 ` dpdklab
2024-08-14  4:15 ` dpdklab
2024-08-14  4:15 ` |SUCCESS| " dpdklab
2024-08-14  4:15 ` |PENDING| " dpdklab
2024-08-14  4:16 ` dpdklab
2024-08-14  4:16 ` dpdklab
2024-08-14  4:16 ` dpdklab
2024-08-14  4:17 ` dpdklab
2024-08-14  4:17 ` dpdklab
2024-08-14  4:17 ` dpdklab
2024-08-14  4:18 ` dpdklab
2024-08-14  4:18 ` dpdklab
2024-08-14  4:18 ` dpdklab
2024-08-14  4:18 ` |SUCCESS| " dpdklab
2024-08-14  4:19 ` |PENDING| " dpdklab
2024-08-14  4:21 ` dpdklab
2024-08-14  4:21 ` dpdklab
2024-08-14  4:21 ` dpdklab
2024-08-14  4:21 ` dpdklab
2024-08-14  4:22 ` dpdklab
2024-08-14  4:22 ` dpdklab
2024-08-14  4:22 ` dpdklab
2024-08-14  4:23 ` dpdklab
2024-08-14  4:23 ` dpdklab
2024-08-14  4:25 ` dpdklab
2024-08-14  4:25 ` dpdklab
2024-08-14  4:25 ` dpdklab
2024-08-14  4:26 ` dpdklab
2024-08-14  4:26 ` dpdklab
2024-08-14  4:27 ` dpdklab
2024-08-14  4:27 ` dpdklab
2024-08-14  4:27 ` dpdklab
2024-08-14  4:28 ` dpdklab
2024-08-14  4:28 ` dpdklab
2024-08-14  4:28 ` dpdklab
2024-08-14  4:29 ` |SUCCESS| " dpdklab
2024-08-14  4:29 ` |PENDING| " dpdklab
2024-08-14  4:29 ` dpdklab
2024-08-14  4:29 ` dpdklab
2024-08-14  4:30 ` dpdklab
2024-08-14  4:30 ` dpdklab
2024-08-14  4:32 ` dpdklab
2024-08-14  4:33 ` dpdklab
2024-08-14  4:35 ` dpdklab
2024-08-14  4:35 ` dpdklab
2024-08-14  4:35 ` |SUCCESS| " dpdklab
2024-08-14  4:37 ` |PENDING| " dpdklab
2024-08-14  4:38 ` dpdklab
2024-08-14  4:40 ` |SUCCESS| " dpdklab
2024-08-14  4:40 ` dpdklab
2024-08-14  4:42 ` |PENDING| " dpdklab
2024-08-14  4:44 ` dpdklab
2024-08-14  4:48 ` dpdklab
2024-08-14  4:49 ` |SUCCESS| " dpdklab
2024-08-14  4:50 ` |PENDING| " dpdklab
2024-08-14  4:51 ` |SUCCESS| " dpdklab
2024-08-14  4:52 ` dpdklab
2024-08-14  4:59 ` dpdklab
2024-08-14  5:04 ` dpdklab
2024-08-14  5:09 ` dpdklab
2024-08-14  5:32 ` |PENDING| " dpdklab
2024-08-14  5:53 ` dpdklab
2024-08-14  5:57 ` |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=66bc2f32.170a0220.2b251.8d51SMTPIN_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).