From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135241 [PATCH] [v2,1/5] app/test-mp: add multiprocess te
Date: Sun, 17 Dec 2023 03:05:04 -0800 (PST) [thread overview]
Message-ID: <657ed5e0.0d0a0220.e4f99.8e62SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135241
_Testing PASS_
Submitter: Artemy Kovalyov <artemyko@nvidia.com>
Date: Sunday, December 17 2023 03:53:59
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e
135241 --> testing pass
Test environment and result as below:
+--------------------------+----------------+
| Environment | dpdk_unit_test |
+==========================+================+
| Debian 11 (Buster) (ARM) | PASS |
+--------------------------+----------------+
| Fedora 37 (ARM) | PASS |
+--------------------------+----------------+
| CentOS Stream 9 (ARM) | PASS |
+--------------------------+----------------+
| Fedora 38 (ARM) | PASS |
+--------------------------+----------------+
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
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28653/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-17 11:05 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-17 11:05 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-17 13:15 dpdklab
2023-12-17 12:24 dpdklab
2023-12-17 12:14 dpdklab
2023-12-17 12:13 dpdklab
2023-12-17 12:10 dpdklab
2023-12-17 12:05 dpdklab
2023-12-17 12:05 dpdklab
2023-12-17 12:02 dpdklab
2023-12-17 12:01 dpdklab
2023-12-17 12:00 dpdklab
2023-12-17 11:59 dpdklab
2023-12-17 11:58 dpdklab
2023-12-17 11:57 dpdklab
2023-12-17 11:57 dpdklab
2023-12-17 11:55 dpdklab
2023-12-17 11:54 dpdklab
2023-12-17 11:54 dpdklab
2023-12-17 11:53 dpdklab
2023-12-17 11:52 dpdklab
2023-12-17 11:50 dpdklab
2023-12-17 11:48 dpdklab
2023-12-17 11:44 dpdklab
2023-12-17 11:43 dpdklab
2023-12-17 11:43 dpdklab
2023-12-17 11:42 dpdklab
2023-12-17 11:41 dpdklab
2023-12-17 11:41 dpdklab
2023-12-17 11:40 dpdklab
2023-12-17 11:38 dpdklab
2023-12-17 11:37 dpdklab
2023-12-17 11:37 dpdklab
2023-12-17 11:36 dpdklab
2023-12-17 11:34 dpdklab
2023-12-17 11:32 dpdklab
2023-12-17 11:32 dpdklab
2023-12-17 11:31 dpdklab
2023-12-17 11:30 dpdklab
2023-12-17 11:29 dpdklab
2023-12-17 11:29 dpdklab
2023-12-17 11:26 dpdklab
2023-12-17 11:26 dpdklab
2023-12-17 11:25 dpdklab
2023-12-17 11:20 dpdklab
2023-12-17 11:18 dpdklab
2023-12-17 11:18 dpdklab
2023-12-17 11:14 dpdklab
2023-12-17 11:13 dpdklab
2023-12-17 11:11 dpdklab
2023-12-17 11:09 dpdklab
2023-12-17 11:08 dpdklab
2023-12-17 11:02 dpdklab
2023-12-17 11:01 dpdklab
2023-12-17 11:01 dpdklab
2023-12-17 10:59 dpdklab
2023-12-17 10:59 dpdklab
2023-12-17 10:57 dpdklab
2023-12-17 10:56 dpdklab
2023-12-17 10:53 dpdklab
2023-12-17 10:52 dpdklab
2023-12-17 10:49 dpdklab
2023-12-17 10:48 dpdklab
2023-12-17 10:47 dpdklab
2023-12-17 10:43 dpdklab
2023-12-17 10:42 dpdklab
2023-12-17 10:41 dpdklab
2023-12-17 10:40 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=657ed5e0.0d0a0220.e4f99.8e62SMTPIN_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).