From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135456-135473 [PATCH] [v5,18/18] log: mark PMD logtype a
Date: Thu, 21 Dec 2023 10:39:33 -0800 (PST) [thread overview]
Message-ID: <65848665.050a0220.f4bec.5f65SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135473
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, December 21 2023 16:46:35
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e
135456-135473 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | 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 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang version 10.0.0-4ubuntu1
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28717/
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-21 18:39 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 18:39 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-21 20:36 dpdklab
2023-12-21 20:24 dpdklab
2023-12-21 20:22 dpdklab
2023-12-21 20:14 dpdklab
2023-12-21 19:21 dpdklab
2023-12-21 19:15 dpdklab
2023-12-21 19:03 dpdklab
2023-12-21 19:03 dpdklab
2023-12-21 19:00 dpdklab
2023-12-21 18:59 dpdklab
2023-12-21 18:58 dpdklab
2023-12-21 18:30 dpdklab
2023-12-21 18:27 dpdklab
2023-12-21 18:26 dpdklab
2023-12-21 18:22 dpdklab
2023-12-21 18:20 dpdklab
2023-12-21 18:18 dpdklab
2023-12-21 18:18 dpdklab
2023-12-21 18:15 dpdklab
2023-12-21 18:12 dpdklab
2023-12-21 18:11 dpdklab
2023-12-21 18:11 dpdklab
2023-12-21 18:06 dpdklab
2023-12-21 18:05 dpdklab
2023-12-21 18:04 dpdklab
2023-12-21 18:04 dpdklab
2023-12-21 18:03 dpdklab
2023-12-21 18:03 dpdklab
2023-12-21 18:02 dpdklab
2023-12-21 18:02 dpdklab
2023-12-21 18:01 dpdklab
2023-12-21 18:00 dpdklab
2023-12-21 17:59 dpdklab
2023-12-21 17:58 dpdklab
2023-12-21 17:58 dpdklab
2023-12-21 17:56 dpdklab
2023-12-21 17:54 dpdklab
2023-12-21 17:54 dpdklab
2023-12-21 17:53 dpdklab
2023-12-21 17:53 dpdklab
2023-12-21 17:51 dpdklab
2023-12-21 17:51 dpdklab
2023-12-21 17:50 dpdklab
2023-12-21 17:50 dpdklab
2023-12-21 17:49 dpdklab
2023-12-21 17:47 dpdklab
2023-12-21 17:46 dpdklab
2023-12-21 17:45 dpdklab
2023-12-21 17:44 dpdklab
2023-12-21 17:44 dpdklab
2023-12-21 17:40 dpdklab
2023-12-21 17:40 dpdklab
2023-12-21 17:39 dpdklab
2023-12-21 17:36 dpdklab
2023-12-21 17:36 dpdklab
2023-12-21 17:34 dpdklab
2023-12-21 17:33 dpdklab
2023-12-21 17:31 dpdklab
2023-12-21 17:31 dpdklab
2023-12-21 17:31 dpdklab
2023-12-21 17:30 dpdklab
2023-12-21 17:30 dpdklab
2023-12-21 17:29 dpdklab
2023-12-21 17:29 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=65848665.050a0220.f4bec.5f65SMTPIN_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).