From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu
Subject: |SUCCESS| [GIT MASTER] d3db37893eeeb17b4f3f96eea072077c0fc537d1
Date: Mon, 21 Feb 2022 12:31:10 +0000 (UTC) [thread overview]
Message-ID: <20220221123110.B2577601B6@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
_Testing PASS_
Branch: dpdk-next-eventdev
d3db37893eeeb17b4f3f96eea072077c0fc537d1 --> testing pass
Test environment and result as below:
+-----------------+----------------+
| Environment | dpdk_unit_test |
+=================+================+
| CentOS 8 | PASS |
+-----------------+----------------+
| Ubuntu 18.04 | PASS |
+-----------------+----------------+
| Fedora 34 clang | PASS |
+-----------------+----------------+
CentOS 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Ubuntu 18.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0-3ubuntu1~18.04
Fedora 34 clang
Kernel: 5.4.0-72-generic
Compiler: clang 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/18811/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-02-21 12:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 12:31 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-21 15:53 dpdklab
2022-02-21 15:42 dpdklab
2022-02-21 15:34 dpdklab
2022-02-21 15:31 dpdklab
2022-02-21 14:05 dpdklab
2022-02-21 14:01 dpdklab
2022-02-21 12:35 dpdklab
2022-02-21 12:32 dpdklab
2022-02-21 12:31 dpdklab
2022-02-21 12:31 dpdklab
2022-02-21 12:31 dpdklab
2022-02-21 12:30 dpdklab
2022-02-21 12:26 dpdklab
2022-02-21 12:25 dpdklab
2022-02-21 12:24 dpdklab
2022-02-21 12:20 dpdklab
2022-02-21 12:19 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=20220221123110.B2577601B6@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@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).