From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw134118-134119 [PATCH] [v3,2/2] examples/l3fwd: relax the
Date: Sun, 12 Nov 2023 00:16:27 -0800 (PST) [thread overview]
Message-ID: <655089db.c80a0220.61d82.8922SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/134119
_Testing PASS_
Submitter: Trevor Tao <taozj888@163.com>
Date: Sunday, November 12 2023 07:16:11
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fa6a754e746551382922c8be4db0e8f8e39bab40
134118-134119 --> testing pass
Test environment and result as below:
+-----------------------+---------------------------+------------------------------+----------------+
| Environment | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest | dpdk_unit_test |
+=======================+===========================+==============================+================+
| Debian 11 (arm) | PASS | PASS | SKIPPED |
+-----------------------+---------------------------+------------------------------+----------------+
| Fedora 37 (ARM) | SKIPPED | SKIPPED | PASS |
+-----------------------+---------------------------+------------------------------+----------------+
| CentOS Stream 9 (ARM) | SKIPPED | SKIPPED | PASS |
+-----------------------+---------------------------+------------------------------+----------------+
Debian 11 (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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28338/
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-12 8:16 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 8:16 dpdklab [this message]
2023-11-12 8:16 dpdklab
2023-11-12 8:16 dpdklab
2023-11-12 8:18 dpdklab
2023-11-12 8:18 dpdklab
2023-11-12 8:18 dpdklab
2023-11-12 8:19 dpdklab
2023-11-12 8:19 dpdklab
2023-11-12 8:20 dpdklab
2023-11-12 8:20 dpdklab
2023-11-12 8:21 dpdklab
2023-11-12 8:22 dpdklab
2023-11-12 8:22 dpdklab
2023-11-12 8:23 dpdklab
2023-11-12 8:23 dpdklab
2023-11-12 8:24 dpdklab
2023-11-12 8:24 dpdklab
2023-11-12 8:24 dpdklab
2023-11-12 8:25 dpdklab
2023-11-12 8:26 dpdklab
2023-11-12 8:27 dpdklab
2023-11-12 8:27 dpdklab
2023-11-12 8:28 dpdklab
2023-11-12 8:28 dpdklab
2023-11-12 8:29 dpdklab
2023-11-12 8:29 dpdklab
2023-11-12 8:29 dpdklab
2023-11-12 8:29 dpdklab
2023-11-12 8:29 dpdklab
2023-11-12 8:30 dpdklab
2023-11-12 8:30 dpdklab
2023-11-12 8:30 dpdklab
2023-11-12 8:31 dpdklab
2023-11-12 8:31 dpdklab
2023-11-12 8:31 dpdklab
2023-11-12 8:31 dpdklab
2023-11-12 8:31 dpdklab
2023-11-12 8:31 dpdklab
2023-11-12 8:32 dpdklab
2023-11-12 8:33 dpdklab
2023-11-12 8:36 dpdklab
2023-11-12 8:38 dpdklab
2023-11-12 8:41 dpdklab
2023-11-12 8:42 dpdklab
2023-11-12 8:45 dpdklab
2023-11-12 8:46 dpdklab
2023-11-12 8:46 dpdklab
2023-11-12 8:49 dpdklab
2023-11-12 8:50 dpdklab
2023-11-12 8:50 dpdklab
2023-11-12 9:04 dpdklab
2023-11-12 9:05 dpdklab
2023-11-12 11:14 dpdklab
2023-11-15 4:56 dpdklab
2023-11-15 5:19 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=655089db.c80a0220.61d82.8922SMTPIN_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).