From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw67706 [PATCH] [v1, 1/1] net/octeontx2: add routines to set/clear interrupt enable registers
Date: Mon, 6 Apr 2020 13:38:26 -0400 (EDT) [thread overview]
Message-ID: <20200406173826.71A3D6D4D7@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2916 bytes --]
Test-Label: iol-testing
Test-Status: SUCCESS
http://dpdk.org/patch/67706
_Testing PASS_
Submitter: Vamsi Krishna Attunuru <vattunuru@marvell.com>
Date: Friday, April 03 2020 02:20:16
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:10c69730a4b4910b4d57c365329a6c26479d25cd
67706 --> testing pass
Test environment and result as below:
+---------------------+------------------+--------------+--------------------+-------------------+----------------+
| Environment | dpdk_compile_ovs | dpdk_compile | dpdk_meson_compile | dpdk_compile_spdk | dpdk_unit_test |
+=====================+==================+==============+====================+===================+================+
| openSUSE Leap 15 | PASS | PASS | PASS | PASS | SKIPPED |
+---------------------+------------------+--------------+--------------------+-------------------+----------------+
| CentOS 8 | PASS | PASS | PASS | PASS | SKIPPED |
+---------------------+------------------+--------------+--------------------+-------------------+----------------+
| Ubuntu 18.04 | PASS | PASS | PASS | PASS | PASS |
+---------------------+------------------+--------------+--------------------+-------------------+----------------+
| Fedora 31 | PASS | PASS | PASS | PASS | SKIPPED |
+---------------------+------------------+--------------+--------------------+-------------------+----------------+
| Arch Linux | PASS | PASS | PASS | SKIPPED | SKIPPED |
+---------------------+------------------+--------------+--------------------+-------------------+----------------+
| FreeBSD 11.2 | SKIPPED | PASS | PASS | PASS | SKIPPED |
+---------------------+------------------+--------------+--------------------+-------------------+----------------+
| Windows Server 2019 | SKIPPED | SKIPPED | PASS | SKIPPED | SKIPPED |
+---------------------+------------------+--------------+--------------------+-------------------+----------------+
openSUSE Leap 15
Kernel: 4.12.14
Compiler: gcc 7.4.1
CentOS 8
Kernel: 4.18.0.el8_0
Compiler: gcc 8.3.1
Ubuntu 18.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
Fedora 31
Kernel: 5.3.16
Compiler: gcc 9.2.1
Arch Linux
Kernel: latest
Compiler: gcc latest
FreeBSD 11.2
Kernel: 11.2
Compiler: gcc 8.3
Windows Server 2019
Kernel: 10.0
Compiler: clang 9.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/10239/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2020-04-06 17:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 17:38 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-03 3:21 dpdklab
2020-04-03 3:10 dpdklab
2020-04-03 3:10 dpdklab
[not found] <20200403022016.2676-1-vattunuru@marvell.com>
2020-04-03 2:21 ` [dpdk-test-report] |SUCCESS| pw67706 [PATCH] [v1 " checkpatch
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=20200406173826.71A3D6D4D7@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).