From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw86453 [PATCH] [v2] eal: fix errno on service cores init failure
Date: Thu, 14 Jan 2021 18:23:21 -0500 (EST) [thread overview]
Message-ID: <20210114232321.500D58903A@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2999 bytes --]
Test-Label: iol-testing
Test-Status: SUCCESS
http://dpdk.org/patch/86453
_Testing PASS_
Submitter: Olivier Matz <olivier.matz@6wind.com>
Date: Wednesday, January 13 2021 08:28:06
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:9b27a37b847237bc7b4f8369e1dad2dce3cdbb44
86453 --> testing pass
Test environment and result as below:
+---------------------+----------------------+--------------------+-------------------+----------------+
| Environment | dpdk_mingw64_compile | dpdk_meson_compile | dpdk_compile_spdk | dpdk_unit_test |
+=====================+======================+====================+===================+================+
| Windows Server 2019 | PASS | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+----------------+
| FreeBSD 11.2 | SKIPPED | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+----------------+
| Fedora 31 | SKIPPED | PASS | PASS | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+----------------+
| CentOS 8 | SKIPPED | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+----------------+
| Ubuntu 18.04 | SKIPPED | PASS | PASS | PASS |
+---------------------+----------------------+--------------------+-------------------+----------------+
| openSUSE Leap 15 | SKIPPED | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+----------------+
| Arch Linux | SKIPPED | PASS | SKIPPED | SKIPPED |
+---------------------+----------------------+--------------------+-------------------+----------------+
| Ubuntu 18.04 ARM | SKIPPED | PASS | SKIPPED | PASS |
+---------------------+----------------------+--------------------+-------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 9.0
FreeBSD 11.2
Kernel: 11.2
Compiler: gcc 8.3
Fedora 31
Kernel: 5.3.16
Compiler: gcc 9.2.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.5
openSUSE Leap 15
Kernel: 4.12.14
Compiler: gcc 7.4.1
Arch Linux
Kernel: latest
Compiler: gcc latest
Ubuntu 18.04 ARM
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/15137/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-01-14 23:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 23:23 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-01-14 23:22 dpdklab
2021-01-13 9:24 dpdklab
2021-01-13 9:12 dpdklab
2021-01-13 9:10 dpdklab
2021-01-13 9:03 dpdklab
[not found] <20210113082805.5945-1-olivier.matz@6wind.com>
2021-01-13 8:29 ` [dpdk-test-report] |SUCCESS| pw86453 [PATCH v2] " 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=20210114232321.500D58903A@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).