From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138649-138651 [PATCH] [v7,4/4] cryptodev: remove rte mar
Date: Wed, 20 Mar 2024 22:44:31 -0700 (PDT) [thread overview]
Message-ID: <65fbc93f.0d0a0220.f322e.ad59SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1710972098-2209-5-git-send-email-roretzla@linux.microsoft.com>
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138651
_Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wednesday, March 20 2024 22:01:38
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2
138649-138651 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Debian 12 with MUSDK | PASS |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+----------------------------------------+--------------------+
| Debian 12 (arm) | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM Clang) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| CentOS Stream 9 (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
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
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
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0
Fedora 38 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 16.0.6
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang 10.0.0-4ubuntu1
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.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
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.4.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29616/
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-03-21 5:44 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1710972098-2209-5-git-send-email-roretzla@linux.microsoft.com>
2024-03-20 21:39 ` |SUCCESS| pw138649-138651 [PATCH v7 4/4] cryptodev: remove rte marker fields qemudev
2024-03-20 21:43 ` qemudev
2024-03-20 22:03 ` |SUCCESS| pw138651 " checkpatch
2024-03-20 23:05 ` |FAILURE| " 0-day Robot
2024-03-21 0:17 ` |SUCCESS| pw138649-138651 [PATCH] [v7,4/4] cryptodev: remove rte mar dpdklab
2024-03-21 0:18 ` dpdklab
2024-03-21 0:25 ` dpdklab
2024-03-21 0:34 ` dpdklab
2024-03-21 0:36 ` dpdklab
2024-03-21 0:36 ` dpdklab
2024-03-21 0:37 ` dpdklab
2024-03-21 0:42 ` dpdklab
2024-03-21 0:44 ` dpdklab
2024-03-21 0:45 ` dpdklab
2024-03-21 0:48 ` dpdklab
2024-03-21 0:50 ` |WARNING| " dpdklab
2024-03-21 0:50 ` dpdklab
2024-03-21 0:52 ` dpdklab
2024-03-21 0:52 ` |SUCCESS| " dpdklab
2024-03-21 0:52 ` |WARNING| " dpdklab
2024-03-21 1:01 ` dpdklab
2024-03-21 1:03 ` dpdklab
2024-03-21 1:08 ` dpdklab
2024-03-21 1:13 ` |SUCCESS| " dpdklab
2024-03-21 1:13 ` |WARNING| " dpdklab
2024-03-21 1:18 ` dpdklab
2024-03-21 1:44 ` dpdklab
2024-03-21 1:47 ` |SUCCESS| " dpdklab
2024-03-21 1:48 ` dpdklab
2024-03-21 1:48 ` dpdklab
2024-03-21 1:49 ` dpdklab
2024-03-21 1:49 ` dpdklab
2024-03-21 1:52 ` dpdklab
2024-03-21 1:53 ` dpdklab
2024-03-21 1:55 ` dpdklab
2024-03-21 1:56 ` dpdklab
2024-03-21 2:24 ` dpdklab
2024-03-21 2:27 ` dpdklab
2024-03-21 2:29 ` dpdklab
2024-03-21 2:29 ` dpdklab
2024-03-21 2:29 ` dpdklab
2024-03-21 2:30 ` dpdklab
2024-03-21 2:30 ` dpdklab
2024-03-21 2:41 ` dpdklab
2024-03-21 2:42 ` dpdklab
2024-03-21 2:48 ` dpdklab
2024-03-21 2:51 ` dpdklab
2024-03-21 2:57 ` dpdklab
2024-03-21 2:58 ` dpdklab
2024-03-21 2:59 ` dpdklab
2024-03-21 2:59 ` dpdklab
2024-03-21 3:00 ` dpdklab
2024-03-21 3:01 ` dpdklab
2024-03-21 3:01 ` dpdklab
2024-03-21 3:02 ` dpdklab
2024-03-21 3:03 ` dpdklab
2024-03-21 3:03 ` dpdklab
2024-03-21 3:03 ` dpdklab
2024-03-21 3:04 ` dpdklab
2024-03-21 3:05 ` dpdklab
2024-03-21 3:05 ` dpdklab
2024-03-21 3:06 ` dpdklab
2024-03-21 3:06 ` dpdklab
2024-03-21 3:06 ` dpdklab
2024-03-21 3:07 ` dpdklab
2024-03-21 3:07 ` dpdklab
2024-03-21 3:08 ` dpdklab
2024-03-21 3:09 ` dpdklab
2024-03-21 3:09 ` dpdklab
2024-03-21 3:10 ` dpdklab
2024-03-21 3:10 ` dpdklab
2024-03-21 3:20 ` dpdklab
2024-03-21 3:21 ` dpdklab
2024-03-21 3:24 ` dpdklab
2024-03-21 3:27 ` dpdklab
2024-03-21 3:43 ` dpdklab
2024-03-21 4:55 ` dpdklab
2024-03-21 5:44 ` dpdklab [this message]
2024-03-21 16:18 ` dpdklab
2024-03-22 14:23 ` dpdklab
2024-03-22 14:59 ` 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=65fbc93f.0d0a0220.f322e.ad59SMTPIN_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).