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] 9b1122634e8affeb1a3d957f3a96e48ae17956bc
Date: Tue, 03 Oct 2023 05:42:42 -0700 (PDT)	[thread overview]
Message-ID: <651c0c42.a70a0220.1b602.3ecaSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk-next-eventdev

9b1122634e8affeb1a3d957f3a96e48ae17956bc --> testing pass

Test environment and result as below:

+--------------------------+--------------------+
|       Environment        | dpdk_meson_compile |
+==========================+====================+
| Ubuntu 20.04 ARM SVE     | PASS               |
+--------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS               |
+--------------------------+--------------------+
| Fedora 37 (ARM)          | PASS               |
+--------------------------+--------------------+
| CentOS Stream 9 (ARM)    | PASS               |
+--------------------------+--------------------+
| Ubuntu 20.04 (ARM)       | PASS               |
+--------------------------+--------------------+
| Fedora 38 (ARM)          | 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)

Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

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

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

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

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/26335/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-03 12:42 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-03 12:42 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-03 13:36 dpdklab
2023-10-03 13:26 dpdklab
2023-10-03 12:59 dpdklab
2023-10-03 12:44 dpdklab
2023-10-03 12:43 dpdklab
2023-10-03 12:42 dpdklab
2023-10-03 12:41 dpdklab
2023-10-03 12:41 dpdklab
2023-10-03 12:41 dpdklab
2023-10-03 12:40 dpdklab
2023-10-03 12:32 dpdklab
2023-10-03 12:26 dpdklab
2023-10-03 12:22 dpdklab
2023-10-03 12:20 dpdklab
2023-10-03 11:55 dpdklab
2023-10-03 11:52 dpdklab
2023-10-03 11:52 dpdklab
2023-10-03 11:50 dpdklab
2023-10-03 11:49 dpdklab
2023-10-03 11:38 dpdklab
2023-10-03 11:36 dpdklab
2023-10-03 11:36 dpdklab
2023-10-03 11:35 dpdklab
2023-10-03 11:35 dpdklab
2023-10-03 11:29 dpdklab
2023-10-03 11:25 dpdklab
2023-10-03 11:25 dpdklab
2023-10-03 11:24 dpdklab
2023-10-03 11:24 dpdklab
2023-10-03 11:24 dpdklab
2023-10-03 11:19 dpdklab
2023-10-03 11:18 dpdklab
2023-10-03 11:18 dpdklab
2023-10-03 11:17 dpdklab
2023-10-03 11:16 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=651c0c42.a70a0220.1b602.3ecaSMTPIN_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).