From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>,
dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135371-135376 [PATCH] [v3,6/6] examples/vm_power_manager
Date: Tue, 19 Dec 2023 23:51:39 -0800 (PST) [thread overview]
Message-ID: <65829d0b.050a0220.30b88.0004SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135376
_Testing PASS_
Submitter: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
Date: Wednesday, December 20 2023 06:45:01
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e
135371-135376 --> testing pass
Test environment and result as below:
+--------------------------+----------------+------------------------------+
| Environment | dpdk_unit_test | cryptodev_sw_snow3g_autotest |
+==========================+================+==============================+
| Debian 11 (Buster) (ARM) | PASS | SKIPPED |
+--------------------------+----------------+------------------------------+
| Fedora 37 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+------------------------------+
| CentOS Stream 9 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+------------------------------+
| Fedora 38 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+------------------------------+
| Debian 11 (arm) | SKIPPED | 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
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28692/
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-20 7:51 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 7:51 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-20 9:02 dpdklab
2023-12-20 8:54 dpdklab
2023-12-20 8:50 dpdklab
2023-12-20 8:48 dpdklab
2023-12-20 8:46 dpdklab
2023-12-20 8:46 dpdklab
2023-12-20 8:42 dpdklab
2023-12-20 8:40 dpdklab
2023-12-20 8:37 dpdklab
2023-12-20 8:36 dpdklab
2023-12-20 8:35 dpdklab
2023-12-20 8:34 dpdklab
2023-12-20 8:34 dpdklab
2023-12-20 8:33 dpdklab
2023-12-20 8:33 dpdklab
2023-12-20 8:32 dpdklab
2023-12-20 8:30 dpdklab
2023-12-20 8:29 dpdklab
2023-12-20 8:27 dpdklab
2023-12-20 8:26 dpdklab
2023-12-20 8:25 dpdklab
2023-12-20 8:25 dpdklab
2023-12-20 8:21 dpdklab
2023-12-20 8:20 dpdklab
2023-12-20 8:16 dpdklab
2023-12-20 8:16 dpdklab
2023-12-20 8:14 dpdklab
2023-12-20 8:13 dpdklab
2023-12-20 8:13 dpdklab
2023-12-20 8:12 dpdklab
2023-12-20 8:10 dpdklab
2023-12-20 8:10 dpdklab
2023-12-20 8:10 dpdklab
2023-12-20 8:02 dpdklab
2023-12-20 8:01 dpdklab
2023-12-20 8:01 dpdklab
2023-12-20 7:59 dpdklab
2023-12-20 7:59 dpdklab
2023-12-20 7:57 dpdklab
2023-12-20 7:55 dpdklab
2023-12-20 7:55 dpdklab
2023-12-20 7:54 dpdklab
2023-12-20 7:54 dpdklab
2023-12-20 7:53 dpdklab
2023-12-20 7:52 dpdklab
2023-12-20 7:52 dpdklab
2023-12-20 7:51 dpdklab
2023-12-20 7:51 dpdklab
2023-12-20 7:51 dpdklab
2023-12-20 7:50 dpdklab
2023-12-20 7:50 dpdklab
2023-12-20 7:49 dpdklab
2023-12-20 7:49 dpdklab
2023-12-20 7:49 dpdklab
2023-12-20 7:48 dpdklab
2023-12-20 7:48 dpdklab
2023-12-20 7:41 dpdklab
2023-12-20 7:41 dpdklab
2023-12-20 7:41 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=65829d0b.050a0220.30b88.0004SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=Sivaprasad.Tummala@amd.com \
--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).