From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Mattias Ronnblom <mattias.ronnblom@ericsson.com>
Subject: |FAILURE| pw140311 [PATCH] event/dsw: support explicit release only
Date: Sat, 25 May 2024 09:22:05 -0700 (PDT) [thread overview]
Message-ID: <6652102d.d40a0220.1f917.f45eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240524192437.183960-1-mattias.ronnblom@ericsson.com>
Test-Label: iol-unit-arm64-testing
Test-Status: FAILURE
http://dpdk.org/patch/140311
_Testing issues_
Submitter: Mattias Ronnblom <mattias.ronnblom@ericsson.com>
Date: Friday, May 24 2024 19:24:37
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6f80df8cb0f889203d7cd27766abcc6ebc720e33
140311 --> testing fail
Test environment and result as below:
+-----------------------------+---------------------------+------------------------------+----------------+
| Environment | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest | dpdk_unit_test |
+=============================+===========================+==============================+================+
| Debian 12 (arm) | PASS | PASS | FAIL |
+-----------------------------+---------------------------+------------------------------+----------------+
| CentOS Stream 9 (ARM) | SKIPPED | SKIPPED | FAIL |
+-----------------------------+---------------------------+------------------------------+----------------+
| Debian 11 (Buster) (ARM) | SKIPPED | SKIPPED | FAIL |
+-----------------------------+---------------------------+------------------------------+----------------+
| 32-bit Ubuntu 20.04.4 (ARM) | SKIPPED | SKIPPED | PASS |
+-----------------------------+---------------------------+------------------------------+----------------+
| Fedora 37 (ARM) | SKIPPED | SKIPPED | FAIL |
+-----------------------------+---------------------------+------------------------------+----------------+
| Fedora 38 (ARM) | SKIPPED | SKIPPED | PASS |
+-----------------------------+---------------------------+------------------------------+----------------+
| Fedora 39 (ARM) | SKIPPED | SKIPPED | FAIL |
+-----------------------------+---------------------------+------------------------------+----------------+
==== 20 line log output for Fedora 39 (ARM) (dpdk_unit_test): ====
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
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
32-bit Ubuntu 20.04.4 (ARM)
Kernel: 5.4.0-155-generic aarch64
Compiler: gcc 9.4
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
Fedora 39 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.2.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30010/
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-05-25 16:22 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240524192437.183960-1-mattias.ronnblom@ericsson.com>
2024-05-24 19:08 ` |SUCCESS| pw140311 [PATCH] event/dsw: support explicit release only mode qemudev
2024-05-24 19:12 ` qemudev
2024-05-24 19:35 ` |WARNING| " checkpatch
2024-05-24 20:23 ` |FAILURE| " 0-day Robot
2024-05-25 15:20 ` |SUCCESS| pw140311 [PATCH] event/dsw: support explicit release only dpdklab
2024-05-25 15:22 ` dpdklab
2024-05-25 15:22 ` dpdklab
2024-05-25 15:23 ` dpdklab
2024-05-25 15:23 ` dpdklab
2024-05-25 15:25 ` dpdklab
2024-05-25 15:28 ` dpdklab
2024-05-25 15:41 ` dpdklab
2024-05-25 15:42 ` dpdklab
2024-05-25 15:42 ` dpdklab
2024-05-25 15:43 ` dpdklab
2024-05-25 15:43 ` dpdklab
2024-05-25 15:43 ` dpdklab
2024-05-25 15:44 ` dpdklab
2024-05-25 15:44 ` dpdklab
2024-05-25 15:44 ` dpdklab
2024-05-25 15:44 ` dpdklab
2024-05-25 15:45 ` dpdklab
2024-05-25 15:45 ` dpdklab
2024-05-25 15:45 ` dpdklab
2024-05-25 15:45 ` dpdklab
2024-05-25 15:46 ` dpdklab
2024-05-25 15:50 ` dpdklab
2024-05-25 15:52 ` dpdklab
2024-05-25 15:52 ` dpdklab
2024-05-25 15:53 ` dpdklab
2024-05-25 15:54 ` dpdklab
2024-05-25 15:54 ` dpdklab
2024-05-25 15:54 ` dpdklab
2024-05-25 15:55 ` dpdklab
2024-05-25 15:55 ` dpdklab
2024-05-25 15:55 ` dpdklab
2024-05-25 15:55 ` dpdklab
2024-05-25 15:55 ` dpdklab
2024-05-25 15:56 ` dpdklab
2024-05-25 15:56 ` |FAILURE| " dpdklab
2024-05-25 15:57 ` |SUCCESS| " dpdklab
2024-05-25 15:57 ` dpdklab
2024-05-25 15:58 ` |FAILURE| " dpdklab
2024-05-25 15:58 ` |SUCCESS| " dpdklab
2024-05-25 15:59 ` |FAILURE| " dpdklab
2024-05-25 16:01 ` dpdklab
2024-05-25 16:02 ` dpdklab
2024-05-25 16:04 ` |SUCCESS| " dpdklab
2024-05-25 16:04 ` dpdklab
2024-05-25 16:07 ` |FAILURE| " dpdklab
2024-05-25 16:10 ` |SUCCESS| " dpdklab
2024-05-25 16:14 ` dpdklab
2024-05-25 16:16 ` dpdklab
2024-05-25 16:16 ` dpdklab
2024-05-25 16:18 ` dpdklab
2024-05-25 16:18 ` dpdklab
2024-05-25 16:18 ` dpdklab
2024-05-25 16:22 ` dpdklab [this message]
2024-05-25 16:23 ` dpdklab
2024-05-25 16:23 ` dpdklab
2024-05-25 16:23 ` dpdklab
2024-05-25 16:24 ` dpdklab
2024-05-25 16:27 ` dpdklab
2024-05-25 16:30 ` dpdklab
2024-05-25 16:31 ` dpdklab
2024-05-25 16:31 ` dpdklab
2024-05-25 16:32 ` dpdklab
2024-05-25 16:32 ` dpdklab
2024-05-25 16:32 ` |FAILURE| " dpdklab
2024-05-25 16:33 ` |SUCCESS| " dpdklab
2024-05-25 16:34 ` dpdklab
2024-05-25 16:35 ` |FAILURE| " dpdklab
2024-05-25 16:37 ` |SUCCESS| " dpdklab
2024-05-25 16:37 ` |FAILURE| " dpdklab
2024-05-25 16:39 ` dpdklab
2024-05-25 16:42 ` |SUCCESS| " dpdklab
2024-05-25 16:42 ` dpdklab
2024-05-25 16:43 ` dpdklab
2024-05-25 16:46 ` dpdklab
2024-05-25 16:48 ` dpdklab
2024-05-25 16:48 ` dpdklab
2024-05-25 16:48 ` dpdklab
2024-05-25 16:48 ` dpdklab
2024-05-25 16:51 ` dpdklab
2024-05-25 16:52 ` dpdklab
2024-05-25 16:52 ` dpdklab
2024-05-25 16:55 ` dpdklab
2024-05-25 18:28 ` dpdklab
2024-05-25 18:34 ` dpdklab
2024-05-28 21:03 ` dpdklab
2024-05-28 21:39 ` 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=6652102d.d40a0220.1f917.f45eSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=mattias.ronnblom@ericsson.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).