From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136232 [PATCH] maintainers: update for fm10k/ifc drivers
Date: Wed, 31 Jan 2024 06:12:44 -0800 (PST) [thread overview]
Message-ID: <65ba555c.810a0220.d245c.3a06SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136232
_Testing PASS_
Submitter: Xiao Wang <xiao.w.wang@intel.com>
Date: Wednesday, January 31 2024 09:50:08
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:5eedf66ac0e5ce62cd333e523996c63a3c4c2c00
136232 --> testing pass
Test environment and result as below:
+--------------------------+--------------------+
| Environment | dpdk_meson_compile |
+==========================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+--------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+--------------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+--------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+--------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+--------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+--------------------------+--------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.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
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/29001/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-31 14:12 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 14:12 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-31 15:41 dpdklab
2024-01-31 15:17 dpdklab
2024-01-31 15:07 dpdklab
2024-01-31 15:00 dpdklab
2024-01-31 15:00 dpdklab
2024-01-31 14:57 dpdklab
2024-01-31 14:54 dpdklab
2024-01-31 14:53 dpdklab
2024-01-31 14:51 dpdklab
2024-01-31 14:49 dpdklab
2024-01-31 14:48 dpdklab
2024-01-31 14:47 dpdklab
2024-01-31 14:46 dpdklab
2024-01-31 14:46 dpdklab
2024-01-31 14:43 dpdklab
2024-01-31 14:43 dpdklab
2024-01-31 14:42 dpdklab
2024-01-31 14:41 dpdklab
2024-01-31 14:40 dpdklab
2024-01-31 14:39 dpdklab
2024-01-31 14:38 dpdklab
2024-01-31 14:37 dpdklab
2024-01-31 14:36 dpdklab
2024-01-31 14:35 dpdklab
2024-01-31 14:34 dpdklab
2024-01-31 14:34 dpdklab
2024-01-31 14:33 dpdklab
2024-01-31 14:33 dpdklab
2024-01-31 14:32 dpdklab
2024-01-31 14:32 dpdklab
2024-01-31 14:29 dpdklab
2024-01-31 14:29 dpdklab
2024-01-31 14:29 dpdklab
2024-01-31 14:26 dpdklab
2024-01-31 14:25 dpdklab
2024-01-31 14:25 dpdklab
2024-01-31 14:25 dpdklab
2024-01-31 14:23 dpdklab
2024-01-31 14:23 dpdklab
2024-01-31 14:23 dpdklab
2024-01-31 14:21 dpdklab
2024-01-31 14:21 dpdklab
2024-01-31 14:20 dpdklab
2024-01-31 14:20 dpdklab
2024-01-31 14:19 dpdklab
2024-01-31 14:18 dpdklab
2024-01-31 14:17 dpdklab
2024-01-31 14:17 dpdklab
2024-01-31 14:16 dpdklab
2024-01-31 14:15 dpdklab
2024-01-31 14:15 dpdklab
2024-01-31 14:14 dpdklab
2024-01-31 14:14 dpdklab
2024-01-31 14:13 dpdklab
2024-01-31 14:12 dpdklab
2024-01-31 14:12 dpdklab
2024-01-31 14:12 dpdklab
2024-01-31 14:12 dpdklab
2024-01-31 14:12 dpdklab
2024-01-31 14:11 dpdklab
2024-01-31 14:11 dpdklab
2024-01-31 14:11 dpdklab
2024-01-31 14:10 dpdklab
2024-01-31 14:10 dpdklab
2024-01-31 14:10 dpdklab
[not found] <20240131095008.1547927-1-xiao.w.wang@intel.com>
2024-01-31 9:45 ` qemudev
2024-01-31 9:49 ` qemudev
2024-01-31 9:51 ` checkpatch
2024-01-31 10:43 ` 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=65ba555c.810a0220.d245c.3a06SMTPIN_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).