From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136844-136846 [PATCH] [v2,3/3] add extension keyword to
Date: Fri, 16 Feb 2024 06:39:04 -0800 (PST) [thread overview]
Message-ID: <65cf7388.0d0a0220.ebafc.6e70SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136846
_Testing PASS_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Friday, February 16 2024 10:24:54
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:537caad2c70057c68e110211bab0cb4088f391d2
136844-136846 --> 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 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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29170/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-16 14:39 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 14:39 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-17 3:29 dpdklab
2024-02-16 16:56 dpdklab
2024-02-16 15:59 dpdklab
2024-02-16 15:55 dpdklab
2024-02-16 15:51 dpdklab
2024-02-16 15:49 dpdklab
2024-02-16 15:32 dpdklab
2024-02-16 14:57 dpdklab
2024-02-16 14:51 dpdklab
2024-02-16 14:46 dpdklab
2024-02-16 14:43 dpdklab
2024-02-16 14:42 dpdklab
2024-02-16 14:41 dpdklab
2024-02-16 14:40 dpdklab
2024-02-16 14:37 dpdklab
2024-02-16 14:35 dpdklab
2024-02-16 14:29 dpdklab
2024-02-16 14:20 dpdklab
2024-02-16 14:18 dpdklab
2024-02-16 14:15 dpdklab
2024-02-16 14:14 dpdklab
2024-02-16 14:13 dpdklab
2024-02-16 14:11 dpdklab
2024-02-16 14:11 dpdklab
2024-02-16 14:10 dpdklab
2024-02-16 14:09 dpdklab
2024-02-16 14:08 dpdklab
2024-02-16 14:07 dpdklab
2024-02-16 14:07 dpdklab
2024-02-16 14:06 dpdklab
2024-02-16 14:05 dpdklab
2024-02-16 14:04 dpdklab
2024-02-16 14:04 dpdklab
2024-02-16 14:04 dpdklab
2024-02-16 14:03 dpdklab
2024-02-16 14:01 dpdklab
2024-02-16 14:01 dpdklab
2024-02-16 14:01 dpdklab
2024-02-16 14:00 dpdklab
2024-02-16 14:00 dpdklab
2024-02-16 13:58 dpdklab
2024-02-16 13:56 dpdklab
2024-02-16 13:54 dpdklab
2024-02-16 13:54 dpdklab
2024-02-16 13:51 dpdklab
2024-02-16 13:50 dpdklab
2024-02-16 13:49 dpdklab
2024-02-16 13:48 dpdklab
2024-02-16 13:46 dpdklab
2024-02-16 13:46 dpdklab
2024-02-16 13:44 dpdklab
2024-02-16 13:44 dpdklab
2024-02-16 13:43 dpdklab
2024-02-16 13:43 dpdklab
2024-02-16 13:41 dpdklab
2024-02-16 13:40 dpdklab
2024-02-16 13:40 dpdklab
2024-02-16 13:39 dpdklab
2024-02-16 13:38 dpdklab
2024-02-16 13:35 dpdklab
2024-02-16 13:35 dpdklab
2024-02-16 13:12 dpdklab
2024-02-16 13:11 dpdklab
2024-02-16 13:09 dpdklab
2024-02-16 13:06 dpdklab
2024-02-16 13:03 dpdklab
2024-02-16 13:03 dpdklab
2024-02-16 13:00 dpdklab
2024-02-16 12:55 dpdklab
2024-02-16 12:53 dpdklab
2024-02-16 12:51 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=65cf7388.0d0a0220.ebafc.6e70SMTPIN_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).