From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136885-136887 [PATCH] [4/4] cfgfile: add unique name fla
Date: Mon, 19 Feb 2024 21:27:50 -0800 (PST) [thread overview]
Message-ID: <65d43856.810a0220.2363d.07e5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136887
_Testing PASS_
Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Tuesday, February 20 2024 03:58:40
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4aa3ea9d5a17df941fab13a648e69b8de8573992
136885-136887 --> testing pass
Test environment and result as below:
+--------------------------+--------------+----------------+
| Environment | lpm_autotest | dpdk_unit_test |
+==========================+==============+================+
| Ubuntu 20.04 ARM SVE | PASS | SKIPPED |
+--------------------------+--------------+----------------+
| CentOS Stream 9 (ARM) | SKIPPED | PASS |
+--------------------------+--------------+----------------+
| Fedora 37 (ARM) | SKIPPED | PASS |
+--------------------------+--------------+----------------+
| Debian 11 (Buster) (ARM) | 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)
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
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/29185/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-20 5:27 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 5:27 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-21 8:29 dpdklab
2024-02-21 6:23 dpdklab
2024-02-21 0:24 dpdklab
2024-02-20 6:17 dpdklab
2024-02-20 6:03 dpdklab
2024-02-20 6:02 dpdklab
2024-02-20 5:57 dpdklab
2024-02-20 5:50 dpdklab
2024-02-20 5:48 dpdklab
2024-02-20 5:42 dpdklab
2024-02-20 5:32 dpdklab
2024-02-20 5:31 dpdklab
2024-02-20 5:26 dpdklab
2024-02-20 5:26 dpdklab
2024-02-20 5:26 dpdklab
2024-02-20 5:24 dpdklab
2024-02-20 5:24 dpdklab
2024-02-20 5:23 dpdklab
2024-02-20 5:20 dpdklab
2024-02-20 5:15 dpdklab
2024-02-20 5:06 dpdklab
2024-02-20 5:05 dpdklab
2024-02-20 5:05 dpdklab
2024-02-20 5:05 dpdklab
2024-02-20 5:05 dpdklab
2024-02-20 5:05 dpdklab
2024-02-20 5:04 dpdklab
2024-02-20 5:03 dpdklab
2024-02-20 5:03 dpdklab
2024-02-20 5:02 dpdklab
2024-02-20 5:02 dpdklab
2024-02-20 5:02 dpdklab
2024-02-20 5:01 dpdklab
2024-02-20 5:01 dpdklab
2024-02-20 5:01 dpdklab
2024-02-20 5:00 dpdklab
2024-02-20 5:00 dpdklab
2024-02-20 4:59 dpdklab
2024-02-20 4:59 dpdklab
2024-02-20 4:59 dpdklab
2024-02-20 4:59 dpdklab
2024-02-20 4:59 dpdklab
2024-02-20 4:59 dpdklab
2024-02-20 4:59 dpdklab
2024-02-20 4:56 dpdklab
2024-02-20 4:56 dpdklab
2024-02-20 4:56 dpdklab
2024-02-20 4:55 dpdklab
2024-02-20 4:55 dpdklab
2024-02-20 4:55 dpdklab
2024-02-20 4:55 dpdklab
2024-02-20 4:54 dpdklab
2024-02-20 4:54 dpdklab
2024-02-20 4:54 dpdklab
2024-02-20 4:54 dpdklab
2024-02-20 4:54 dpdklab
2024-02-20 4:54 dpdklab
2024-02-20 4:53 dpdklab
2024-02-20 4:53 dpdklab
2024-02-20 4:53 dpdklab
2024-02-20 4:52 dpdklab
2024-02-20 4:52 dpdklab
2024-02-20 4:47 dpdklab
2024-02-20 4:47 dpdklab
2024-02-20 4:47 dpdklab
2024-02-20 4:46 dpdklab
2024-02-20 4:46 dpdklab
2024-02-20 4:45 dpdklab
2024-02-20 4:45 dpdklab
2024-02-20 4:45 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=65d43856.810a0220.2363d.07e5SMTPIN_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).