From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130090 [PATCH] mbuf: add ESP packet type
Date: Thu, 10 Aug 2023 14:41:03 -0700 (PDT) [thread overview]
Message-ID: <64d5596f.020a0220.be717.478fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130090
_Testing PASS_
Submitter: Alexander Kozyrev <akozyrev@nvidia.com>
Date: Thursday, August 10 2023 15:54:08
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:70b6941e4e22d67bc10495d1638234a7e974f582
130090 --> testing pass
Test environment and result as below:
+--------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+======================================+====================+
| CentOS Stream 9 (ARM) | PASS |
+--------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+--------------------------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+--------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+--------------------------------------+--------------------+
| Fedora 38 (ARM Clang) | PASS |
+--------------------------------------+--------------------+
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang version 10.0.0-4ubuntu1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
Fedora 38 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 16.0.3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27283/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-10 21:41 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 21:41 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-14 3:28 dpdklab
2023-08-14 3:17 dpdklab
2023-08-14 3:12 dpdklab
2023-08-14 3:11 dpdklab
2023-08-14 3:11 dpdklab
2023-08-14 3:09 dpdklab
2023-08-14 3:09 dpdklab
2023-08-14 3:08 dpdklab
2023-08-14 3:07 dpdklab
2023-08-14 3:06 dpdklab
2023-08-14 3:05 dpdklab
2023-08-14 3:05 dpdklab
2023-08-13 23:30 dpdklab
2023-08-13 19:25 dpdklab
2023-08-11 11:05 dpdklab
2023-08-11 10:38 dpdklab
2023-08-11 10:03 dpdklab
2023-08-11 9:57 dpdklab
2023-08-11 9:56 dpdklab
2023-08-11 2:00 dpdklab
2023-08-10 22:42 dpdklab
2023-08-10 22:34 dpdklab
2023-08-10 22:33 dpdklab
2023-08-10 22:32 dpdklab
2023-08-10 22:31 dpdklab
2023-08-10 22:29 dpdklab
2023-08-10 22:28 dpdklab
2023-08-10 22:23 dpdklab
2023-08-10 22:22 dpdklab
2023-08-10 22:16 dpdklab
2023-08-10 22:15 dpdklab
2023-08-10 22:14 dpdklab
2023-08-10 22:14 dpdklab
2023-08-10 22:14 dpdklab
2023-08-10 22:06 dpdklab
2023-08-10 21:58 dpdklab
2023-08-10 21:46 dpdklab
2023-08-10 21:46 dpdklab
2023-08-10 21:46 dpdklab
2023-08-10 21:44 dpdklab
2023-08-10 21:43 dpdklab
2023-08-10 21:42 dpdklab
2023-08-10 21:41 dpdklab
2023-08-10 21:33 dpdklab
2023-08-10 21:31 dpdklab
2023-08-10 21:30 dpdklab
2023-08-10 21:29 dpdklab
2023-08-10 21:28 dpdklab
2023-08-10 21:28 dpdklab
2023-08-10 21:27 dpdklab
2023-08-10 21:25 dpdklab
2023-08-10 21:22 dpdklab
2023-08-10 21:22 dpdklab
2023-08-10 21:21 dpdklab
2023-08-10 21:21 dpdklab
2023-08-10 21:18 dpdklab
2023-08-10 21:18 dpdklab
2023-08-10 21:17 dpdklab
2023-08-10 21:09 dpdklab
2023-08-10 20:54 dpdklab
2023-08-10 20:09 dpdklab
2023-08-10 19:57 dpdklab
2023-08-10 18:09 dpdklab
2023-08-10 18:08 dpdklab
2023-08-10 17:59 dpdklab
2023-08-10 17:49 dpdklab
[not found] <20230810155408.2045404-1-akozyrev@nvidia.com>
2023-08-10 15:46 ` qemudev
2023-08-10 15:50 ` qemudev
2023-08-10 15:55 ` checkpatch
2023-08-10 17:18 ` 0-day Robot
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=64d5596f.020a0220.be717.478fSMTPIN_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).