From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] 68453e54f42c392520a9cbf5c3be4198272ca507
Date: Thu, 02 Nov 2023 11:52:07 -0700 (PDT) [thread overview]
Message-ID: <6543efd7.630a0220.c330e.0821SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Testing PASS_
Branch: dpdk-next-virtio
68453e54f42c392520a9cbf5c3be4198272ca507 --> testing pass
Test environment and result as below:
+-----------------+----------------+
| Environment | dpdk_unit_test |
+=================+================+
| CentOS Stream 9 | PASS |
+-----------------+----------------+
| CentOS Stream 8 | PASS |
+-----------------+----------------+
| Debian Buster | PASS |
+-----------------+----------------+
| Fedora 38 | PASS |
+-----------------+----------------+
| Debian Bullseye | PASS |
+-----------------+----------------+
| Fedora 37 | PASS |
+-----------------+----------------+
| RHEL8 | PASS |
+-----------------+----------------+
| Ubuntu 20.04 | PASS |
+-----------------+----------------+
| Ubuntu 22.04 | PASS |
+-----------------+----------------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/26792/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-02 18:52 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 18:52 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-03 2:12 dpdklab
2023-11-02 20:16 dpdklab
2023-11-02 19:54 dpdklab
2023-11-02 19:26 dpdklab
2023-11-02 19:19 dpdklab
2023-11-02 19:11 dpdklab
2023-11-02 19:10 dpdklab
2023-11-02 19:09 dpdklab
2023-11-02 19:03 dpdklab
2023-11-02 19:03 dpdklab
2023-11-02 19:01 dpdklab
2023-11-02 18:59 dpdklab
2023-11-02 18:58 dpdklab
2023-11-02 18:58 dpdklab
2023-11-02 18:58 dpdklab
2023-11-02 18:57 dpdklab
2023-11-02 18:57 dpdklab
2023-11-02 18:57 dpdklab
2023-11-02 18:57 dpdklab
2023-11-02 18:56 dpdklab
2023-11-02 18:56 dpdklab
2023-11-02 18:56 dpdklab
2023-11-02 18:55 dpdklab
2023-11-02 18:55 dpdklab
2023-11-02 18:55 dpdklab
2023-11-02 18:55 dpdklab
2023-11-02 18:55 dpdklab
2023-11-02 18:55 dpdklab
2023-11-02 18:55 dpdklab
2023-11-02 18:55 dpdklab
2023-11-02 18:55 dpdklab
2023-11-02 18:54 dpdklab
2023-11-02 18:54 dpdklab
2023-11-02 18:53 dpdklab
2023-11-02 18:53 dpdklab
2023-11-02 18:53 dpdklab
2023-11-02 18:39 dpdklab
2023-11-02 18:38 dpdklab
2023-11-02 18:33 dpdklab
2023-11-02 18:23 dpdklab
2023-11-02 18:07 dpdklab
2023-11-02 18:02 dpdklab
2023-11-02 17:59 dpdklab
2023-11-02 17:55 dpdklab
2023-11-02 17:35 dpdklab
2023-11-02 17:31 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=6543efd7.630a0220.c330e.0821SMTPIN_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).