From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139176 [PATCH] [v3] cnxk: disable building template file
Date: Sat, 06 Apr 2024 06:55:27 -0700 (PDT) [thread overview]
Message-ID: <6611544f.050a0220.5a2bf.ee47SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240405214742.8324-1-pbhagavatula@marvell.com>
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139176
_Testing PASS_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Friday, April 05 2024 21:47:41
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139176 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Debian 12 with MUSDK | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
| Debian 12 (arm) | PASS |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Fedora 39 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+----------------------------------------+--------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-167-generic
Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0
Debian 12 with MUSDK
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang 10.0.0-4ubuntu1
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: 5.4.0-167-generic
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Fedora 39 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.2.1
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29731/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-04-06 13:55 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240405214742.8324-1-pbhagavatula@marvell.com>
2024-04-05 21:24 ` |SUCCESS| pw139176 [PATCH v3] cnxk: disable building template files qemudev
2024-04-05 21:29 ` qemudev
2024-04-05 21:49 ` checkpatch
2024-04-05 22:44 ` 0-day Robot
2024-04-06 11:59 ` |SUCCESS| pw139176 [PATCH] [v3] cnxk: disable building template file dpdklab
2024-04-06 12:06 ` dpdklab
2024-04-06 12:07 ` dpdklab
2024-04-06 12:07 ` dpdklab
2024-04-06 12:11 ` dpdklab
2024-04-06 12:31 ` dpdklab
2024-04-06 12:32 ` dpdklab
2024-04-06 12:33 ` dpdklab
2024-04-06 12:34 ` dpdklab
2024-04-06 12:36 ` dpdklab
2024-04-06 12:36 ` dpdklab
2024-04-06 12:38 ` dpdklab
2024-04-06 12:38 ` dpdklab
2024-04-06 12:38 ` dpdklab
2024-04-06 12:39 ` dpdklab
2024-04-06 12:39 ` dpdklab
2024-04-06 12:43 ` dpdklab
2024-04-06 12:43 ` dpdklab
2024-04-06 12:43 ` dpdklab
2024-04-06 12:44 ` dpdklab
2024-04-06 12:48 ` dpdklab
2024-04-06 12:50 ` dpdklab
2024-04-06 12:50 ` dpdklab
2024-04-06 12:50 ` dpdklab
2024-04-06 12:51 ` dpdklab
2024-04-06 12:51 ` dpdklab
2024-04-06 12:52 ` dpdklab
2024-04-06 13:17 ` dpdklab
2024-04-06 13:21 ` dpdklab
2024-04-06 13:21 ` dpdklab
2024-04-06 13:22 ` dpdklab
2024-04-06 13:22 ` dpdklab
2024-04-06 13:24 ` dpdklab
2024-04-06 13:26 ` dpdklab
2024-04-06 13:26 ` dpdklab
2024-04-06 13:26 ` dpdklab
2024-04-06 13:27 ` dpdklab
2024-04-06 13:27 ` dpdklab
2024-04-06 13:29 ` dpdklab
2024-04-06 13:30 ` dpdklab
2024-04-06 13:32 ` dpdklab
2024-04-06 13:33 ` dpdklab
2024-04-06 13:36 ` dpdklab
2024-04-06 13:38 ` dpdklab
2024-04-06 13:38 ` dpdklab
2024-04-06 13:38 ` dpdklab
2024-04-06 13:39 ` dpdklab
2024-04-06 13:40 ` dpdklab
2024-04-06 13:40 ` dpdklab
2024-04-06 13:40 ` dpdklab
2024-04-06 13:40 ` dpdklab
2024-04-06 13:40 ` dpdklab
2024-04-06 13:41 ` dpdklab
2024-04-06 13:41 ` dpdklab
2024-04-06 13:42 ` dpdklab
2024-04-06 13:43 ` dpdklab
2024-04-06 13:43 ` dpdklab
2024-04-06 13:44 ` dpdklab
2024-04-06 13:44 ` dpdklab
2024-04-06 13:44 ` dpdklab
2024-04-06 13:46 ` dpdklab
2024-04-06 13:47 ` dpdklab
2024-04-06 13:47 ` dpdklab
2024-04-06 13:47 ` dpdklab
2024-04-06 13:49 ` dpdklab
2024-04-06 13:51 ` dpdklab
2024-04-06 13:52 ` dpdklab
2024-04-06 13:54 ` dpdklab
2024-04-06 13:55 ` dpdklab [this message]
2024-04-06 13:57 ` dpdklab
2024-04-06 13:59 ` dpdklab
2024-04-06 13:59 ` dpdklab
2024-04-06 13:59 ` dpdklab
2024-04-06 14:00 ` dpdklab
2024-04-06 14:01 ` dpdklab
2024-04-06 14:08 ` dpdklab
2024-04-06 14:08 ` dpdklab
2024-04-06 14:08 ` dpdklab
2024-04-06 14:08 ` dpdklab
2024-04-06 14:09 ` |FAILURE| " dpdklab
2024-04-06 14:12 ` |SUCCESS| " dpdklab
2024-04-06 14:20 ` dpdklab
2024-04-06 14:20 ` |FAILURE| " dpdklab
2024-04-06 14:20 ` |SUCCESS| " dpdklab
2024-04-06 14:23 ` dpdklab
2024-04-06 14:31 ` dpdklab
2024-04-06 14:40 ` dpdklab
2024-04-06 14:40 ` 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=6611544f.050a0220.5a2bf.ee47SMTPIN_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).