From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138055-138060 [PATCH] [v5,6/6] table: replace zero lengt
Date: Wed, 06 Mar 2024 13:14:06 -0800 (PST) [thread overview]
Message-ID: <65e8dc9e.050a0220.dd37b.1ff9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1709756036-24068-7-git-send-email-roretzla@linux.microsoft.com>
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138060
_Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wednesday, March 06 2024 20:13:56
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:dd329b2cc53dd61156b0227b0b858f9b17215574
138055-138060 --> testing pass
Test environment and result as below:
+----------------------+--------------------+
| Environment | dpdk_meson_compile |
+======================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------+--------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29443/
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-06 21:14 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1709756036-24068-7-git-send-email-roretzla@linux.microsoft.com>
2024-03-06 19:52 ` |SUCCESS| pw138055-138060 [PATCH v5 6/6] table: replace zero length array with flex array qemudev
2024-03-06 19:56 ` qemudev
2024-03-06 20:14 ` |SUCCESS| pw138060 " checkpatch
2024-03-06 21:05 ` 0-day Robot
2024-03-06 21:06 ` |SUCCESS| pw138055-138060 [PATCH] [v5,6/6] table: replace zero lengt dpdklab
2024-03-06 21:07 ` dpdklab
2024-03-06 21:07 ` dpdklab
2024-03-06 21:08 ` dpdklab
2024-03-06 21:08 ` dpdklab
2024-03-06 21:09 ` dpdklab
2024-03-06 21:09 ` dpdklab
2024-03-06 21:10 ` dpdklab
2024-03-06 21:12 ` dpdklab
2024-03-06 21:12 ` dpdklab
2024-03-06 21:12 ` dpdklab
2024-03-06 21:12 ` dpdklab
2024-03-06 21:13 ` dpdklab
2024-03-06 21:14 ` dpdklab [this message]
2024-03-06 21:14 ` dpdklab
2024-03-06 21:14 ` dpdklab
2024-03-06 21:15 ` dpdklab
2024-03-06 21:15 ` dpdklab
2024-03-06 21:15 ` dpdklab
2024-03-06 21:16 ` dpdklab
2024-03-06 21:18 ` dpdklab
2024-03-06 21:18 ` dpdklab
2024-03-06 21:19 ` dpdklab
2024-03-06 21:19 ` dpdklab
2024-03-06 21:19 ` dpdklab
2024-03-06 21:20 ` dpdklab
2024-03-06 21:20 ` dpdklab
2024-03-06 21:23 ` dpdklab
2024-03-06 21:24 ` dpdklab
2024-03-06 21:27 ` dpdklab
2024-03-06 21:27 ` dpdklab
2024-03-06 21:27 ` dpdklab
2024-03-06 21:29 ` dpdklab
2024-03-06 21:30 ` dpdklab
2024-03-06 21:30 ` dpdklab
2024-03-06 21:31 ` dpdklab
2024-03-06 21:31 ` dpdklab
2024-03-06 21:35 ` dpdklab
2024-03-06 21:36 ` dpdklab
2024-03-06 21:38 ` dpdklab
2024-03-06 21:39 ` dpdklab
2024-03-06 21:39 ` dpdklab
2024-03-06 21:40 ` dpdklab
2024-03-06 21:42 ` dpdklab
2024-03-06 21:42 ` dpdklab
2024-03-06 21:43 ` dpdklab
2024-03-06 21:44 ` dpdklab
2024-03-06 21:44 ` dpdklab
2024-03-06 21:46 ` dpdklab
2024-03-06 21:49 ` dpdklab
2024-03-06 21:49 ` dpdklab
2024-03-06 22:01 ` dpdklab
2024-03-06 22:02 ` dpdklab
2024-03-06 22:03 ` dpdklab
2024-03-06 22:04 ` dpdklab
2024-03-06 22:10 ` dpdklab
2024-03-06 22:22 ` dpdklab
2024-03-06 22:22 ` dpdklab
2024-03-06 22:37 ` dpdklab
2024-03-06 22:38 ` dpdklab
2024-03-06 22:40 ` dpdklab
2024-03-06 22:41 ` dpdklab
2024-03-06 22:56 ` dpdklab
2024-03-06 23:11 ` dpdklab
2024-03-07 0:28 ` dpdklab
2024-03-07 2:15 ` dpdklab
2024-03-07 23:51 ` dpdklab
2024-03-07 23:54 ` dpdklab
2024-03-07 23:59 ` dpdklab
2024-03-08 0: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=65e8dc9e.050a0220.dd37b.1ff9SMTPIN_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).