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,
	Jochen Behrens <jochen.behrens@broadcom.com>
Subject: |FAILURE| pw139177 [PATCH] maintainers: change e-mail for vmxnet3
Date: Sat, 06 Apr 2024 05:42:13 -0700 (PDT)	[thread overview]
Message-ID: <66114325.050a0220.d343c.a43bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240405215619.1887731-1-jochen.behrens@broadcom.com>

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

_Testing issues_

Submitter: Jochen Behrens <jochen.behrens@broadcom.com>
Date: Friday, April 05 2024 21:56:19 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c

139177 --> testing fail

Test environment and result as below:

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

==== 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 :      29
+ Tests Failed :      36
+ ------------------------------------------------------- +
Test Failed
RTE>>
==== End log output ====

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

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

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

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

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

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

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

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-06 12:42 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240405215619.1887731-1-jochen.behrens@broadcom.com>
2024-04-05 21:33 ` |SUCCESS| " qemudev
2024-04-05 21:38 ` qemudev
2024-04-05 21:57 ` checkpatch
2024-04-05 22:44 ` 0-day Robot
2024-04-06 11:37 ` dpdklab
2024-04-06 11:38 ` dpdklab
2024-04-06 11:40 ` dpdklab
2024-04-06 11:41 ` dpdklab
2024-04-06 11:41 ` dpdklab
2024-04-06 11:42 ` dpdklab
2024-04-06 11:44 ` dpdklab
2024-04-06 11:45 ` dpdklab
2024-04-06 11:58 ` dpdklab
2024-04-06 11:58 ` dpdklab
2024-04-06 12:05 ` dpdklab
2024-04-06 12:05 ` dpdklab
2024-04-06 12:05 ` dpdklab
2024-04-06 12:07 ` dpdklab
2024-04-06 12:07 ` dpdklab
2024-04-06 12:07 ` dpdklab
2024-04-06 12:09 ` dpdklab
2024-04-06 12:09 ` dpdklab
2024-04-06 12:11 ` dpdklab
2024-04-06 12:13 ` dpdklab
2024-04-06 12:13 ` dpdklab
2024-04-06 12:13 ` dpdklab
2024-04-06 12:14 ` dpdklab
2024-04-06 12:15 ` dpdklab
2024-04-06 12:16 ` dpdklab
2024-04-06 12:19 ` dpdklab
2024-04-06 12:19 ` dpdklab
2024-04-06 12:19 ` dpdklab
2024-04-06 12:19 ` dpdklab
2024-04-06 12:20 ` dpdklab
2024-04-06 12:21 ` dpdklab
2024-04-06 12:21 ` |FAILURE| " dpdklab
2024-04-06 12:33 ` dpdklab
2024-04-06 12:33 ` |SUCCESS| " dpdklab
2024-04-06 12:34 ` |FAILURE| " dpdklab
2024-04-06 12:34 ` dpdklab
2024-04-06 12:35 ` |SUCCESS| " dpdklab
2024-04-06 12:35 ` dpdklab
2024-04-06 12:35 ` dpdklab
2024-04-06 12:35 ` dpdklab
2024-04-06 12:36 ` dpdklab
2024-04-06 12:39 ` |FAILURE| " dpdklab
2024-04-06 12:42 ` dpdklab [this message]
2024-04-06 12:43 ` |SUCCESS| " dpdklab
2024-04-06 12:44 ` dpdklab
2024-04-06 12:48 ` |FAILURE| " dpdklab
2024-04-06 12:49 ` |SUCCESS| " dpdklab
2024-04-06 12:50 ` dpdklab
2024-04-06 12:52 ` dpdklab
2024-04-06 12:53 ` dpdklab
2024-04-06 12:53 ` dpdklab
2024-04-06 12:53 ` |FAILURE| " dpdklab
2024-04-06 12:53 ` |SUCCESS| " dpdklab
2024-04-06 12:53 ` dpdklab
2024-04-06 12:53 ` dpdklab
2024-04-06 12:54 ` dpdklab
2024-04-06 12:54 ` dpdklab
2024-04-06 12:59 ` dpdklab
2024-04-06 12:59 ` dpdklab
2024-04-06 12:59 ` dpdklab
2024-04-06 13:00 ` dpdklab
2024-04-06 13:01 ` dpdklab
2024-04-06 13:17 ` dpdklab
2024-04-06 13:18 ` dpdklab
2024-04-06 13:18 ` dpdklab
2024-04-06 13:18 ` dpdklab
2024-04-06 13:19 ` dpdklab
2024-04-06 13:19 ` dpdklab
2024-04-06 13:20 ` dpdklab
2024-04-06 13:20 ` dpdklab
2024-04-06 13:20 ` dpdklab
2024-04-06 13:21 ` dpdklab
2024-04-06 13:21 ` |FAILURE| " dpdklab
2024-04-06 13:23 ` |SUCCESS| " dpdklab
2024-04-06 13:24 ` dpdklab
2024-04-06 13:25 ` dpdklab
2024-04-06 13:26 ` |FAILURE| " dpdklab
2024-04-06 13:27 ` |SUCCESS| " dpdklab
2024-04-06 13:27 ` dpdklab
2024-04-06 13:38 ` dpdklab
2024-04-06 13:39 ` dpdklab
2024-04-06 13:46 ` dpdklab
2024-04-06 13:58 ` dpdklab
2024-04-06 14:07 ` dpdklab
2024-04-06 14:11 ` dpdklab
2024-04-06 14:52 ` 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=66114325.050a0220.d343c.a43bSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=jochen.behrens@broadcom.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).