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| pw91957 [PATCH] pipeline: prevent some compiler warnings
Date: Sat, 24 Apr 2021 17:14:23 -0400 (EDT) [thread overview]
Message-ID: <20210424211423.EB05E3062F@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 911 bytes --]
Test-Label: iol-mellanox-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/91957
_Functional Testing PASS_
Submitter: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
Date: Wednesday, April 21 2021 13:57:44
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:ff4cf5265cc9dfdf41eabaded8617f73afb1283e
91957 --> 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/16698/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-04-24 21:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-24 21:14 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-24 17:45 dpdklab
2021-04-23 20:06 dpdklab
2021-04-23 18:22 dpdklab
2021-04-22 4:32 dpdklab
2021-04-22 3:40 dpdklab
2021-04-22 3:34 dpdklab
2021-04-22 2:27 dpdklab
2021-04-21 20:55 dpdklab
2021-04-21 20:06 dpdklab
[not found] <20210421135744.21114-1-cristian.dumitrescu@intel.com>
2021-04-21 13:58 ` 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=20210424211423.EB05E3062F@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).