From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw134507-134515 [PATCH] [24.03,v2,9/9] event/sw: add sched
Date: Tue, 21 Nov 2023 04:47:05 -0800 (PST) [thread overview]
Message-ID: <655ca6c9.050a0220.b86d7.7547SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/134515
_Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Tuesday, November 21 2023 11:54:37
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:517b4b26b508a6464d07c456c04eb48d6c7f03ea
134507-134515 --> testing pass
Test environment and result as below:
+-----------------------+--------------+------------------------------+----------------+
| Environment | lpm_autotest | cryptodev_sw_snow3g_autotest | dpdk_unit_test |
+=======================+==============+==============================+================+
| Ubuntu 20.04 ARM SVE | PASS | SKIPPED | SKIPPED |
+-----------------------+--------------+------------------------------+----------------+
| Debian 11 (arm) | SKIPPED | PASS | SKIPPED |
+-----------------------+--------------+------------------------------+----------------+
| CentOS Stream 9 (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
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28427/
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-21 12:47 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-21 12:47 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-21 15:23 dpdklab
2023-11-21 14:59 dpdklab
2023-11-21 13:56 dpdklab
2023-11-21 13:51 dpdklab
2023-11-21 13:46 dpdklab
2023-11-21 13:27 dpdklab
2023-11-21 13:12 dpdklab
2023-11-21 13:10 dpdklab
2023-11-21 13:07 dpdklab
2023-11-21 13:05 dpdklab
2023-11-21 13:02 dpdklab
2023-11-21 13:02 dpdklab
2023-11-21 12:59 dpdklab
2023-11-21 12:58 dpdklab
2023-11-21 12:57 dpdklab
2023-11-21 12:55 dpdklab
2023-11-21 12:54 dpdklab
2023-11-21 12:53 dpdklab
2023-11-21 12:51 dpdklab
2023-11-21 12:49 dpdklab
2023-11-21 12:49 dpdklab
2023-11-21 12:48 dpdklab
2023-11-21 12:48 dpdklab
2023-11-21 12:48 dpdklab
2023-11-21 12:46 dpdklab
2023-11-21 12:46 dpdklab
2023-11-21 12:45 dpdklab
2023-11-21 12:44 dpdklab
2023-11-21 12:44 dpdklab
2023-11-21 12:43 dpdklab
2023-11-21 12:42 dpdklab
2023-11-21 12:41 dpdklab
2023-11-21 12:41 dpdklab
2023-11-21 12:41 dpdklab
2023-11-21 12:41 dpdklab
2023-11-21 12:41 dpdklab
2023-11-21 12:39 dpdklab
2023-11-21 12:39 dpdklab
2023-11-21 12:39 dpdklab
2023-11-21 12:39 dpdklab
2023-11-21 12:38 dpdklab
2023-11-21 12:38 dpdklab
2023-11-21 12:38 dpdklab
2023-11-21 12:38 dpdklab
2023-11-21 12:38 dpdklab
2023-11-21 12:38 dpdklab
2023-11-21 12:38 dpdklab
2023-11-21 12:38 dpdklab
2023-11-21 12:38 dpdklab
2023-11-21 12:36 dpdklab
2023-11-21 12:36 dpdklab
2023-11-21 12:35 dpdklab
2023-11-21 12:34 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=655ca6c9.050a0220.b86d7.7547SMTPIN_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).