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, Maryam Tahhan <mtahhan@redhat.com>
Subject: |FAILURE| pw139186-139188 [PATCH] [v14,3/3] net/af_xdp: support AF_X
Date: Mon, 08 Apr 2024 11:56:33 -0700 (PDT)	[thread overview]
Message-ID: <66143de1.050a0220.e518e.d5d8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240408130924.232154-4-mtahhan@redhat.com>

Test-Label: iol-unit-arm64-testing
Test-Status: FAILURE
http://dpdk.org/patch/139188

_Testing issues_

Submitter: Maryam Tahhan <mtahhan@redhat.com>
Date: Monday, April 08 2024 13:09:22 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c

139186-139188 --> testing fail

Test environment and result as below:

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

==== 20 line log output for 32-bit Ubuntu 20.04.4 (ARM) (dpdk_unit_test): ====
+ TestCase [57] : test_broadcast_tx_burst failed
+ TestCase [58] : test_broadcast_tx_burst_slave_tx_fail failed
+ TestCase [59] : test_broadcast_rx_burst failed
+ TestCase [60] : test_broadcast_verify_promiscuous_enable_disable failed
+ TestCase [61] : test_broadcast_verify_mac_assignment failed
+ TestCase [62] : test_broadcast_verify_slave_link_status_change_behaviour failed
+ TestCase [63] : test_reconfigure_bonded_device failed
+ TestCase [64] : test_close_bonded_device succeeded
+ ------------------------------------------------------- +
+ Test Suite Summary : Link Bonding Unit Test Suite
+ ------------------------------------------------------- +
+ Tests Total :       65
+ Tests Skipped :      0
+ Tests Executed :    65
+ Tests Unsupported:   0
+ Tests Passed :      44
+ Tests Failed :      21
+ ------------------------------------------------------- +
Test Failed
RTE>>
==== End log output ====

Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

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

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

32-bit Ubuntu 20.04.4 (ARM)
	Kernel: 5.4.0-155-generic aarch64
	Compiler: gcc 9.4

Fedora 39 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Ubuntu 20.04 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 9.4.0

Fedora 39 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-04-08 18:56 UTC|newest]

Thread overview: 118+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240408130924.232154-4-mtahhan@redhat.com>
2024-04-08 12:46 ` |SUCCESS| pw139186-139188 [v14 3/3] net/af_xdp: support AF_XDP DP pinned maps qemudev
2024-04-08 12:51 ` qemudev
2024-04-08 13:11 ` |SUCCESS| pw139188 " checkpatch
2024-04-08 14:04 ` 0-day Robot
2024-04-08 17:59 ` |SUCCESS| pw139186-139188 [PATCH] [v14,3/3] net/af_xdp: support AF_X dpdklab
2024-04-08 18:00 ` dpdklab
2024-04-08 18:00 ` dpdklab
2024-04-08 18:00 ` dpdklab
2024-04-08 18:01 ` dpdklab
2024-04-08 18:01 ` dpdklab
2024-04-08 18:02 ` dpdklab
2024-04-08 18:10 ` dpdklab
2024-04-08 18:18 ` dpdklab
2024-04-08 18:18 ` dpdklab
2024-04-08 18:18 ` dpdklab
2024-04-08 18:19 ` dpdklab
2024-04-08 18:19 ` dpdklab
2024-04-08 18:19 ` dpdklab
2024-04-08 18:20 ` dpdklab
2024-04-08 18:20 ` dpdklab
2024-04-08 18:20 ` dpdklab
2024-04-08 18:21 ` dpdklab
2024-04-08 18:21 ` dpdklab
2024-04-08 18:22 ` dpdklab
2024-04-08 18:22 ` dpdklab
2024-04-08 18:22 ` dpdklab
2024-04-08 18:22 ` dpdklab
2024-04-08 18:22 ` dpdklab
2024-04-08 18:23 ` dpdklab
2024-04-08 18:23 ` dpdklab
2024-04-08 18:23 ` dpdklab
2024-04-08 18:23 ` dpdklab
2024-04-08 18:24 ` dpdklab
2024-04-08 18:24 ` dpdklab
2024-04-08 18:24 ` dpdklab
2024-04-08 18:24 ` dpdklab
2024-04-08 18:24 ` dpdklab
2024-04-08 18:24 ` dpdklab
2024-04-08 18:25 ` dpdklab
2024-04-08 18:25 ` dpdklab
2024-04-08 18:25 ` dpdklab
2024-04-08 18:25 ` dpdklab
2024-04-08 18:26 ` dpdklab
2024-04-08 18:26 ` dpdklab
2024-04-08 18:26 ` dpdklab
2024-04-08 18:26 ` dpdklab
2024-04-08 18:27 ` dpdklab
2024-04-08 18:27 ` dpdklab
2024-04-08 18:27 ` dpdklab
2024-04-08 18:27 ` dpdklab
2024-04-08 18:28 ` dpdklab
2024-04-08 18:28 ` dpdklab
2024-04-08 18:28 ` dpdklab
2024-04-08 18:28 ` dpdklab
2024-04-08 18:28 ` dpdklab
2024-04-08 18:29 ` dpdklab
2024-04-08 18:29 ` dpdklab
2024-04-08 18:30 ` dpdklab
2024-04-08 18:30 ` dpdklab
2024-04-08 18:31 ` dpdklab
2024-04-08 18:31 ` dpdklab
2024-04-08 18:31 ` dpdklab
2024-04-08 18:32 ` dpdklab
2024-04-08 18:32 ` dpdklab
2024-04-08 18:32 ` dpdklab
2024-04-08 18:34 ` dpdklab
2024-04-08 18:35 ` |FAILURE| " dpdklab
2024-04-08 18:35 ` |SUCCESS| " dpdklab
2024-04-08 18:35 ` dpdklab
2024-04-08 18:35 ` dpdklab
2024-04-08 18:35 ` dpdklab
2024-04-08 18:35 ` dpdklab
2024-04-08 18:35 ` dpdklab
2024-04-08 18:35 ` dpdklab
2024-04-08 18:36 ` |FAILURE| " dpdklab
2024-04-08 18:36 ` |SUCCESS| " dpdklab
2024-04-08 18:36 ` |FAILURE| " dpdklab
2024-04-08 18:37 ` |SUCCESS| " dpdklab
2024-04-08 18:38 ` dpdklab
2024-04-08 18:55 ` dpdklab
2024-04-08 18:56 ` dpdklab
2024-04-08 18:56 ` dpdklab [this message]
2024-04-08 19:02 ` dpdklab
2024-04-08 19:06 ` dpdklab
2024-04-08 19:07 ` dpdklab
2024-04-08 19:10 ` dpdklab
2024-04-08 19:14 ` dpdklab
2024-04-08 19:18 ` |FAILURE| " dpdklab
2024-04-08 19:41 ` |SUCCESS| " dpdklab
2024-04-08 19:43 ` dpdklab
2024-04-08 19:46 ` dpdklab
2024-04-18 22:40 ` |FAILURE| " dpdklab
2024-04-18 22:41 ` |SUCCESS| " dpdklab
2024-04-18 22:41 ` dpdklab
2024-04-18 22:41 ` |FAILURE| " dpdklab
2024-04-18 22:41 ` |SUCCESS| " dpdklab
2024-04-18 22:44 ` dpdklab
2024-04-18 22:45 ` dpdklab
2024-04-18 22:45 ` dpdklab
2024-04-18 22:48 ` dpdklab
2024-04-18 22:51 ` |FAILURE| " dpdklab
2024-04-18 22:51 ` dpdklab
2024-04-18 22:52 ` dpdklab
2024-04-18 22:52 ` |SUCCESS| " dpdklab
2024-04-18 22:55 ` dpdklab
2024-04-18 22:55 ` dpdklab
2024-04-18 22:56 ` |FAILURE| " dpdklab
2024-04-18 22:57 ` |SUCCESS| " dpdklab
2024-04-18 22:59 ` dpdklab
2024-04-18 23:02 ` |FAILURE| " dpdklab
2024-04-18 23:03 ` dpdklab
2024-04-18 23:08 ` |SUCCESS| " dpdklab
2024-04-18 23:09 ` dpdklab
2024-04-18 23:12 ` dpdklab
2024-04-18 23:13 ` dpdklab
2024-04-18 23:19 ` dpdklab
2024-04-18 23:20 ` dpdklab
2024-04-18 23:25 ` 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=66143de1.050a0220.e518e.d5d8SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=mtahhan@redhat.com \
    --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).