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| [GIT MASTER] b2f967dcae6940b4707437d024747318a159f9b3
Date: Fri, 25 Aug 2023 19:03:42 -0700 (PDT)	[thread overview]
Message-ID: <64e95d7e.0c0a0220.d5983.9a74SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk

b2f967dcae6940b4707437d024747318a159f9b3 --> testing pass

Test environment and result as below:

+------------------------------------+--------------------+
|            Environment             | dpdk_meson_compile |
+====================================+====================+
| Ubuntu 20.04 ARM SVE               | PASS               |
+------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS               |
+------------------------------------+--------------------+
| Fedora 37 (ARM)                    | PASS               |
+------------------------------------+--------------------+
| Ubuntu 20.04 (ARM)                 | 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 ARM GCC Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-08-26  2:03 UTC|newest]

Thread overview: 117+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-26  2:03 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-28  1:38 dpdklab
2023-08-28  1:37 dpdklab
2023-08-28  1:23 dpdklab
2023-08-28  1:18 dpdklab
2023-08-28  1:15 dpdklab
2023-08-28  1:11 dpdklab
2023-08-28  1:11 dpdklab
2023-08-28  1:09 dpdklab
2023-08-28  1:09 dpdklab
2023-08-28  1:07 dpdklab
2023-08-28  1:04 dpdklab
2023-08-28  1:02 dpdklab
2023-08-28  1:02 dpdklab
2023-08-28  0:57 dpdklab
2023-08-27  2:17 dpdklab
2023-08-27  1:59 dpdklab
2023-08-27  1:58 dpdklab
2023-08-27  1:51 dpdklab
2023-08-27  1:51 dpdklab
2023-08-27  1:47 dpdklab
2023-08-27  1:47 dpdklab
2023-08-27  1:46 dpdklab
2023-08-27  1:43 dpdklab
2023-08-27  1:43 dpdklab
2023-08-27  1:38 dpdklab
2023-08-27  1:38 dpdklab
2023-08-27  1:37 dpdklab
2023-08-27  1:37 dpdklab
2023-08-27  1:32 dpdklab
2023-08-27  1:30 dpdklab
2023-08-27  1:30 dpdklab
2023-08-27  1:29 dpdklab
2023-08-27  1:27 dpdklab
2023-08-27  1:27 dpdklab
2023-08-27  1:25 dpdklab
2023-08-27  1:24 dpdklab
2023-08-27  1:23 dpdklab
2023-08-27  1:20 dpdklab
2023-08-27  1:20 dpdklab
2023-08-27  1:20 dpdklab
2023-08-27  1:17 dpdklab
2023-08-27  1:17 dpdklab
2023-08-27  1:16 dpdklab
2023-08-27  1:16 dpdklab
2023-08-27  1:14 dpdklab
2023-08-27  1:13 dpdklab
2023-08-27  1:11 dpdklab
2023-08-27  1:07 dpdklab
2023-08-27  1:06 dpdklab
2023-08-27  1:06 dpdklab
2023-08-27  1:06 dpdklab
2023-08-27  1:02 dpdklab
2023-08-27  1:02 dpdklab
2023-08-27  1:01 dpdklab
2023-08-27  1:01 dpdklab
2023-08-27  1:00 dpdklab
2023-08-27  1:00 dpdklab
2023-08-27  1:00 dpdklab
2023-08-27  1:00 dpdklab
2023-08-27  0:58 dpdklab
2023-08-27  0:56 dpdklab
2023-08-27  0:56 dpdklab
2023-08-27  0:55 dpdklab
2023-08-27  0:55 dpdklab
2023-08-27  0:55 dpdklab
2023-08-26  4:27 dpdklab
2023-08-26  4:14 dpdklab
2023-08-26  4:09 dpdklab
2023-08-26  3:51 dpdklab
2023-08-26  3:48 dpdklab
2023-08-26  3:47 dpdklab
2023-08-26  3:21 dpdklab
2023-08-26  2:35 dpdklab
2023-08-26  2:26 dpdklab
2023-08-26  2:14 dpdklab
2023-08-26  2:14 dpdklab
2023-08-26  2:12 dpdklab
2023-08-26  2:09 dpdklab
2023-08-26  2:06 dpdklab
2023-08-26  2:06 dpdklab
2023-08-26  2:05 dpdklab
2023-08-26  2:04 dpdklab
2023-08-26  2:03 dpdklab
2023-08-26  2:01 dpdklab
2023-08-26  2:01 dpdklab
2023-08-26  2:00 dpdklab
2023-08-26  2:00 dpdklab
2023-08-26  1:57 dpdklab
2023-08-26  1:56 dpdklab
2023-08-26  1:56 dpdklab
2023-08-26  1:56 dpdklab
2023-08-26  1:55 dpdklab
2023-08-26  1:54 dpdklab
2023-08-26  1:47 dpdklab
2023-08-26  1:45 dpdklab
2023-08-26  1:44 dpdklab
2023-08-26  1:44 dpdklab
2023-08-26  1:44 dpdklab
2023-08-26  1:43 dpdklab
2023-08-26  1:41 dpdklab
2023-08-26  1:38 dpdklab
2023-08-26  1:36 dpdklab
2023-08-26  1:35 dpdklab
2023-08-26  1:33 dpdklab
2023-08-26  1:33 dpdklab
2023-08-26  1:32 dpdklab
2023-08-26  1:30 dpdklab
2023-08-26  1:29 dpdklab
2023-08-26  1:29 dpdklab
2023-08-26  1:22 dpdklab
2023-08-26  1:21 dpdklab
2023-08-26  1:21 dpdklab
2023-08-26  1:21 dpdklab
2023-08-26  1:20 dpdklab
2023-08-26  1:19 dpdklab
2023-08-26  1:18 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=64e95d7e.0c0a0220.d5983.9a74SMTPIN_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).