automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137401-137403 [PATCH] [3/3] rcu: use rte macro instead o
Date: Tue, 27 Feb 2024 20:03:01 -0800 (PST)	[thread overview]
Message-ID: <65deb075.170a0220.5e010.3cf6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1709075273-6885-4-git-send-email-roretzla@linux.microsoft.com>

Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137403

_Testing PASS_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Tuesday, February 27 2024 23:07:53 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049

137401-137403 --> testing pass

Test environment and result as below:

+--------------------------+---------------------------+------------------------------+----------------+--------------+
|       Environment        | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest | dpdk_unit_test | lpm_autotest |
+==========================+===========================+==============================+================+==============+
| Debian 12 (arm)          | PASS                      | PASS                         | PASS           | SKIPPED      |
+--------------------------+---------------------------+------------------------------+----------------+--------------+
| CentOS Stream 9 (ARM)    | SKIPPED                   | SKIPPED                      | PASS           | SKIPPED      |
+--------------------------+---------------------------+------------------------------+----------------+--------------+
| Fedora 37 (ARM)          | SKIPPED                   | SKIPPED                      | PASS           | SKIPPED      |
+--------------------------+---------------------------+------------------------------+----------------+--------------+
| Debian 11 (Buster) (ARM) | SKIPPED                   | SKIPPED                      | PASS           | SKIPPED      |
+--------------------------+---------------------------+------------------------------+----------------+--------------+
| Ubuntu 20.04 (ARM)       | SKIPPED                   | SKIPPED                      | PASS           | SKIPPED      |
+--------------------------+---------------------------+------------------------------+----------------+--------------+
| Fedora 38 (ARM Clang)    | SKIPPED                   | SKIPPED                      | PASS           | SKIPPED      |
+--------------------------+---------------------------+------------------------------+----------------+--------------+
| Ubuntu 20.04 ARM SVE     | SKIPPED                   | SKIPPED                      | SKIPPED        | PASS         |
+--------------------------+---------------------------+------------------------------+----------------+--------------+


Debian 12 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 11

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.3.1

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.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

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/29305/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2024-02-28  4:03 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1709075273-6885-4-git-send-email-roretzla@linux.microsoft.com>
2024-02-27 22:46 ` |SUCCESS| pw137401-137403 [PATCH 3/3] rcu: use rte macro instead of GCC attribute qemudev
2024-02-27 22:50 ` qemudev
2024-02-27 23:09 ` |SUCCESS| pw137403 " checkpatch
2024-02-28  0:05 ` 0-day Robot
2024-02-28  0:32 ` |SUCCESS| pw137401-137403 [PATCH] [3/3] rcu: use rte macro instead o dpdklab
2024-02-28  0:32 ` dpdklab
2024-02-28  0:40 ` dpdklab
2024-02-28  0:46 ` dpdklab
2024-02-28  1:12 ` dpdklab
2024-02-28  1:16 ` dpdklab
2024-02-28  1:16 ` dpdklab
2024-02-28  1:18 ` dpdklab
2024-02-28  1:19 ` dpdklab
2024-02-28  1:19 ` dpdklab
2024-02-28  1:21 ` dpdklab
2024-02-28  1:22 ` dpdklab
2024-02-28  1:30 ` dpdklab
2024-02-28  2:10 ` dpdklab
2024-02-28  2:15 ` dpdklab
2024-02-28  2:16 ` dpdklab
2024-02-28  2:26 ` dpdklab
2024-02-28  2:26 ` dpdklab
2024-02-28  2:27 ` dpdklab
2024-02-28  2:27 ` dpdklab
2024-02-28  2:28 ` dpdklab
2024-02-28  2:28 ` dpdklab
2024-02-28  2:29 ` dpdklab
2024-02-28  2:30 ` dpdklab
2024-02-28  2:31 ` dpdklab
2024-02-28  2:31 ` dpdklab
2024-02-28  2:31 ` dpdklab
2024-02-28  2:43 ` dpdklab
2024-02-28  2:44 ` dpdklab
2024-02-28  2:55 ` dpdklab
2024-02-28  2:56 ` dpdklab
2024-02-28  2:58 ` dpdklab
2024-02-28  2:59 ` dpdklab
2024-02-28  3:00 ` dpdklab
2024-02-28  3:01 ` dpdklab
2024-02-28  3:01 ` dpdklab
2024-02-28  3:01 ` dpdklab
2024-02-28  3:03 ` dpdklab
2024-02-28  3:03 ` dpdklab
2024-02-28  3:12 ` dpdklab
2024-02-28  3:12 ` dpdklab
2024-02-28  3:15 ` dpdklab
2024-02-28  3:32 ` dpdklab
2024-02-28  3:39 ` dpdklab
2024-02-28  3:46 ` dpdklab
2024-02-28  3:49 ` dpdklab
2024-02-28  3:52 ` dpdklab
2024-02-28  3:56 ` dpdklab
2024-02-28  4:01 ` dpdklab
2024-02-28  4:01 ` dpdklab
2024-02-28  4:02 ` dpdklab
2024-02-28  4:03 ` dpdklab [this message]
2024-02-28  4:18 ` dpdklab
2024-02-28  4:21 ` dpdklab
2024-02-28  6:44 ` dpdklab
2024-02-28  9:33 ` dpdklab
2024-02-28 13:02 ` dpdklab
2024-02-28 13:34 ` dpdklab
2024-02-28 20:55 ` dpdklab
2024-02-29 12:42 ` dpdklab
2024-02-29 15:47 ` dpdklab
2024-02-29 15:48 ` dpdklab
2024-02-29 16:06 ` dpdklab
2024-02-29 16:11 ` 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=65deb075.170a0220.5e010.3cf6SMTPIN_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).