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: |SUCCESS| pw141746 [PATCH] net/tap/bpf: fix meson warning
Date: Tue, 25 Jun 2024 14:51:51 -0700 (PDT)	[thread overview]
Message-ID: <667b3bf7.050a0220.79317.0efeSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240625170652.12017-1-stephen@networkplumber.org>

Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/141746

_Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, June 25 2024 17:06:52 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fbba6db3640f9f623c29c452e1a6b057073e81d2

141746 --> testing pass

Test environment and result as below:

+-----------------------+----------------+--------------+
|      Environment      | dpdk_unit_test | lpm_autotest |
+=======================+================+==============+
| Fedora 37 (ARM)       | PASS           | SKIPPED      |
+-----------------------+----------------+--------------+
| CentOS Stream 9 (ARM) | PASS           | SKIPPED      |
+-----------------------+----------------+--------------+
| Debian 12 (arm)       | PASS           | SKIPPED      |
+-----------------------+----------------+--------------+
| Fedora 39 (ARM)       | PASS           | SKIPPED      |
+-----------------------+----------------+--------------+
| Ubuntu 20.04 ARM SVE  | SKIPPED        | PASS         |
+-----------------------+----------------+--------------+


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

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.4.1

Debian 12 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

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

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-25 21:51 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240625170652.12017-1-stephen@networkplumber.org>
2024-06-25 16:41 ` qemudev
2024-06-25 16:45 ` qemudev
2024-06-25 17:07 ` checkpatch
2024-06-25 18:05 ` 0-day Robot
2024-06-25 20:50 ` dpdklab
2024-06-25 20:52 ` dpdklab
2024-06-25 20:52 ` dpdklab
2024-06-25 20:53 ` dpdklab
2024-06-25 20:54 ` dpdklab
2024-06-25 21:38 ` dpdklab
2024-06-25 21:41 ` dpdklab
2024-06-25 21:42 ` dpdklab
2024-06-25 21:42 ` dpdklab
2024-06-25 21:42 ` dpdklab
2024-06-25 21:43 ` dpdklab
2024-06-25 21:44 ` dpdklab
2024-06-25 21:44 ` dpdklab
2024-06-25 21:45 ` dpdklab
2024-06-25 21:46 ` dpdklab
2024-06-25 21:47 ` dpdklab
2024-06-25 21:48 ` dpdklab
2024-06-25 21:49 ` dpdklab
2024-06-25 21:50 ` dpdklab
2024-06-25 21:51 ` dpdklab [this message]
2024-06-25 21:51 ` dpdklab
2024-06-25 21:57 ` dpdklab
2024-06-25 21:59 ` dpdklab
2024-06-25 21:59 ` dpdklab
2024-06-25 21:59 ` dpdklab
2024-06-25 21:59 ` dpdklab
2024-06-25 22:00 ` dpdklab
2024-06-25 22:00 ` dpdklab
2024-06-25 22:01 ` dpdklab
2024-06-25 22:03 ` dpdklab
2024-06-25 22:05 ` dpdklab
2024-06-25 22:15 ` dpdklab
2024-06-25 22:15 ` dpdklab
2024-06-25 22:25 ` dpdklab
2024-06-25 22:25 ` dpdklab
2024-06-25 22:34 ` dpdklab
2024-06-25 22:36 ` dpdklab
2024-06-25 22:37 ` dpdklab
2024-06-25 22:48 ` dpdklab
2024-06-25 23:04 ` dpdklab
2024-06-25 23:10 ` dpdklab
2024-06-25 23:12 ` dpdklab
2024-06-25 23:12 ` dpdklab
2024-06-25 23:13 ` dpdklab
2024-06-25 23:14 ` dpdklab
2024-06-25 23:16 ` dpdklab
2024-06-25 23:16 ` dpdklab
2024-06-25 23:17 ` dpdklab
2024-06-25 23:18 ` dpdklab
2024-06-25 23:22 ` 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=667b3bf7.050a0220.79317.0efeSMTPIN_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).