From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| [GIT MASTER] d3fa7b89f0b893f051cb4cef1cbc961cb59f5721
Date: Mon, 30 Nov 2020 18:15:01 -0500 (EST) [thread overview]
Message-ID: <20201130231501.6CB2A306A0@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2117 bytes --]
_Testing PASS_
Branch: dpdk
d3fa7b89f0b893f051cb4cef1cbc961cb59f5721 --> testing pass
Test environment and result as below:
+---------------------+--------------------+-------------------+----------------+
| Environment | dpdk_meson_compile | dpdk_compile_spdk | dpdk_unit_test |
+=====================+====================+===================+================+
| Windows Server 2019 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-------------------+----------------+
| FreeBSD 11.2 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-------------------+----------------+
| CentOS 8 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-------------------+----------------+
| Fedora 31 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-------------------+----------------+
| openSUSE Leap 15 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-------------------+----------------+
| Ubuntu 18.04 | PASS | PASS | PASS |
+---------------------+--------------------+-------------------+----------------+
| Arch Linux | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+-------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 9.0
FreeBSD 11.2
Kernel: 11.2
Compiler: gcc 8.3
CentOS 8
Kernel: 4.18.0.el8_0
Compiler: gcc 8.3.1
Fedora 31
Kernel: 5.3.16
Compiler: gcc 9.2.1
openSUSE Leap 15
Kernel: 4.12.14
Compiler: gcc 7.4.1
Ubuntu 18.04
Kernel: 4.15.0-generic
Compiler: gcc 7.5
Arch Linux
Kernel: latest
Compiler: gcc latest
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/12811/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2020-11-30 23:15 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 23:15 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-02 0:51 dpdklab
2020-12-02 0:42 dpdklab
2020-12-02 0:35 dpdklab
2020-12-02 0:34 dpdklab
2020-12-02 0:29 dpdklab
2020-12-01 16:38 dpdklab
2020-12-01 15:45 dpdklab
2020-12-01 15:44 dpdklab
2020-12-01 15:41 dpdklab
2020-12-01 15:39 dpdklab
2020-12-01 15:34 dpdklab
2020-12-01 15:03 dpdklab
2020-12-01 12:38 dpdklab
2020-12-01 12:28 dpdklab
2020-12-01 12:23 dpdklab
2020-12-01 12:19 dpdklab
2020-12-01 12:14 dpdklab
2020-12-01 0:10 dpdklab
2020-11-30 23:31 dpdklab
2020-11-30 23:19 dpdklab
2020-11-30 23:03 dpdklab
2020-11-30 22:56 dpdklab
2020-11-30 22:29 dpdklab
2020-11-30 22:13 dpdklab
2020-11-30 22:04 dpdklab
2020-11-30 21:59 dpdklab
2020-11-30 21:55 dpdklab
2020-11-30 21:50 dpdklab
2020-11-30 21:06 dpdklab
2020-11-30 20:49 dpdklab
2020-11-30 20:39 dpdklab
2020-11-30 20:36 dpdklab
2020-11-30 20:31 dpdklab
2020-11-30 20:24 dpdklab
2020-11-30 20:02 dpdklab
2020-11-30 19:45 dpdklab
2020-11-30 19:36 dpdklab
2020-11-30 19:32 dpdklab
2020-11-30 19:28 dpdklab
2020-11-30 19:23 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=20201130231501.6CB2A306A0@noxus.dpdklab.iol.unh.edu \
--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).