From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Ashwin Sekhar T K <asekhar@marvell.com>, dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130648-130650 [PATCH] [3/3] mempool/cnxk: fix alloc from
Date: Tue, 22 Aug 2023 19:45:57 -0700 (PDT) [thread overview]
Message-ID: <64e572e5.4a0a0220.c25e7.12ccSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130650
_Testing PASS_
Submitter: Ashwin Sekhar T K <asekhar@marvell.com>
Date: Tuesday, August 22 2023 17:01:57
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:971d2b57972919527e27ed683032a71864a2eb56
130648-130650 --> testing pass
Test environment and result as below:
+-----------------------+----------------+------------------------------+
| Environment | dpdk_unit_test | cryptodev_sw_snow3g_autotest |
+=======================+================+==============================+
| CentOS Stream 9 (ARM) | PASS | SKIPPED |
+-----------------------+----------------+------------------------------+
| Fedora 37 (ARM) | PASS | SKIPPED |
+-----------------------+----------------+------------------------------+
| Fedora 38 (ARM) | PASS | SKIPPED |
+-----------------------+----------------+------------------------------+
| Debian 11 (arm) | SKIPPED | PASS |
+-----------------------+----------------+------------------------------+
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.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/27419/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-23 2:45 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 2:45 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-23 19:17 dpdklab
2023-08-23 19:12 dpdklab
2023-08-23 19:08 dpdklab
2023-08-23 18:58 dpdklab
2023-08-23 18:40 dpdklab
2023-08-23 10:41 dpdklab
2023-08-23 5:13 dpdklab
2023-08-23 3:57 dpdklab
2023-08-23 3:57 dpdklab
2023-08-23 3:53 dpdklab
2023-08-23 3:52 dpdklab
2023-08-23 3:50 dpdklab
2023-08-23 3:50 dpdklab
2023-08-23 3:46 dpdklab
2023-08-23 3:42 dpdklab
2023-08-23 3:40 dpdklab
2023-08-23 3:39 dpdklab
2023-08-23 3:39 dpdklab
2023-08-23 3:36 dpdklab
2023-08-23 3:22 dpdklab
2023-08-23 3:06 dpdklab
2023-08-23 2:55 dpdklab
2023-08-23 2:52 dpdklab
2023-08-23 2:48 dpdklab
2023-08-23 2:47 dpdklab
2023-08-23 2:45 dpdklab
2023-08-23 2:31 dpdklab
2023-08-23 2:20 dpdklab
2023-08-23 2:14 dpdklab
2023-08-23 2:12 dpdklab
2023-08-23 2:12 dpdklab
2023-08-23 2:11 dpdklab
2023-08-23 2:11 dpdklab
2023-08-23 2:11 dpdklab
2023-08-23 2:10 dpdklab
2023-08-23 2:10 dpdklab
2023-08-23 2:10 dpdklab
2023-08-23 2:09 dpdklab
2023-08-23 2:09 dpdklab
2023-08-23 2:09 dpdklab
2023-08-23 2:09 dpdklab
2023-08-23 2:09 dpdklab
2023-08-23 2:08 dpdklab
2023-08-23 2:08 dpdklab
2023-08-23 2:06 dpdklab
2023-08-23 1:53 dpdklab
2023-08-23 1:52 dpdklab
2023-08-23 1:43 dpdklab
2023-08-23 1:03 dpdklab
2023-08-23 0:06 dpdklab
2023-08-22 23:54 dpdklab
2023-08-22 23:51 dpdklab
2023-08-22 23:43 dpdklab
2023-08-22 23:32 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=64e572e5.4a0a0220.c25e7.12ccSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=asekhar@marvell.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).