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,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| [GIT MASTER] 7e338963a9c9e3c66f667985578ab2197e55bcc6
Date: Wed, 04 Oct 2023 14:25:54 -0700 (PDT)	[thread overview]
Message-ID: <651dd862.0d0a0220.f6a4e.08a9SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk-next-net

7e338963a9c9e3c66f667985578ab2197e55bcc6 --> testing pass

Test environment and result as below:

+----------------------------------------+--------------------+
|              Environment               | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE                   | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS               |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile   | PASS               |
+----------------------------------------+--------------------+
| Fedora 38 (ARM Clang)                  | PASS               |
+----------------------------------------+--------------------+


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

Ubuntu 20.04 aarch32 GCC Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: gcc 9.3.0

Ubuntu 20.04 ARM Clang Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: clang version 10.0.0-4ubuntu1

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

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/26355/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-04 21:25 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-04 21:25 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-04 22:01 dpdklab
2023-10-04 21:42 dpdklab
2023-10-04 21:38 dpdklab
2023-10-04 21:37 dpdklab
2023-10-04 21:37 dpdklab
2023-10-04 21:31 dpdklab
2023-10-04 21:28 dpdklab
2023-10-04 21:20 dpdklab
2023-10-04 21:19 dpdklab
2023-10-04 21:17 dpdklab
2023-10-04 21:15 dpdklab
2023-10-04 21:14 dpdklab
2023-10-04 21:13 dpdklab
2023-10-04 21:11 dpdklab
2023-10-04 21:07 dpdklab
2023-10-04 21:04 dpdklab
2023-10-04 21:01 dpdklab
2023-10-04 21:01 dpdklab
2023-10-04 20:58 dpdklab
2023-10-04 20:47 dpdklab
2023-10-04 20:46 dpdklab
2023-10-04 20:43 dpdklab
2023-10-04 20:40 dpdklab
2023-10-04 20:37 dpdklab
2023-10-04 20:37 dpdklab
2023-10-04 20:31 dpdklab
2023-10-04 20:29 dpdklab
2023-10-04 20:23 dpdklab
2023-10-04 20:22 dpdklab
2023-10-04 20:20 dpdklab
2023-10-04 20:10 dpdklab
2023-10-04 20:06 dpdklab
2023-10-04 20:05 dpdklab
2023-10-04 20:04 dpdklab
2023-10-04 19:49 dpdklab
2023-10-04 19:39 dpdklab
2023-10-04 19:38 dpdklab
2023-10-04 19:35 dpdklab
2023-10-04 19:34 dpdklab
2023-10-04 19:26 dpdklab
2023-10-04 19:25 dpdklab
2023-10-04 19:25 dpdklab
2023-10-04 19:24 dpdklab
2023-10-04 19:24 dpdklab
2023-10-04 19: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=651dd862.0d0a0220.f6a4e.08a9SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ferruh.yigit@amd.com \
    --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).