From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136562-136567 [PATCH] [v4,7/7] MAINTAINERS: add maintain
Date: Thu, 08 Feb 2024 15:46:27 -0800 (PST) [thread overview]
Message-ID: <65c567d3.050a0220.8976b.1132SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136567
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, February 08 2024 19:05:55
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6e4dc4ffef11af54fd21faf1a258d8566dc4fcee
136562-136567 --> testing pass
Test environment and result as below:
+--------------------------+----------------+---------------------------+
| Environment | dpdk_unit_test | cryptodev_sw_zuc_autotest |
+==========================+================+===========================+
| CentOS Stream 9 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+---------------------------+
| Fedora 38 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+---------------------------+
| Debian 11 (Buster) (ARM) | PASS | SKIPPED |
+--------------------------+----------------+---------------------------+
| Fedora 37 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+---------------------------+
| Debian 11 (arm) | SKIPPED | PASS |
+--------------------------+----------------+---------------------------+
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29101/
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-08 23:46 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 23:46 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-09 3:20 dpdklab
2024-02-09 2:57 dpdklab
2024-02-09 2:46 dpdklab
2024-02-09 2:29 dpdklab
2024-02-09 2:10 dpdklab
2024-02-09 2:08 dpdklab
2024-02-09 1:09 dpdklab
2024-02-09 0:08 dpdklab
2024-02-09 0:01 dpdklab
2024-02-08 23:59 dpdklab
2024-02-08 23:59 dpdklab
2024-02-08 23:57 dpdklab
2024-02-08 23:57 dpdklab
2024-02-08 23:56 dpdklab
2024-02-08 23:56 dpdklab
2024-02-08 23:56 dpdklab
2024-02-08 23:54 dpdklab
2024-02-08 23:54 dpdklab
2024-02-08 23:54 dpdklab
2024-02-08 23:53 dpdklab
2024-02-08 23:53 dpdklab
2024-02-08 23:53 dpdklab
2024-02-08 23:53 dpdklab
2024-02-08 23:53 dpdklab
2024-02-08 23:52 dpdklab
2024-02-08 23:52 dpdklab
2024-02-08 23:52 dpdklab
2024-02-08 23:51 dpdklab
2024-02-08 23:51 dpdklab
2024-02-08 23:51 dpdklab
2024-02-08 23:51 dpdklab
2024-02-08 23:51 dpdklab
2024-02-08 23:50 dpdklab
2024-02-08 23:50 dpdklab
2024-02-08 23:50 dpdklab
2024-02-08 23:50 dpdklab
2024-02-08 23:50 dpdklab
2024-02-08 23:49 dpdklab
2024-02-08 23:49 dpdklab
2024-02-08 23:49 dpdklab
2024-02-08 23:49 dpdklab
2024-02-08 23:49 dpdklab
2024-02-08 23:49 dpdklab
2024-02-08 23:48 dpdklab
2024-02-08 23:48 dpdklab
2024-02-08 23:48 dpdklab
2024-02-08 23:47 dpdklab
2024-02-08 23:47 dpdklab
2024-02-08 23:47 dpdklab
2024-02-08 23:47 dpdklab
2024-02-08 23:46 dpdklab
2024-02-08 23:46 dpdklab
2024-02-08 23:45 dpdklab
2024-02-08 23:45 dpdklab
2024-02-08 23:44 dpdklab
2024-02-08 23:43 dpdklab
2024-02-08 23:43 dpdklab
2024-02-08 23:41 dpdklab
2024-02-08 23:40 dpdklab
2024-02-08 23:40 dpdklab
2024-02-08 23:39 dpdklab
2024-02-08 23:38 dpdklab
2024-02-08 23:38 dpdklab
2024-02-08 23:34 dpdklab
2024-02-08 23:27 dpdklab
2024-02-08 23:27 dpdklab
2024-02-08 23:26 dpdklab
2024-02-08 23:23 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=65c567d3.050a0220.8976b.1132SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=stephen@networkplumber.org \
--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).