From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138071 [PATCH] [v1,1/1] lib: allow libraries with no sou
Date: Wed, 06 Mar 2024 19:07:34 -0800 (PST) [thread overview]
Message-ID: <65e92f76.050a0220.68787.9b7dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240306221709.166722-2-paul.szczepanek@arm.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138071
_Functional Testing PASS_
Submitter: Paul Szczepanek <paul.szczepanek@arm.com>
Date: Wednesday, March 06 2024 22:17:09
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2a454f84f715608ee709a4c6ba00edf2e4b62b69
138071 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29447/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-07 3:07 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240306221709.166722-2-paul.szczepanek@arm.com>
2024-03-06 21:56 ` |SUCCESS| pw138071 [PATCH v1 1/1] lib: allow libraries with no sources qemudev
2024-03-06 22:00 ` qemudev
2024-03-06 22:17 ` checkpatch
2024-03-06 23:04 ` 0-day Robot
2024-03-07 2:39 ` |SUCCESS| pw138071 [PATCH] [v1,1/1] lib: allow libraries with no sou dpdklab
2024-03-07 2:49 ` dpdklab
2024-03-07 2:53 ` dpdklab
2024-03-07 2:58 ` dpdklab
2024-03-07 3:06 ` dpdklab
2024-03-07 3:06 ` dpdklab
2024-03-07 3:06 ` dpdklab
2024-03-07 3:07 ` dpdklab
2024-03-07 3:07 ` dpdklab [this message]
2024-03-07 3:07 ` dpdklab
2024-03-07 3:08 ` dpdklab
2024-03-07 3:08 ` dpdklab
2024-03-07 3:09 ` dpdklab
2024-03-07 3:10 ` dpdklab
2024-03-07 3:10 ` dpdklab
2024-03-07 3:11 ` dpdklab
2024-03-07 3:11 ` dpdklab
2024-03-07 3:11 ` dpdklab
2024-03-07 3:11 ` dpdklab
2024-03-07 3:11 ` dpdklab
2024-03-07 3:11 ` dpdklab
2024-03-07 3:12 ` dpdklab
2024-03-07 3:13 ` dpdklab
2024-03-07 3:13 ` dpdklab
2024-03-07 3:13 ` dpdklab
2024-03-07 3:13 ` dpdklab
2024-03-07 3:13 ` dpdklab
2024-03-07 3:13 ` dpdklab
2024-03-07 3:14 ` dpdklab
2024-03-07 3:14 ` dpdklab
2024-03-07 3:14 ` dpdklab
2024-03-07 3:14 ` dpdklab
2024-03-07 3:15 ` dpdklab
2024-03-07 3:15 ` dpdklab
2024-03-07 3:15 ` dpdklab
2024-03-07 3:15 ` dpdklab
2024-03-07 3:16 ` dpdklab
2024-03-07 3:16 ` dpdklab
2024-03-07 3:16 ` dpdklab
2024-03-07 3:17 ` dpdklab
2024-03-07 3:17 ` dpdklab
2024-03-07 3:17 ` dpdklab
2024-03-07 3:17 ` dpdklab
2024-03-07 3:17 ` dpdklab
2024-03-07 3:29 ` dpdklab
2024-03-07 3:29 ` dpdklab
2024-03-07 3:30 ` dpdklab
2024-03-07 3:30 ` dpdklab
2024-03-07 3:30 ` dpdklab
2024-03-07 3:30 ` dpdklab
2024-03-07 3:31 ` dpdklab
2024-03-07 3:31 ` dpdklab
2024-03-07 3:31 ` dpdklab
2024-03-07 3:31 ` dpdklab
2024-03-07 3:32 ` dpdklab
2024-03-07 3:32 ` dpdklab
2024-03-07 3:32 ` dpdklab
2024-03-07 3:33 ` dpdklab
2024-03-07 3:33 ` dpdklab
2024-03-07 3:33 ` dpdklab
2024-03-07 3:44 ` dpdklab
2024-03-07 4:00 ` dpdklab
2024-03-07 4:21 ` dpdklab
2024-03-07 4:45 ` dpdklab
2024-03-08 0:50 ` dpdklab
2024-03-08 0:54 ` dpdklab
2024-03-08 0:59 ` dpdklab
2024-03-08 1:03 ` 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=65e92f76.050a0220.68787.9b7dSMTPIN_ADDED_MISSING@mx.google.com \
--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).