From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw134703-134721 [PATCH] [v5,19/19] drivers: remove use of
Date: Thu, 30 Nov 2023 19:24:34 -0800 (PST) [thread overview]
Message-ID: <656951f2.050a0220.44ada.5134SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/134721
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, November 29 2023 17:26:13
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:eeb0605f118dae66e80faa44f7b3e88748032353
134703-134721 --> testing pass
Test environment and result as below:
+--------------------------+----------------+--------------+
| Environment | dpdk_unit_test | lpm_autotest |
+==========================+================+==============+
| CentOS Stream 9 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+--------------+
| Debian 11 (Buster) (ARM) | PASS | SKIPPED |
+--------------------------+----------------+--------------+
| Fedora 38 (ARM Clang) | PASS | SKIPPED |
+--------------------------+----------------+--------------+
| Fedora 37 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+--------------+
| Fedora 38 (ARM) | PASS | SKIPPED |
+--------------------------+----------------+--------------+
| Ubuntu 20.04 ARM SVE | SKIPPED | PASS |
+--------------------------+----------------+--------------+
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 Clang)
Kernel: Depends on container host
Compiler: clang 16.0.3
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.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/28496/
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-01 3:24 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 3:24 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-01 10:30 dpdklab
2023-12-01 9:02 dpdklab
2023-12-01 6:33 dpdklab
2023-12-01 6:10 dpdklab
2023-12-01 6:06 dpdklab
2023-12-01 4:46 dpdklab
2023-12-01 4:44 dpdklab
2023-12-01 4:42 dpdklab
2023-12-01 4:27 dpdklab
2023-12-01 4:27 dpdklab
2023-12-01 4:25 dpdklab
2023-12-01 4:16 dpdklab
2023-12-01 4:13 dpdklab
2023-12-01 4:12 dpdklab
2023-12-01 4:11 dpdklab
2023-12-01 4:09 dpdklab
2023-12-01 4:08 dpdklab
2023-12-01 4:03 dpdklab
2023-12-01 3:51 dpdklab
2023-12-01 3:51 dpdklab
2023-12-01 3:51 dpdklab
2023-12-01 3:50 dpdklab
2023-12-01 3:45 dpdklab
2023-12-01 3:45 dpdklab
2023-12-01 3:41 dpdklab
2023-12-01 3:41 dpdklab
2023-12-01 3:41 dpdklab
2023-12-01 3:33 dpdklab
2023-12-01 3:18 dpdklab
2023-12-01 3:08 dpdklab
2023-12-01 3:07 dpdklab
2023-12-01 3:07 dpdklab
2023-12-01 3:06 dpdklab
2023-12-01 3:06 dpdklab
2023-12-01 3:06 dpdklab
2023-12-01 3:06 dpdklab
2023-12-01 3:03 dpdklab
2023-12-01 3:03 dpdklab
2023-12-01 2:49 dpdklab
2023-12-01 2:47 dpdklab
2023-12-01 2:47 dpdklab
2023-12-01 2:46 dpdklab
2023-12-01 2:46 dpdklab
2023-12-01 2:45 dpdklab
2023-12-01 2:38 dpdklab
2023-12-01 2:33 dpdklab
2023-12-01 2:33 dpdklab
2023-12-01 2:25 dpdklab
2023-12-01 2:23 dpdklab
2023-12-01 2:19 dpdklab
2023-12-01 2:18 dpdklab
2023-12-01 2:17 dpdklab
2023-12-01 2:07 dpdklab
2023-12-01 2:06 dpdklab
2023-12-01 2:06 dpdklab
2023-12-01 2:00 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=656951f2.050a0220.44ada.5134SMTPIN_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).