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| pw138575 [PATCH] buildtools: fix build with clang 17
Date: Wed, 20 Mar 2024 10:01:50 -0700 (PDT)	[thread overview]
Message-ID: <65fb167e.d40a0220.8a467.00ceSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240320155814.617220-1-alialnu@nvidia.com>

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

_Testing PASS_

Submitter: Ali Alnubani <alialnu@nvidia.com>
Date: Wednesday, March 20 2024 15:58:14 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2

138575 --> 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      |
+--------------------------+---------------------------+------------------------------+----------------+--------------+
| Fedora 37 (ARM)          | SKIPPED                   | SKIPPED                      | PASS           | SKIPPED      |
+--------------------------+---------------------------+------------------------------+----------------+--------------+
| CentOS Stream 9 (ARM)    | SKIPPED                   | SKIPPED                      | PASS           | SKIPPED      |
+--------------------------+---------------------------+------------------------------+----------------+--------------+
| Debian 11 (Buster) (ARM) | SKIPPED                   | SKIPPED                      | PASS           | SKIPPED      |
+--------------------------+---------------------------+------------------------------+----------------+--------------+
| Ubuntu 20.04 (ARM)       | SKIPPED                   | SKIPPED                      | PASS           | SKIPPED      |
+--------------------------+---------------------------+------------------------------+----------------+--------------+
| Ubuntu 20.04 ARM SVE     | SKIPPED                   | SKIPPED                      | SKIPPED        | PASS         |
+--------------------------+---------------------------+------------------------------+----------------+--------------+


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

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

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.4.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

Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-167-generic
	Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29604/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-20 17:02 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240320155814.617220-1-alialnu@nvidia.com>
2024-03-20 15:37 ` qemudev
2024-03-20 15:42 ` qemudev
2024-03-20 16:01 ` checkpatch
2024-03-20 16:47 ` dpdklab
2024-03-20 16:48 ` dpdklab
2024-03-20 16:48 ` dpdklab
2024-03-20 16:48 ` dpdklab
2024-03-20 16:48 ` dpdklab
2024-03-20 16:49 ` dpdklab
2024-03-20 16:49 ` dpdklab
2024-03-20 16:49 ` dpdklab
2024-03-20 16:49 ` dpdklab
2024-03-20 16:50 ` dpdklab
2024-03-20 16:50 ` dpdklab
2024-03-20 16:50 ` dpdklab
2024-03-20 16:50 ` dpdklab
2024-03-20 16:50 ` dpdklab
2024-03-20 16:50 ` dpdklab
2024-03-20 16:51 ` dpdklab
2024-03-20 16:51 ` dpdklab
2024-03-20 16:51 ` dpdklab
2024-03-20 16:52 ` dpdklab
2024-03-20 16:52 ` dpdklab
2024-03-20 16:52 ` dpdklab
2024-03-20 16:52 ` dpdklab
2024-03-20 16:52 ` dpdklab
2024-03-20 16:53 ` dpdklab
2024-03-20 16:53 ` dpdklab
2024-03-20 16:53 ` dpdklab
2024-03-20 16:53 ` dpdklab
2024-03-20 16:54 ` dpdklab
2024-03-20 16:54 ` dpdklab
2024-03-20 16:57 ` dpdklab
2024-03-20 16:57 ` dpdklab
2024-03-20 16:58 ` dpdklab
2024-03-20 16:58 ` dpdklab
2024-03-20 16:58 ` dpdklab
2024-03-20 16:58 ` dpdklab
2024-03-20 16:58 ` dpdklab
2024-03-20 16:59 ` |FAILURE| " dpdklab
2024-03-20 16:59 ` |SUCCESS| " dpdklab
2024-03-20 16:59 ` |FAILURE| " dpdklab
2024-03-20 16:59 ` dpdklab
2024-03-20 16:59 ` |SUCCESS| " dpdklab
2024-03-20 16:59 ` dpdklab
2024-03-20 16:59 ` dpdklab
2024-03-20 17:01 ` dpdklab
2024-03-20 17:01 ` |FAILURE| " dpdklab
2024-03-20 17:01 ` |SUCCESS| " dpdklab
2024-03-20 17:01 ` |FAILURE| " dpdklab
2024-03-20 17:01 ` dpdklab [this message]
2024-03-20 17:02 ` |SUCCESS| " dpdklab
2024-03-20 17:02 ` dpdklab
2024-03-20 17:02 ` dpdklab
2024-03-20 17:02 ` dpdklab
2024-03-20 17:02 ` dpdklab
2024-03-20 17:03 ` |FAILURE| " dpdklab
2024-03-20 17:03 ` |SUCCESS| " dpdklab
2024-03-20 17:03 ` |FAILURE| " dpdklab
2024-03-20 17:03 ` |SUCCESS| " dpdklab
2024-03-20 17:03 ` |FAILURE| " dpdklab
2024-03-20 17:03 ` |SUCCESS| " dpdklab
2024-03-20 17:04 ` |FAILURE| " dpdklab
2024-03-20 17:04 ` dpdklab
2024-03-20 17:05 ` 0-day Robot
2024-03-20 17:05 ` |SUCCESS| " dpdklab
2024-03-20 17:05 ` |FAILURE| " dpdklab
2024-03-20 17:06 ` |SUCCESS| " dpdklab
2024-03-20 17:06 ` dpdklab
2024-03-20 17:20 ` |FAILURE| " dpdklab
2024-03-20 17:21 ` |SUCCESS| " dpdklab
2024-03-20 17:25 ` |FAILURE| " dpdklab
2024-03-20 17:29 ` |SUCCESS| " dpdklab
2024-03-20 18:50 ` dpdklab
2024-03-21 11:37 ` dpdklab
2024-03-22  4:22 ` dpdklab
2024-03-22  5:02 ` 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=65fb167e.d40a0220.8a467.00ceSMTPIN_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).