From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw110564 [PATCH] [v2] lib/eal/ppc fix compilation for musl
Date: Mon, 2 May 2022 10:51:49 -0400 (EDT) [thread overview]
Message-ID: <20220502145149.2EFFF4DA@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 796 bytes --]
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/110564
_Functional Testing PASS_
Submitter: Duncan Bellamy <dunk@denkimushi.com>
Date: Monday, May 02 2022 14:26:15
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:90bf3f89ed33f78e9f41818caf123e13e508dee7
110564 --> 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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/21982/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-05-02 14:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 14:51 dpdklab [this message]
2022-05-02 15:01 dpdklab
2022-05-02 15:03 dpdklab
2022-05-02 15:08 dpdklab
2022-05-02 15:19 dpdklab
2022-05-02 15:28 dpdklab
2022-05-02 17:17 dpdklab
2022-05-02 17:24 dpdklab
2022-05-02 17:26 dpdklab
2022-05-02 17:28 dpdklab
2022-05-02 17:41 dpdklab
2022-05-02 18:33 dpdklab
2022-05-06 17:44 dpdklab
2022-05-06 18:11 dpdklab
2022-05-06 18:46 dpdklab
2022-05-06 19:01 dpdklab
2022-05-06 19:15 dpdklab
2022-05-06 19:48 dpdklab
2022-05-06 23:55 dpdklab
2022-05-07 2:50 dpdklab
2022-05-07 18:06 dpdklab
2022-05-08 1:16 dpdklab
2022-05-08 8:49 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=20220502145149.2EFFF4DA@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).