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| pw135244-135249 [PATCH] [6/6] examples/vm_power_manager: f
Date: Mon, 18 Dec 2023 00:54:07 -0800 (PST) [thread overview]
Message-ID: <658008af.0d0a0220.32208.fe7cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135249
_Testing PASS_
Submitter: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
Date: Monday, December 18 2023 07:49:05
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e
135244-135249 --> testing pass
Test environment and result as below:
+--------------------------+----------------+---------------------------+
| Environment | dpdk_unit_test | cryptodev_sw_zuc_autotest |
+==========================+================+===========================+
| Debian 11 (Buster) (ARM) | PASS | SKIPPED |
+--------------------------+----------------+---------------------------+
| Fedora 37 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+---------------------------+
| CentOS Stream 9 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+---------------------------+
| Fedora 38 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+---------------------------+
| Ubuntu 20.04 (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
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28656/
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-18 8:54 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 8:54 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-18 9:35 dpdklab
2023-12-18 9:30 dpdklab
2023-12-18 9:23 dpdklab
2023-12-18 9:22 dpdklab
2023-12-18 9:21 dpdklab
2023-12-18 9:20 dpdklab
2023-12-18 9:18 dpdklab
2023-12-18 9:16 dpdklab
2023-12-18 9:14 dpdklab
2023-12-18 9:14 dpdklab
2023-12-18 9:14 dpdklab
2023-12-18 9:11 dpdklab
2023-12-18 9:10 dpdklab
2023-12-18 9:10 dpdklab
2023-12-18 9:07 dpdklab
2023-12-18 9:06 dpdklab
2023-12-18 9:04 dpdklab
2023-12-18 9:04 dpdklab
2023-12-18 9:04 dpdklab
2023-12-18 9:04 dpdklab
2023-12-18 9:02 dpdklab
2023-12-18 8:59 dpdklab
2023-12-18 8:58 dpdklab
2023-12-18 8:55 dpdklab
2023-12-18 8:55 dpdklab
2023-12-18 8:53 dpdklab
2023-12-18 8:52 dpdklab
2023-12-18 8:52 dpdklab
2023-12-18 8:51 dpdklab
2023-12-18 8:51 dpdklab
2023-12-18 8:51 dpdklab
2023-12-18 8:51 dpdklab
2023-12-18 8:51 dpdklab
2023-12-18 8:50 dpdklab
2023-12-18 8:50 dpdklab
2023-12-18 8:50 dpdklab
2023-12-18 8:50 dpdklab
2023-12-18 8:50 dpdklab
2023-12-18 8:50 dpdklab
2023-12-18 8:50 dpdklab
2023-12-18 8:49 dpdklab
2023-12-18 8:49 dpdklab
2023-12-18 8:49 dpdklab
2023-12-18 8:49 dpdklab
2023-12-18 8:49 dpdklab
2023-12-18 8:49 dpdklab
2023-12-18 8:48 dpdklab
2023-12-18 8:48 dpdklab
2023-12-18 8:47 dpdklab
2023-12-18 8:47 dpdklab
2023-12-18 8:47 dpdklab
2023-12-18 8:46 dpdklab
2023-12-18 8:46 dpdklab
2023-12-18 8:46 dpdklab
2023-12-18 8:46 dpdklab
2023-12-18 8:45 dpdklab
2023-12-18 8:45 dpdklab
2023-12-18 8:45 dpdklab
2023-12-18 8:44 dpdklab
2023-12-18 8:44 dpdklab
2023-12-18 8:44 dpdklab
2023-12-18 8:44 dpdklab
2023-12-18 8:43 dpdklab
2023-12-18 8:43 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=658008af.0d0a0220.32208.fe7cSMTPIN_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).