From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136676-136675 [PATCH] [v3,3/3] eal: remove typeof from p
Date: Tue, 13 Feb 2024 16:19:55 -0800 (PST) [thread overview]
Message-ID: <65cc072b.6b0a0220.95cd3.283cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136675
_Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Tuesday, February 13 2024 19:12:03
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:31d72ff4dc7c057366153e9918ac92bf9123a3bc
136676-136675 --> testing pass
Test environment and result as below:
+--------------------------+---------------------------+------------------------------+----------------+
| Environment | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest | dpdk_unit_test |
+==========================+===========================+==============================+================+
| Debian 11 (arm) | PASS | PASS | SKIPPED |
+--------------------------+---------------------------+------------------------------+----------------+
| Debian 11 (Buster) (ARM) | SKIPPED | SKIPPED | PASS |
+--------------------------+---------------------------+------------------------------+----------------+
| CentOS Stream 9 (ARM) | SKIPPED | SKIPPED | PASS |
+--------------------------+---------------------------+------------------------------+----------------+
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29140/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-14 0:19 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 0:19 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-14 5:28 dpdklab
2024-02-14 3:08 dpdklab
2024-02-14 2:42 dpdklab
2024-02-14 2:42 dpdklab
2024-02-14 2:41 dpdklab
2024-02-14 2:39 dpdklab
2024-02-14 2:38 dpdklab
2024-02-14 2:38 dpdklab
2024-02-14 2:35 dpdklab
2024-02-14 2:07 dpdklab
2024-02-14 1:52 dpdklab
2024-02-14 1:52 dpdklab
2024-02-14 1:51 dpdklab
2024-02-14 1:50 dpdklab
2024-02-14 1:50 dpdklab
2024-02-14 1:49 dpdklab
2024-02-14 1:43 dpdklab
2024-02-14 1:39 dpdklab
2024-02-14 1:39 dpdklab
2024-02-14 1:38 dpdklab
2024-02-14 1:38 dpdklab
2024-02-14 1:36 dpdklab
2024-02-14 1:34 dpdklab
2024-02-14 1:31 dpdklab
2024-02-14 1:30 dpdklab
2024-02-14 1:29 dpdklab
2024-02-14 1:28 dpdklab
2024-02-14 1:27 dpdklab
2024-02-14 1:26 dpdklab
2024-02-14 1:25 dpdklab
2024-02-14 1:24 dpdklab
2024-02-14 1:23 dpdklab
2024-02-14 1:23 dpdklab
2024-02-14 1:22 dpdklab
2024-02-14 1:07 dpdklab
2024-02-14 0:53 dpdklab
2024-02-14 0:50 dpdklab
2024-02-14 0:50 dpdklab
2024-02-14 0:48 dpdklab
2024-02-14 0:47 dpdklab
2024-02-14 0:46 dpdklab
2024-02-14 0:46 dpdklab
2024-02-14 0:45 dpdklab
2024-02-14 0:41 dpdklab
2024-02-14 0:40 dpdklab
2024-02-14 0:39 dpdklab
2024-02-14 0:39 dpdklab
2024-02-14 0:38 dpdklab
2024-02-14 0:36 dpdklab
2024-02-14 0:36 dpdklab
2024-02-14 0:29 dpdklab
2024-02-14 0:28 dpdklab
2024-02-14 0:26 dpdklab
2024-02-14 0:24 dpdklab
2024-02-14 0:23 dpdklab
2024-02-14 0:22 dpdklab
2024-02-14 0:18 dpdklab
2024-02-14 0:17 dpdklab
2024-02-14 0:12 dpdklab
2024-02-14 0:11 dpdklab
2024-02-13 23:46 dpdklab
2024-02-13 23:46 dpdklab
2024-02-13 23:45 dpdklab
2024-02-13 23:41 dpdklab
2024-02-13 23:39 dpdklab
2024-02-13 23:39 dpdklab
2024-02-13 23:37 dpdklab
2024-02-13 23:36 dpdklab
2024-02-13 23:34 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=65cc072b.6b0a0220.95cd3.283cSMTPIN_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).