From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136472 [PATCH] doc: remove cmdline deprecation notice
Date: Wed, 07 Feb 2024 03:54:40 -0800 (PST) [thread overview]
Message-ID: <65c36f80.c80a0220.ddb66.1c41SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136472
_Testing PASS_
Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Wednesday, February 07 2024 11:09:34
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a4ce111cc89f580b8c4aad51bdb061acbdfde86b
136472 --> 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 |
+--------------------------+---------------------------+------------------------------+----------------+
| CentOS Stream 9 (ARM) | SKIPPED | SKIPPED | PASS |
+--------------------------+---------------------------+------------------------------+----------------+
| Debian 11 (Buster) (ARM) | SKIPPED | SKIPPED | PASS |
+--------------------------+---------------------------+------------------------------+----------------+
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29077/
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-07 11:54 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 11:54 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-07 13:34 dpdklab
2024-02-07 13:08 dpdklab
2024-02-07 13:06 dpdklab
2024-02-07 12:15 dpdklab
2024-02-07 12:12 dpdklab
2024-02-07 12:10 dpdklab
2024-02-07 12:06 dpdklab
2024-02-07 12:06 dpdklab
2024-02-07 12:05 dpdklab
2024-02-07 12:05 dpdklab
2024-02-07 12:03 dpdklab
2024-02-07 12:02 dpdklab
2024-02-07 12:02 dpdklab
2024-02-07 12:00 dpdklab
2024-02-07 12:00 dpdklab
2024-02-07 12:00 dpdklab
2024-02-07 12:00 dpdklab
2024-02-07 12:00 dpdklab
2024-02-07 12:00 dpdklab
2024-02-07 12:00 dpdklab
2024-02-07 11:59 dpdklab
2024-02-07 11:59 dpdklab
2024-02-07 11:59 dpdklab
2024-02-07 11:59 dpdklab
2024-02-07 11:59 dpdklab
2024-02-07 11:59 dpdklab
2024-02-07 11:58 dpdklab
2024-02-07 11:58 dpdklab
2024-02-07 11:58 dpdklab
2024-02-07 11:58 dpdklab
2024-02-07 11:57 dpdklab
2024-02-07 11:57 dpdklab
2024-02-07 11:57 dpdklab
2024-02-07 11:57 dpdklab
2024-02-07 11:57 dpdklab
2024-02-07 11:57 dpdklab
2024-02-07 11:56 dpdklab
2024-02-07 11:56 dpdklab
2024-02-07 11:56 dpdklab
2024-02-07 11:56 dpdklab
2024-02-07 11:56 dpdklab
2024-02-07 11:55 dpdklab
2024-02-07 11:55 dpdklab
2024-02-07 11:55 dpdklab
2024-02-07 11:55 dpdklab
2024-02-07 11:55 dpdklab
2024-02-07 11:54 dpdklab
2024-02-07 11:54 dpdklab
2024-02-07 11:53 dpdklab
2024-02-07 11:53 dpdklab
2024-02-07 11:53 dpdklab
2024-02-07 11:53 dpdklab
2024-02-07 11:52 dpdklab
2024-02-07 11:52 dpdklab
2024-02-07 11:52 dpdklab
2024-02-07 11:52 dpdklab
2024-02-07 11:52 dpdklab
2024-02-07 11:51 dpdklab
2024-02-07 11:51 dpdklab
2024-02-07 11:51 dpdklab
2024-02-07 11:50 dpdklab
2024-02-07 11:50 dpdklab
2024-02-07 11:49 dpdklab
2024-02-07 11:48 dpdklab
[not found] <20240207110934.2350346-1-dsosnowski@nvidia.com>
2024-02-07 10:53 ` qemudev
2024-02-07 10:58 ` qemudev
2024-02-07 11:10 ` checkpatch
2024-02-07 12:04 ` 0-day Robot
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=65c36f80.c80a0220.ddb66.1c41SMTPIN_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).