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,
	Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Subject: |FAILURE| pw138119 [PATCH] crypto/qat: fix ccm null aad pointer segf
Date: Fri, 08 Mar 2024 03:42:14 -0800 (PST)	[thread overview]
Message-ID: <65eaf996.050a0220.6baa.2230SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240308082512.5226-1-arkadiuszx.kusztal@intel.com>

Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/138119

_Testing issues_

Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Friday, March 08 2024 08:25:12 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:4877d26a37d3bb515fc714b260066c0cac1985cf

138119 --> testing fail

Test environment and result as below:

+------------------+----------------+
|   Environment    | dpdk_unit_test |
+==================+================+
| CentOS Stream 9  | PASS           |
+------------------+----------------+
| Debian Bullseye  | PASS           |
+------------------+----------------+
| Debian 12 (arm)  | FAIL           |
+------------------+----------------+
| Fedora 38        | PASS           |
+------------------+----------------+
| Ubuntu 20.04     | PASS           |
+------------------+----------------+
| Ubuntu 22.04     | PASS           |
+------------------+----------------+
| CentOS Stream 8  | PASS           |
+------------------+----------------+
| Fedora 37        | PASS           |
+------------------+----------------+
| RHEL8            | PASS           |
+------------------+----------------+
| openSUSE Leap 15 | PASS           |
+------------------+----------------+

==== 20 line log output for Debian 12 (arm) (dpdk_unit_test): ====
Installing symlink pointing to librte_event_opdl.so.24 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_event_opdl.so
Installing symlink pointing to librte_event_skeleton.so.24.1 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_event_skeleton.so.24
Installing symlink pointing to librte_event_skeleton.so.24 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_event_skeleton.so
Installing symlink pointing to librte_event_sw.so.24.1 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_event_sw.so.24
Installing symlink pointing to librte_event_sw.so.24 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_event_sw.so
Installing symlink pointing to librte_event_octeontx.so.24.1 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_event_octeontx.so.24
Installing symlink pointing to librte_event_octeontx.so.24 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_event_octeontx.so
Installing symlink pointing to librte_baseband_acc.so.24.1 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_baseband_acc.so.24
Installing symlink pointing to librte_baseband_acc.so.24 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_baseband_acc.so
Installing symlink pointing to librte_baseband_fpga_5gnr_fec.so.24.1 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_baseband_fpga_5gnr_fec.so.24
Installing symlink pointing to librte_baseband_fpga_5gnr_fec.so.24 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_baseband_fpga_5gnr_fec.so
Installing symlink pointing to librte_baseband_fpga_lte_fec.so.24.1 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_baseband_fpga_lte_fec.so.24
Installing symlink pointing to librte_baseband_fpga_lte_fec.so.24 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_baseband_fpga_lte_fec.so
Installing symlink pointing to librte_baseband_la12xx.so.24.1 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_baseband_la12xx.so.24
Installing symlink pointing to librte_baseband_la12xx.so.24 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_baseband_la12xx.so
Installing symlink pointing to librte_baseband_null.so.24.1 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_baseband_null.so.24
Installing symlink pointing to librte_baseband_null.so.24 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_baseband_null.so
Installing symlink pointing to librte_baseband_turbo_sw.so.24.1 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_baseband_turbo_sw.so.24
Installing symlink pointing to librte_baseband_turbo_sw.so.24 to /usr/local/lib/x86_64-linux-gnu/dpdk/pmds-24.1/librte_baseband_turbo_sw.so
Running custom install script '/bin/sh /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/config/../buildtools/symlink-drivers-solibs.sh lib/x86_64-linux-gnu dpdk/pmds-24.1'
==== End log output ====

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

Debian Bullseye
	Kernel: 5.4.0-122-generic
	Compiler: gcc 10.2.1-6

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

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

Ubuntu 20.04
	Kernel: 5.4.0-153-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

Ubuntu 22.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.0

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

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

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-08 11:42 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240308082512.5226-1-arkadiuszx.kusztal@intel.com>
2024-03-08  8:05 ` |SUCCESS| pw138119 [PATCH] crypto/qat: fix ccm null aad pointer segfault qemudev
2024-03-08  8:10 ` qemudev
2024-03-08  8:26 ` checkpatch
2024-03-08  9:24 ` 0-day Robot
2024-03-08 10:56 ` |SUCCESS| pw138119 [PATCH] crypto/qat: fix ccm null aad pointer segf dpdklab
2024-03-08 10:58 ` dpdklab
2024-03-08 11:04 ` dpdklab
2024-03-08 11:05 ` dpdklab
2024-03-08 11:23 ` dpdklab
2024-03-08 11:23 ` dpdklab
2024-03-08 11:24 ` dpdklab
2024-03-08 11:25 ` dpdklab
2024-03-08 11:25 ` dpdklab
2024-03-08 11:27 ` dpdklab
2024-03-08 11:27 ` dpdklab
2024-03-08 11:27 ` dpdklab
2024-03-08 11:28 ` dpdklab
2024-03-08 11:31 ` dpdklab
2024-03-08 11:32 ` dpdklab
2024-03-08 11:32 ` dpdklab
2024-03-08 11:36 ` dpdklab
2024-03-08 11:36 ` dpdklab
2024-03-08 11:37 ` dpdklab
2024-03-08 11:37 ` dpdklab
2024-03-08 11:37 ` dpdklab
2024-03-08 11:37 ` dpdklab
2024-03-08 11:37 ` dpdklab
2024-03-08 11:37 ` dpdklab
2024-03-08 11:37 ` dpdklab
2024-03-08 11:38 ` dpdklab
2024-03-08 11:38 ` |FAILURE| " dpdklab
2024-03-08 11:38 ` |SUCCESS| " dpdklab
2024-03-08 11:38 ` dpdklab
2024-03-08 11:39 ` dpdklab
2024-03-08 11:39 ` dpdklab
2024-03-08 11:39 ` dpdklab
2024-03-08 11:39 ` dpdklab
2024-03-08 11:39 ` |FAILURE| " dpdklab
2024-03-08 11:41 ` |SUCCESS| " dpdklab
2024-03-08 11:41 ` |FAILURE| " dpdklab
2024-03-08 11:41 ` |SUCCESS| " dpdklab
2024-03-08 11:42 ` dpdklab
2024-03-08 11:42 ` dpdklab [this message]
2024-03-08 11:42 ` dpdklab
2024-03-08 11:42 ` |FAILURE| " dpdklab
2024-03-08 11:42 ` |SUCCESS| " dpdklab
2024-03-08 11:43 ` dpdklab
2024-03-08 11:46 ` dpdklab
2024-03-08 11:46 ` dpdklab
2024-03-08 11:46 ` |FAILURE| " dpdklab
2024-03-08 11:46 ` dpdklab
2024-03-08 11:46 ` dpdklab
2024-03-08 11:46 ` dpdklab
2024-03-08 11:47 ` |SUCCESS| " dpdklab
2024-03-08 11:47 ` dpdklab
2024-03-08 11:48 ` |FAILURE| " dpdklab
2024-03-08 11:50 ` |SUCCESS| " dpdklab
2024-03-08 11:53 ` |FAILURE| " dpdklab
2024-03-08 12:12 ` dpdklab
2024-03-08 12:13 ` |SUCCESS| " dpdklab
2024-03-08 12:38 ` dpdklab
2024-03-08 12:59 ` dpdklab
2024-03-08 12:59 ` dpdklab
2024-03-08 13:11 ` dpdklab
2024-03-08 13:20 ` dpdklab
2024-03-08 13:23 ` dpdklab
2024-03-08 13:55 ` dpdklab
2024-03-13  1:26 ` dpdklab
2024-03-13  2: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=65eaf996.050a0220.6baa.2230SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=arkadiuszx.kusztal@intel.com \
    --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).