From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135243 [PATCH] net/e1000: support launchtime feature
Date: Sun, 17 Dec 2023 13:11:53 -0800 (PST) [thread overview]
Message-ID: <657f6419.250a0220.3106e.248eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135243
_Testing PASS_
Submitter: Chuanyu Xue <chuanyu.xue@uconn.edu>
Date: Sunday, December 17 2023 20:20:40
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e
135243 --> testing pass
Test environment and result as below:
+--------------------------+------------------------------+---------------------------+----------------+
| Environment | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest | dpdk_unit_test |
+==========================+==============================+===========================+================+
| Debian 11 (arm) | PASS | PASS | SKIPPED |
+--------------------------+------------------------------+---------------------------+----------------+
| Debian 11 (Buster) (ARM) | SKIPPED | SKIPPED | PASS |
+--------------------------+------------------------------+---------------------------+----------------+
| Fedora 37 (ARM) | SKIPPED | SKIPPED | PASS |
+--------------------------+------------------------------+---------------------------+----------------+
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
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28655/
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-17 21:11 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-17 21:11 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-17 22:24 dpdklab
2023-12-17 22:04 dpdklab
2023-12-17 21:58 dpdklab
2023-12-17 21:47 dpdklab
2023-12-17 21:47 dpdklab
2023-12-17 21:44 dpdklab
2023-12-17 21:43 dpdklab
2023-12-17 21:43 dpdklab
2023-12-17 21:43 dpdklab
2023-12-17 21:40 dpdklab
2023-12-17 21:39 dpdklab
2023-12-17 21:37 dpdklab
2023-12-17 21:36 dpdklab
2023-12-17 21:35 dpdklab
2023-12-17 21:33 dpdklab
2023-12-17 21:33 dpdklab
2023-12-17 21:32 dpdklab
2023-12-17 21:32 dpdklab
2023-12-17 21:27 dpdklab
2023-12-17 21:26 dpdklab
2023-12-17 21:26 dpdklab
2023-12-17 21:26 dpdklab
2023-12-17 21:25 dpdklab
2023-12-17 21:24 dpdklab
2023-12-17 21:24 dpdklab
2023-12-17 21:23 dpdklab
2023-12-17 21:21 dpdklab
2023-12-17 21:20 dpdklab
2023-12-17 21:19 dpdklab
2023-12-17 21:19 dpdklab
2023-12-17 21:19 dpdklab
2023-12-17 21:18 dpdklab
2023-12-17 21:18 dpdklab
2023-12-17 21:17 dpdklab
2023-12-17 21:17 dpdklab
2023-12-17 21:17 dpdklab
2023-12-17 21:16 dpdklab
2023-12-17 21:16 dpdklab
2023-12-17 21:15 dpdklab
2023-12-17 21:15 dpdklab
2023-12-17 21:15 dpdklab
2023-12-17 21:12 dpdklab
2023-12-17 21:12 dpdklab
2023-12-17 21:12 dpdklab
2023-12-17 21:11 dpdklab
2023-12-17 21:10 dpdklab
2023-12-17 21:09 dpdklab
2023-12-17 21:09 dpdklab
2023-12-17 21:09 dpdklab
2023-12-17 21:09 dpdklab
2023-12-17 21:09 dpdklab
2023-12-17 21:08 dpdklab
2023-12-17 21:08 dpdklab
2023-12-17 21:08 dpdklab
2023-12-17 21:08 dpdklab
2023-12-17 21:08 dpdklab
2023-12-17 21:08 dpdklab
2023-12-17 21:07 dpdklab
2023-12-17 21:07 dpdklab
2023-12-17 21:07 dpdklab
2023-12-17 21:07 dpdklab
2023-12-17 21:05 dpdklab
2023-12-17 21:05 dpdklab
2023-12-17 21:05 dpdklab
2023-12-17 21:04 dpdklab
[not found] <20231217202040.478959-1-chuanyu.xue@uconn.edu>
2023-12-17 20:02 ` qemudev
2023-12-17 20:06 ` qemudev
2023-12-17 21:30 ` 0-day Robot
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=657f6419.250a0220.3106e.248eSMTPIN_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).