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| pw125936-125948 [PATCH] [v4, 14/14] eal: always define MSVC as little endian
Date: Tue, 11 Apr 2023 22:14:57 +0000 (UTC) [thread overview]
Message-ID: <20230411221457.CBE6E60092@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/125948
_Functional Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Tuesday, April 11 2023 21:12:28
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:65487b12db83c9ef37526a983c43191cd44dae99
125936-125948 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25961/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-04-11 22:15 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 22:14 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-12 16:47 dpdklab
2023-04-12 16:42 dpdklab
2023-04-12 16:38 dpdklab
2023-04-12 16:37 dpdklab
2023-04-12 16:35 dpdklab
2023-04-12 16:30 dpdklab
2023-04-12 16:30 dpdklab
2023-04-12 16:27 dpdklab
2023-04-12 16:18 dpdklab
2023-04-12 16:17 dpdklab
2023-04-12 16:13 dpdklab
2023-04-12 16:08 dpdklab
2023-04-12 16:05 dpdklab
2023-04-12 16:02 dpdklab
2023-04-12 16:01 dpdklab
2023-04-12 16:01 dpdklab
2023-04-12 15:59 dpdklab
2023-04-12 15:58 dpdklab
2023-04-12 15:58 dpdklab
2023-04-12 15:52 dpdklab
2023-04-12 15:24 dpdklab
2023-04-12 15:19 dpdklab
2023-04-12 15:15 dpdklab
2023-04-12 15:00 dpdklab
2023-04-12 14:55 dpdklab
2023-04-12 14:50 dpdklab
2023-04-12 1:13 dpdklab
2023-04-12 1:12 dpdklab
2023-04-12 0:55 dpdklab
2023-04-12 0:42 dpdklab
2023-04-12 0:42 dpdklab
2023-04-12 0:19 dpdklab
2023-04-12 0:15 dpdklab
2023-04-11 23:44 dpdklab
2023-04-11 23:37 dpdklab
2023-04-11 23:34 dpdklab
2023-04-11 23:32 dpdklab
2023-04-11 23:30 dpdklab
2023-04-11 23:22 dpdklab
2023-04-11 23:15 dpdklab
2023-04-11 23:14 dpdklab
2023-04-11 23:09 dpdklab
2023-04-11 23:01 dpdklab
2023-04-11 22:53 dpdklab
2023-04-11 22:50 dpdklab
2023-04-11 22:41 dpdklab
2023-04-11 22:40 dpdklab
2023-04-11 22:39 dpdklab
2023-04-11 22:33 dpdklab
2023-04-11 22:32 dpdklab
2023-04-11 22:27 dpdklab
2023-04-11 22:25 dpdklab
2023-04-11 22:24 dpdklab
2023-04-11 22:17 dpdklab
2023-04-11 22:11 dpdklab
2023-04-11 22:09 dpdklab
2023-04-11 22:06 dpdklab
[not found] <1681247548-18590-15-git-send-email-roretzla@linux.microsoft.com>
2023-04-11 21:07 ` |SUCCESS| pw125936-125948 [PATCH v4 " qemudev
2023-04-11 21:11 ` qemudev
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=20230411221457.CBE6E60092@dpdk-ubuntu.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).