From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw134017-134016 [PATCH] [RESEND,v7,3/3] ring: add telemetr
Date: Thu, 09 Nov 2023 09:00:09 -0800 (PST) [thread overview]
Message-ID: <654d1019.630a0220.6f9d1.4c4eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/134016
_Testing PASS_
Submitter: Jie Hai <haijie1@huawei.com>
Date: Thursday, November 09 2023 10:20:46
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:de0ec3c2458e3e2ce53e504c4ba92a36fcc78ef3
134017-134016 --> testing pass
Test environment and result as below:
+--------------------------+--------------+---------------------------+----------------+
| Environment | lpm_autotest | cryptodev_sw_zuc_autotest | dpdk_unit_test |
+==========================+==============+===========================+================+
| Ubuntu 20.04 ARM SVE | PASS | SKIPPED | SKIPPED |
+--------------------------+--------------+---------------------------+----------------+
| Debian 11 (arm) | SKIPPED | PASS | SKIPPED |
+--------------------------+--------------+---------------------------+----------------+
| Debian 11 (Buster) (ARM) | SKIPPED | SKIPPED | PASS |
+--------------------------+--------------+---------------------------+----------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28299/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-09 17:00 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 17:00 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-13 21:14 dpdklab
2023-11-13 20:59 dpdklab
2023-11-09 23:18 dpdklab
2023-11-09 19:59 dpdklab
2023-11-09 18:59 dpdklab
2023-11-09 18:19 dpdklab
2023-11-09 18:13 dpdklab
2023-11-09 17:57 dpdklab
2023-11-09 17:56 dpdklab
2023-11-09 17:49 dpdklab
2023-11-09 17:38 dpdklab
2023-11-09 17:35 dpdklab
2023-11-09 17:20 dpdklab
2023-11-09 17:17 dpdklab
2023-11-09 17:12 dpdklab
2023-11-09 17:10 dpdklab
2023-11-09 17:09 dpdklab
2023-11-09 17:08 dpdklab
2023-11-09 17:07 dpdklab
2023-11-09 17:06 dpdklab
2023-11-09 17:06 dpdklab
2023-11-09 16:56 dpdklab
2023-11-09 16:56 dpdklab
2023-11-09 16:56 dpdklab
2023-11-09 16:54 dpdklab
2023-11-09 16:48 dpdklab
2023-11-09 16:47 dpdklab
2023-11-09 16:47 dpdklab
2023-11-09 16:46 dpdklab
2023-11-09 16:46 dpdklab
2023-11-09 16:46 dpdklab
2023-11-09 16:45 dpdklab
2023-11-09 16:45 dpdklab
2023-11-09 16:45 dpdklab
2023-11-09 16:44 dpdklab
2023-11-09 16:43 dpdklab
2023-11-09 16:43 dpdklab
2023-11-09 16:43 dpdklab
2023-11-09 16:42 dpdklab
2023-11-09 16:41 dpdklab
2023-11-09 16:41 dpdklab
2023-11-09 16:40 dpdklab
2023-11-09 16:39 dpdklab
2023-11-09 16:39 dpdklab
2023-11-09 16:39 dpdklab
2023-11-09 16:38 dpdklab
2023-11-09 16:38 dpdklab
2023-11-09 16:37 dpdklab
2023-11-09 16:37 dpdklab
2023-11-09 16:36 dpdklab
2023-11-09 16:36 dpdklab
2023-11-09 16:34 dpdklab
2023-11-09 16:34 dpdklab
2023-11-09 16:30 dpdklab
2023-11-09 16:28 dpdklab
2023-11-09 16:26 dpdklab
2023-11-09 16: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=654d1019.630a0220.6f9d1.4c4eSMTPIN_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).