From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138626-138638 [PATCH] [15/15] examples: pack structures
Date: Wed, 20 Mar 2024 20:31:50 -0700 (PDT) [thread overview]
Message-ID: <65fbaa26.170a0220.574e9.fedcSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1710968771-16435-16-git-send-email-roretzla@linux.microsoft.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138638
_Functional Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wednesday, March 20 2024 21:06:11
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2
138626-138638 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29610/
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-21 3:39 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1710968771-16435-16-git-send-email-roretzla@linux.microsoft.com>
2024-03-20 20:44 ` |SUCCESS| pw138626-138638 [PATCH 15/15] examples: pack structures when building with MSVC qemudev
2024-03-20 20:49 ` qemudev
2024-03-20 21:08 ` |SUCCESS| pw138638 " checkpatch
2024-03-20 22:04 ` 0-day Robot
2024-03-21 3:12 ` |SUCCESS| pw138626-138638 [PATCH] [15/15] examples: pack structures dpdklab
2024-03-21 3:25 ` dpdklab
2024-03-21 3:25 ` dpdklab
2024-03-21 3:27 ` dpdklab
2024-03-21 3:29 ` dpdklab
2024-03-21 3:30 ` dpdklab
2024-03-21 3:31 ` dpdklab
2024-03-21 3:31 ` dpdklab
2024-03-21 3:31 ` dpdklab [this message]
2024-03-21 3:32 ` dpdklab
2024-03-21 3:33 ` dpdklab
2024-03-21 3:42 ` dpdklab
2024-03-21 3:43 ` dpdklab
2024-03-21 3:47 ` dpdklab
2024-03-21 4:43 ` dpdklab
2024-03-21 4:49 ` dpdklab
2024-03-21 5:34 ` dpdklab
2024-03-21 5:34 ` dpdklab
2024-03-21 5:39 ` dpdklab
2024-03-21 5:46 ` dpdklab
2024-03-21 5:53 ` dpdklab
2024-03-21 5:56 ` dpdklab
2024-03-21 5:57 ` dpdklab
2024-03-21 6:16 ` dpdklab
2024-03-21 6:18 ` dpdklab
2024-03-21 6:18 ` dpdklab
2024-03-21 6:20 ` dpdklab
2024-03-21 6:43 ` dpdklab
2024-03-21 6:58 ` dpdklab
2024-03-21 7:08 ` dpdklab
2024-03-21 7:08 ` dpdklab
2024-03-21 7:26 ` dpdklab
2024-03-21 7:28 ` dpdklab
2024-03-21 7:29 ` dpdklab
2024-03-21 7:29 ` dpdklab
2024-03-21 7:30 ` dpdklab
2024-03-21 7:31 ` dpdklab
2024-03-21 7:32 ` dpdklab
2024-03-21 7:33 ` dpdklab
2024-03-21 7:34 ` dpdklab
2024-03-21 7:34 ` dpdklab
2024-03-21 7:34 ` dpdklab
2024-03-21 7:34 ` dpdklab
2024-03-21 7:37 ` dpdklab
2024-03-21 7:38 ` dpdklab
2024-03-21 7:39 ` dpdklab
2024-03-21 7:39 ` dpdklab
2024-03-21 7:41 ` dpdklab
2024-03-21 7:43 ` dpdklab
2024-03-21 7:47 ` dpdklab
2024-03-21 7:49 ` dpdklab
2024-03-21 7:53 ` dpdklab
2024-03-21 7:54 ` dpdklab
2024-03-21 7:57 ` dpdklab
2024-03-21 8:17 ` dpdklab
2024-03-21 9:10 ` dpdklab
2024-03-21 9:15 ` dpdklab
2024-03-21 9:17 ` dpdklab
2024-03-21 9:20 ` dpdklab
2024-03-21 9:32 ` dpdklab
2024-03-21 9:32 ` dpdklab
2024-03-21 9:32 ` dpdklab
2024-03-21 9:47 ` dpdklab
2024-03-21 9:48 ` dpdklab
2024-03-21 9:55 ` dpdklab
2024-03-21 9:56 ` dpdklab
2024-03-21 10:14 ` dpdklab
2024-03-21 10:15 ` dpdklab
2024-03-21 10:38 ` dpdklab
2024-03-21 10:44 ` dpdklab
2024-03-21 11:18 ` dpdklab
2024-03-21 13:37 ` dpdklab
2024-03-21 13:50 ` dpdklab
2024-03-21 20:14 ` dpdklab
2024-03-22 23:03 ` dpdklab
2024-03-22 23:55 ` 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=65fbaa26.170a0220.574e9.fedcSMTPIN_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).