From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138440 [PATCH] [v3,1/1] eal: add C++ include guard in ge
Date: Mon, 18 Mar 2024 04:12:57 -0700 (PDT) [thread overview]
Message-ID: <65f821b9.0d0a0220.32816.c087SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240318024415.555614-1-ashish.sadanandan@gmail.com>
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138440
_Testing PASS_
Submitter: Ashish Sadanandan <ashish.sadanandan@gmail.com>
Date: Monday, March 18 2024 02:44:15
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2
138440 --> testing pass
Test environment and result as below:
+--------------------------+----------------+--------------+------------------------------+---------------------------+
| Environment | dpdk_unit_test | lpm_autotest | cryptodev_sw_snow3g_autotest | cryptodev_sw_zuc_autotest |
+==========================+================+==============+==============================+===========================+
| Debian 11 (Buster) (ARM) | PASS | SKIPPED | SKIPPED | SKIPPED |
+--------------------------+----------------+--------------+------------------------------+---------------------------+
| Fedora 38 (ARM) | PASS | SKIPPED | SKIPPED | SKIPPED |
+--------------------------+----------------+--------------+------------------------------+---------------------------+
| CentOS Stream 9 (ARM) | PASS | SKIPPED | SKIPPED | SKIPPED |
+--------------------------+----------------+--------------+------------------------------+---------------------------+
| Debian 12 (arm) | PASS | SKIPPED | PASS | PASS |
+--------------------------+----------------+--------------+------------------------------+---------------------------+
| Fedora 38 (ARM Clang) | PASS | SKIPPED | SKIPPED | SKIPPED |
+--------------------------+----------------+--------------+------------------------------+---------------------------+
| Fedora 37 (ARM) | PASS | SKIPPED | SKIPPED | SKIPPED |
+--------------------------+----------------+--------------+------------------------------+---------------------------+
| Ubuntu 20.04 (ARM) | PASS | SKIPPED | SKIPPED | SKIPPED |
+--------------------------+----------------+--------------+------------------------------+---------------------------+
| Ubuntu 20.04 ARM SVE | SKIPPED | PASS | SKIPPED | SKIPPED |
+--------------------------+----------------+--------------+------------------------------+---------------------------+
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
Fedora 38 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 16.0.3
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29578/
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-18 11:12 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240318024415.555614-1-ashish.sadanandan@gmail.com>
2024-03-18 2:24 ` |SUCCESS| pw138440 [PATCH v3 1/1] eal: add C++ include guard in generic/rte_vect.h qemudev
2024-03-18 2:29 ` qemudev
2024-03-18 2:44 ` checkpatch
2024-03-18 3:43 ` 0-day Robot
2024-03-18 9:23 ` |SUCCESS| pw138440 [PATCH] [v3,1/1] eal: add C++ include guard in ge dpdklab
2024-03-18 9:24 ` dpdklab
2024-03-18 9:25 ` dpdklab
2024-03-18 9:44 ` dpdklab
2024-03-18 9:44 ` dpdklab
2024-03-18 9:45 ` dpdklab
2024-03-18 9:45 ` dpdklab
2024-03-18 9:45 ` dpdklab
2024-03-18 9:46 ` dpdklab
2024-03-18 9:47 ` dpdklab
2024-03-18 9:49 ` dpdklab
2024-03-18 10:02 ` dpdklab
2024-03-18 10:03 ` dpdklab
2024-03-18 10:04 ` dpdklab
2024-03-18 10:06 ` dpdklab
2024-03-18 10:06 ` dpdklab
2024-03-18 10:06 ` dpdklab
2024-03-18 10:07 ` dpdklab
2024-03-18 10:07 ` dpdklab
2024-03-18 10:07 ` dpdklab
2024-03-18 10:08 ` dpdklab
2024-03-18 10:09 ` dpdklab
2024-03-18 10:10 ` dpdklab
2024-03-18 10:19 ` dpdklab
2024-03-18 10:20 ` dpdklab
2024-03-18 10:20 ` dpdklab
2024-03-18 10:21 ` dpdklab
2024-03-18 10:21 ` dpdklab
2024-03-18 10:22 ` dpdklab
2024-03-18 10:23 ` dpdklab
2024-03-18 10:23 ` dpdklab
2024-03-18 10:23 ` dpdklab
2024-03-18 10:24 ` dpdklab
2024-03-18 10:25 ` dpdklab
2024-03-18 10:25 ` dpdklab
2024-03-18 10:25 ` dpdklab
2024-03-18 10:26 ` dpdklab
2024-03-18 10:26 ` dpdklab
2024-03-18 10:26 ` dpdklab
2024-03-18 10:26 ` dpdklab
2024-03-18 10:28 ` dpdklab
2024-03-18 10:28 ` dpdklab
2024-03-18 10:28 ` dpdklab
2024-03-18 10:28 ` dpdklab
2024-03-18 10:29 ` dpdklab
2024-03-18 10:29 ` dpdklab
2024-03-18 10:29 ` dpdklab
2024-03-18 10:30 ` dpdklab
2024-03-18 10:30 ` dpdklab
2024-03-18 10:30 ` dpdklab
2024-03-18 10:30 ` dpdklab
2024-03-18 10:30 ` dpdklab
2024-03-18 10:31 ` dpdklab
2024-03-18 10:31 ` dpdklab
2024-03-18 10:31 ` dpdklab
2024-03-18 10:32 ` dpdklab
2024-03-18 10:32 ` dpdklab
2024-03-18 10:32 ` dpdklab
2024-03-18 10:47 ` dpdklab
2024-03-18 10:47 ` dpdklab
2024-03-18 10:48 ` dpdklab
2024-03-18 10:48 ` dpdklab
2024-03-18 10:53 ` dpdklab
2024-03-18 10:57 ` dpdklab
2024-03-18 11:08 ` dpdklab
2024-03-18 11:11 ` dpdklab
2024-03-18 11:12 ` dpdklab [this message]
2024-03-18 11:17 ` dpdklab
2024-03-18 12:40 ` dpdklab
2024-03-18 12:43 ` dpdklab
2024-03-18 12:46 ` dpdklab
2024-03-20 10:40 ` dpdklab
2024-03-20 11:16 ` 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=65f821b9.0d0a0220.32816.c087SMTPIN_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).