From: dpdklab@iol.unh.edu
To: Ali Alnubani <alialnu@nvidia.com>, Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw86639 [PATCH] [v2] eal/rwlock: add note about writer starvation
Date: Sat, 16 Jan 2021 03:52:48 -0500 (EST) [thread overview]
Message-ID: <20210116085248.E482C8903A@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 906 bytes --]
Test-Label: iol-mellanox-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/86639
_Functional Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, January 14 2021 16:55:56
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6e4d4a6381c47cfe6d75225945b3f6a5f8453214
86639 --> functional testing pass
Test environment and result as below:
Ubuntu 18.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Mellanox ConnectX-4 Lx 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/5
Ubuntu 18.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Mellanox ConnectX-4 Lx 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/5
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/15204/
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-16 8:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 8:52 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-01-18 9:11 dpdklab
2021-01-18 9:11 dpdklab
2021-01-18 8:24 dpdklab
2021-01-17 3:28 dpdklab
2021-01-17 2:15 dpdklab
2021-01-16 7:37 dpdklab
2021-01-15 10:59 dpdklab
2021-01-15 10:35 dpdklab
2021-01-15 7:30 dpdklab
2021-01-15 7:06 dpdklab
2021-01-14 21:39 dpdklab
2021-01-14 21:04 dpdklab
[not found] <20210114165556.31353-1-stephen@networkplumber.org>
2021-01-14 16:57 ` [dpdk-test-report] |SUCCESS| pw86639 [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=20210116085248.E482C8903A@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=alialnu@nvidia.com \
--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).