From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130622 [PATCH] doc: update for Intel IPU
Date: Tue, 22 Aug 2023 13:10:10 -0700 (PDT) [thread overview]
Message-ID: <64e51622.050a0220.77d49.92dfSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130622
_Testing PASS_
Submitter: Xing, Beilei <beilei.xing@intel.com>
Date: Tuesday, August 22 2023 10:52:56
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:971d2b57972919527e27ed683032a71864a2eb56
130622 --> testing pass
Test environment and result as below:
+-----------------------------+------------------------------+---------------------------+----------------+--------------+
| Environment | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest | dpdk_unit_test | lpm_autotest |
+=============================+==============================+===========================+================+==============+
| Debian 11 (arm) | PASS | PASS | SKIPPED | SKIPPED |
+-----------------------------+------------------------------+---------------------------+----------------+--------------+
| Fedora 37 (ARM) | SKIPPED | SKIPPED | PASS | SKIPPED |
+-----------------------------+------------------------------+---------------------------+----------------+--------------+
| CentOS Stream 9 (ARM) | SKIPPED | SKIPPED | PASS | SKIPPED |
+-----------------------------+------------------------------+---------------------------+----------------+--------------+
| Debian 11 (Buster) (ARM) | SKIPPED | SKIPPED | PASS | SKIPPED |
+-----------------------------+------------------------------+---------------------------+----------------+--------------+
| Fedora 38 (ARM) | SKIPPED | SKIPPED | PASS | SKIPPED |
+-----------------------------+------------------------------+---------------------------+----------------+--------------+
| Ubuntu 20.04 (ARM) | SKIPPED | SKIPPED | PASS | SKIPPED |
+-----------------------------+------------------------------+---------------------------+----------------+--------------+
| Fedora 38 (ARM Clang) | SKIPPED | SKIPPED | PASS | SKIPPED |
+-----------------------------+------------------------------+---------------------------+----------------+--------------+
| 32-bit Ubuntu 20.04.4 (ARM) | SKIPPED | SKIPPED | PASS | SKIPPED |
+-----------------------------+------------------------------+---------------------------+----------------+--------------+
| Ubuntu 20.04 ARM SVE | SKIPPED | 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
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
Fedora 38 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 16.0.3
32-bit Ubuntu 20.04.4 (ARM)
Kernel: 5.4.0-148-generic aarch64
Compiler: gcc 9.4
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27407/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-22 20:10 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 20:10 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-23 15:21 dpdklab
2023-08-23 6:12 dpdklab
2023-08-23 6:00 dpdklab
2023-08-23 5:55 dpdklab
2023-08-23 5:49 dpdklab
2023-08-23 5:46 dpdklab
2023-08-22 22:16 dpdklab
2023-08-22 20:57 dpdklab
2023-08-22 20:24 dpdklab
2023-08-22 20:18 dpdklab
2023-08-22 20:18 dpdklab
2023-08-22 20:17 dpdklab
2023-08-22 20:17 dpdklab
2023-08-22 20:16 dpdklab
2023-08-22 20:16 dpdklab
2023-08-22 20:15 dpdklab
2023-08-22 20:13 dpdklab
2023-08-22 20:13 dpdklab
2023-08-22 20:09 dpdklab
2023-08-22 20:01 dpdklab
2023-08-22 19:56 dpdklab
2023-08-22 19:45 dpdklab
2023-08-22 19:39 dpdklab
2023-08-22 19:39 dpdklab
2023-08-22 19:39 dpdklab
2023-08-22 19:38 dpdklab
2023-08-22 19:38 dpdklab
2023-08-22 19:36 dpdklab
2023-08-22 19:36 dpdklab
2023-08-22 19:36 dpdklab
2023-08-22 19:36 dpdklab
2023-08-22 19:35 dpdklab
2023-08-22 19:32 dpdklab
2023-08-22 19:32 dpdklab
2023-08-22 19:32 dpdklab
2023-08-22 19:32 dpdklab
2023-08-22 19:32 dpdklab
2023-08-22 19:31 dpdklab
2023-08-22 19:31 dpdklab
2023-08-22 19:31 dpdklab
2023-08-22 19:31 dpdklab
2023-08-22 19:28 dpdklab
2023-08-22 19:28 dpdklab
2023-08-22 19:27 dpdklab
2023-08-22 19:27 dpdklab
2023-08-22 19:27 dpdklab
2023-08-22 19:26 dpdklab
2023-08-22 19:25 dpdklab
2023-08-22 19:22 dpdklab
2023-08-22 19:22 dpdklab
2023-08-22 19:22 dpdklab
2023-08-22 19:22 dpdklab
2023-08-22 19:21 dpdklab
2023-08-22 19:20 dpdklab
2023-08-22 19:17 dpdklab
2023-08-22 19:17 dpdklab
2023-08-22 19:12 dpdklab
2023-08-22 19:12 dpdklab
2023-08-22 19:11 dpdklab
[not found] <20230822105256.328431-1-beilei.xing@intel.com>
2023-08-22 2:21 ` qemudev
2023-08-22 2:25 ` qemudev
2023-08-22 2:35 ` checkpatch
2023-08-22 3:19 ` 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=64e51622.050a0220.77d49.92dfSMTPIN_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).