From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135135 [PATCH] [v4] net/af_xdp: enable uds_path instead
Date: Wed, 13 Dec 2023 11:37:57 -0800 (PST) [thread overview]
Message-ID: <657a0815.050a0220.7d5a3.2017SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135135
_Testing PASS_
Submitter: Maryam Tahhan <mtahhan@redhat.com>
Date: Wednesday, December 13 2023 12:24:33
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:f2d5afbb2c05d7647da7ea914887c52115652651
135135 --> 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 38 (ARM) | SKIPPED | SKIPPED | PASS | SKIPPED |
+--------------------------+------------------------------+---------------------------+----------------+--------------+
| Debian 11 (Buster) (ARM) | SKIPPED | SKIPPED | PASS | SKIPPED |
+--------------------------+------------------------------+---------------------------+----------------+--------------+
| Fedora 37 (ARM) | SKIPPED | SKIPPED | PASS | SKIPPED |
+--------------------------+------------------------------+---------------------------+----------------+--------------+
| Ubuntu 20.04 (ARM) | SKIPPED | SKIPPED | PASS | SKIPPED |
+--------------------------+------------------------------+---------------------------+----------------+--------------+
| Fedora 38 (ARM Clang) | SKIPPED | SKIPPED | PASS | SKIPPED |
+--------------------------+------------------------------+---------------------------+----------------+--------------+
| CentOS Stream 9 (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 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
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
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
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/28610/
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-13 19:38 UTC|newest]
Thread overview: 99+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 19:37 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-15 21:53 dpdklab
2023-12-13 22:01 dpdklab
2023-12-13 21:37 dpdklab
2023-12-13 21:13 dpdklab
2023-12-13 21:10 dpdklab
2023-12-13 21:06 dpdklab
2023-12-13 21:04 dpdklab
2023-12-13 21:03 dpdklab
2023-12-13 21:02 dpdklab
2023-12-13 21:01 dpdklab
2023-12-13 20:57 dpdklab
2023-12-13 20:57 dpdklab
2023-12-13 20:57 dpdklab
2023-12-13 20:57 dpdklab
2023-12-13 20:56 dpdklab
2023-12-13 20:55 dpdklab
2023-12-13 20:54 dpdklab
2023-12-13 20:53 dpdklab
2023-12-13 20:52 dpdklab
2023-12-13 20:51 dpdklab
2023-12-13 20:51 dpdklab
2023-12-13 20:51 dpdklab
2023-12-13 20:50 dpdklab
2023-12-13 20:50 dpdklab
2023-12-13 20:50 dpdklab
2023-12-13 20:50 dpdklab
2023-12-13 20:49 dpdklab
2023-12-13 20:49 dpdklab
2023-12-13 20:49 dpdklab
2023-12-13 20:48 dpdklab
2023-12-13 20:47 dpdklab
2023-12-13 20:46 dpdklab
2023-12-13 20:45 dpdklab
2023-12-13 20:40 dpdklab
2023-12-13 20:12 dpdklab
2023-12-13 20:08 dpdklab
2023-12-13 20:01 dpdklab
2023-12-13 19:54 dpdklab
2023-12-13 19:39 dpdklab
2023-12-13 19:34 dpdklab
2023-12-13 19:33 dpdklab
2023-12-13 19:24 dpdklab
2023-12-13 19:21 dpdklab
2023-12-13 18:51 dpdklab
2023-12-13 18:51 dpdklab
2023-12-13 18:27 dpdklab
2023-12-13 18:05 dpdklab
2023-12-13 18:04 dpdklab
2023-12-13 17:59 dpdklab
2023-12-13 17:57 dpdklab
2023-12-13 17:57 dpdklab
2023-12-13 17:57 dpdklab
2023-12-13 17:55 dpdklab
2023-12-13 17:53 dpdklab
2023-12-13 17:53 dpdklab
2023-12-13 17:52 dpdklab
2023-12-13 17:52 dpdklab
2023-12-13 17:44 dpdklab
2023-12-13 17:42 dpdklab
2023-12-13 17:41 dpdklab
2023-12-13 17:41 dpdklab
2023-12-13 17:34 dpdklab
2023-12-13 17:32 dpdklab
2023-12-13 17:32 dpdklab
2023-12-13 17:31 dpdklab
2023-12-13 17:31 dpdklab
2023-12-13 17:31 dpdklab
2023-12-13 17:29 dpdklab
2023-12-13 17:25 dpdklab
2023-12-13 17:19 dpdklab
2023-12-13 17:19 dpdklab
2023-12-13 17:18 dpdklab
2023-12-13 17:18 dpdklab
2023-12-13 17:17 dpdklab
2023-12-13 17:17 dpdklab
2023-12-13 17:16 dpdklab
2023-12-13 17:15 dpdklab
2023-12-13 17:15 dpdklab
2023-12-13 17:07 dpdklab
2023-12-13 17:04 dpdklab
2023-12-13 17:03 dpdklab
2023-12-13 17:01 dpdklab
2023-12-13 16:59 dpdklab
2023-12-13 16:58 dpdklab
2023-12-13 16:57 dpdklab
2023-12-13 16:55 dpdklab
2023-12-13 16:51 dpdklab
2023-12-13 16:51 dpdklab
2023-12-13 16:50 dpdklab
2023-12-13 16:50 dpdklab
2023-12-13 16:49 dpdklab
2023-12-13 16:37 dpdklab
2023-12-13 16:36 dpdklab
2023-12-13 16:34 dpdklab
2023-12-13 16:33 dpdklab
2023-12-13 16:02 dpdklab
2023-12-13 16:00 dpdklab
2023-12-13 15:50 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=657a0815.050a0220.7d5a3.2017SMTPIN_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).