From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138128 [PATCH] add a ignore list for get_maintainer
Date: Fri, 08 Mar 2024 09:40:55 -0800 (PST) [thread overview]
Message-ID: <65eb4da7.170a0220.9870c.b104SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240308170717.8677-1-stephen@networkplumber.org>
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138128
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Friday, March 08 2024 17:07:17
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a86f381b826660e88794754c41d3aec79ce9b87c
138128 --> testing pass
Test environment and result as below:
+--------------------------+------------------------------+---------------------------+----------------+
| Environment | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest | dpdk_unit_test |
+==========================+==============================+===========================+================+
| Debian 12 (arm) | PASS | PASS | PASS |
+--------------------------+------------------------------+---------------------------+----------------+
| Debian 11 (Buster) (ARM) | SKIPPED | SKIPPED | PASS |
+--------------------------+------------------------------+---------------------------+----------------+
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
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/29480/
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-08 17:40 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240308170717.8677-1-stephen@networkplumber.org>
2024-03-08 16:44 ` qemudev
2024-03-08 16:48 ` qemudev
2024-03-08 17:08 ` |WARNING| " checkpatch
2024-03-08 17:39 ` |SUCCESS| " dpdklab
2024-03-08 17:40 ` dpdklab
2024-03-08 17:40 ` dpdklab
2024-03-08 17:40 ` dpdklab [this message]
2024-03-08 17:40 ` dpdklab
2024-03-08 17:41 ` dpdklab
2024-03-08 17:41 ` dpdklab
2024-03-08 17:41 ` dpdklab
2024-03-08 17:42 ` dpdklab
2024-03-08 17:42 ` dpdklab
2024-03-08 17:43 ` dpdklab
2024-03-08 17:43 ` dpdklab
2024-03-08 17:43 ` dpdklab
2024-03-08 17:44 ` dpdklab
2024-03-08 17:44 ` dpdklab
2024-03-08 17:44 ` dpdklab
2024-03-08 17:44 ` dpdklab
2024-03-08 17:44 ` dpdklab
2024-03-08 17:45 ` dpdklab
2024-03-08 17:45 ` dpdklab
2024-03-08 17:45 ` dpdklab
2024-03-08 17:46 ` dpdklab
2024-03-08 17:46 ` dpdklab
2024-03-08 17:46 ` dpdklab
2024-03-08 17:46 ` dpdklab
2024-03-08 17:46 ` dpdklab
2024-03-08 17:46 ` dpdklab
2024-03-08 17:46 ` dpdklab
2024-03-08 17:47 ` dpdklab
2024-03-08 17:47 ` dpdklab
2024-03-08 17:47 ` dpdklab
2024-03-08 17:48 ` dpdklab
2024-03-08 17:48 ` dpdklab
2024-03-08 17:48 ` dpdklab
2024-03-08 17:48 ` dpdklab
2024-03-08 17:48 ` dpdklab
2024-03-08 17:48 ` dpdklab
2024-03-08 17:49 ` dpdklab
2024-03-08 17:49 ` dpdklab
2024-03-08 17:49 ` dpdklab
2024-03-08 17:49 ` dpdklab
2024-03-08 17:49 ` dpdklab
2024-03-08 17:49 ` dpdklab
2024-03-08 17:49 ` dpdklab
2024-03-08 17:50 ` dpdklab
2024-03-08 17:51 ` dpdklab
2024-03-08 17:52 ` dpdklab
2024-03-08 17:52 ` dpdklab
2024-03-08 17:52 ` dpdklab
2024-03-08 17:54 ` dpdklab
2024-03-08 17:54 ` dpdklab
2024-03-08 17:54 ` dpdklab
2024-03-08 17:55 ` dpdklab
2024-03-08 17:55 ` dpdklab
2024-03-08 17:55 ` dpdklab
2024-03-08 17:57 ` dpdklab
2024-03-08 17:57 ` dpdklab
2024-03-08 17:58 ` dpdklab
2024-03-08 17:59 ` dpdklab
2024-03-08 18:00 ` dpdklab
2024-03-08 18:01 ` dpdklab
2024-03-08 18:06 ` dpdklab
2024-03-08 18:06 ` 0-day Robot
2024-03-08 18:08 ` dpdklab
2024-03-08 18:56 ` dpdklab
2024-03-08 20:32 ` dpdklab
2024-03-13 9:08 ` dpdklab
2024-03-13 9:57 ` 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=65eb4da7.170a0220.9870c.b104SMTPIN_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).