From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 0ae35eceb9e4569b0814fcf671b4455301bb7518
Date: Tue, 01 Aug 2023 05:30:35 -0700 (PDT) [thread overview]
Message-ID: <64c8faeb.920a0220.42936.8219SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-eventdev
0ae35eceb9e4569b0814fcf671b4455301bb7518 --> testing pass
Test environment and result as below:
+--------------------------+----------------+
| Environment | dpdk_unit_test |
+==========================+================+
| CentOS Stream 9 | PASS |
+--------------------------+----------------+
| CentOS Stream 9 (ARM) | PASS |
+--------------------------+----------------+
| Debian 11 (Buster) (ARM) | PASS |
+--------------------------+----------------+
| CentOS Stream 8 | PASS |
+--------------------------+----------------+
| Debian Bullseye | PASS |
+--------------------------+----------------+
| Fedora 37 (ARM) | PASS |
+--------------------------+----------------+
| Ubuntu 20.04 (ARM) | PASS |
+--------------------------+----------------+
| Fedora 38 (ARM) | PASS |
+--------------------------+----------------+
| Fedora 38 | PASS |
+--------------------------+----------------+
| Ubuntu 20.04 | PASS |
+--------------------------+----------------+
| openSUSE Leap 15 | PASS |
+--------------------------+----------------+
| Ubuntu 22.04 | PASS |
+--------------------------+----------------+
| Fedora 38 (ARM Clang) | PASS |
+--------------------------+----------------+
| RHEL8 | PASS |
+--------------------------+----------------+
| Debian Buster | PASS |
+--------------------------+----------------+
| Fedora 37 | PASS |
+--------------------------+----------------+
| RHEL 7 | PASS |
+--------------------------+----------------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
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
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
Fedora 38 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 16.0.3
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/25660/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-01 12:30 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 12:30 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-03 6:33 dpdklab
2023-08-03 6:33 dpdklab
2023-08-03 6:29 dpdklab
2023-08-03 6:18 dpdklab
2023-08-03 6:13 dpdklab
2023-08-03 6:09 dpdklab
2023-08-03 4:13 dpdklab
2023-08-03 4:11 dpdklab
2023-08-03 4:02 dpdklab
2023-08-03 3:47 dpdklab
2023-08-03 2:28 dpdklab
2023-08-03 2:11 dpdklab
2023-08-03 2:06 dpdklab
2023-08-03 1:59 dpdklab
2023-08-03 1:55 dpdklab
2023-08-03 1:28 dpdklab
2023-08-03 1:22 dpdklab
2023-08-03 1:20 dpdklab
2023-08-03 1:12 dpdklab
2023-08-03 1:10 dpdklab
2023-08-02 4:03 dpdklab
2023-08-02 3:28 dpdklab
2023-08-02 3:11 dpdklab
2023-08-02 3:11 dpdklab
2023-08-02 3:10 dpdklab
2023-08-02 3:06 dpdklab
2023-08-02 3:02 dpdklab
2023-08-02 2:51 dpdklab
2023-08-02 2:34 dpdklab
2023-08-02 2:10 dpdklab
2023-08-02 2:09 dpdklab
2023-08-02 2:05 dpdklab
2023-08-02 1:46 dpdklab
2023-08-02 1:34 dpdklab
2023-08-02 1:33 dpdklab
2023-08-02 1:22 dpdklab
2023-08-02 1:18 dpdklab
2023-08-02 1:18 dpdklab
2023-08-02 1:14 dpdklab
2023-08-02 1:13 dpdklab
2023-08-01 23:38 dpdklab
2023-08-01 23:33 dpdklab
2023-08-01 23:29 dpdklab
2023-08-01 23:13 dpdklab
2023-08-01 23:02 dpdklab
2023-08-01 21:08 dpdklab
2023-08-01 20:07 dpdklab
2023-08-01 20:07 dpdklab
2023-08-01 20:06 dpdklab
2023-08-01 18:57 dpdklab
2023-08-01 18:56 dpdklab
2023-08-01 18:55 dpdklab
2023-08-01 18:43 dpdklab
2023-08-01 18:38 dpdklab
2023-08-01 18:35 dpdklab
2023-08-01 18:33 dpdklab
2023-08-01 18:31 dpdklab
2023-08-01 18:28 dpdklab
2023-08-01 18:26 dpdklab
2023-08-01 14:24 dpdklab
2023-08-01 12:33 dpdklab
2023-08-01 12:32 dpdklab
2023-08-01 12:30 dpdklab
2023-08-01 12:17 dpdklab
2023-08-01 12:16 dpdklab
2023-08-01 12:12 dpdklab
2023-08-01 12:12 dpdklab
2023-08-01 11:55 dpdklab
2023-08-01 11:55 dpdklab
2023-08-01 11:54 dpdklab
2023-08-01 11:54 dpdklab
2023-08-01 11:54 dpdklab
2023-08-01 11:54 dpdklab
2023-08-01 11:54 dpdklab
2023-08-01 11:54 dpdklab
2023-08-01 11:54 dpdklab
2023-08-01 11:54 dpdklab
2023-08-01 5:32 dpdklab
2023-08-01 5:32 dpdklab
2023-08-01 3:48 dpdklab
2023-08-01 2:12 dpdklab
2023-08-01 2:07 dpdklab
2023-08-01 2:06 dpdklab
2023-08-01 1:57 dpdklab
2023-08-01 1:54 dpdklab
2023-08-01 1:36 dpdklab
2023-08-01 1:32 dpdklab
2023-08-01 1:23 dpdklab
2023-08-01 1:12 dpdklab
2023-08-01 1:10 dpdklab
2023-08-01 1:09 dpdklab
2023-08-01 1:09 dpdklab
2023-08-01 1:09 dpdklab
2023-08-01 1:08 dpdklab
2023-08-01 1:08 dpdklab
2023-08-01 1:08 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=64c8faeb.920a0220.42936.8219SMTPIN_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).