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, Brian Dooley <brian.dooley@intel.com>
Subject: |WARNING| pw137426 [PATCH] [v4] crypto/ipsec_mb: unified IPsec MB in
Date: Wed, 28 Feb 2024 06:52:14 -0800 (PST)	[thread overview]
Message-ID: <65df489e.810a0220.7e8c8.4e1bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240228113301.934291-1-brian.dooley@intel.com>

Test-Label: iol-unit-arm64-testing
Test-Status: WARNING
http://dpdk.org/patch/137426

_Testing issues_

Submitter: Brian Dooley <brian.dooley@intel.com>
Date: Wednesday, February 28 2024 11:33:01 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049

137426 --> testing fail

Test environment and result as below:

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

==== 20 line log output for Debian 12 (arm) (cryptodev_sw_snow3g_autotest): ====
[3127/3131] Compiling C object app/dpdk-test.p/test_test_trace_register.c.o
[3128/3131] Compiling C object app/dpdk-test.p/test_test_trace_perf.c.o
[3129/3131] Compiling C object app/dpdk-test.p/test_test_vdev.c.o
[3130/3131] Compiling C object app/dpdk-test.p/test_test_version.c.o
[3131/3131] Linking target app/dpdk-test
ninja: no work to do.
ninja: Entering directory `/home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/build'
ninja: no work to do.
1/1 DPDK:driver-tests / cryptodev_sw_snow3g_autotest FAIL             1.22s   (exit status 255 or signal 127 SIGinvalid)
>>> DPDK_TEST=cryptodev_sw_snow3g_autotest MALLOC_PERTURB_=95 /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/build/app/dpdk-test --no-huge --no-pci --vdev=crypto_snow3g


Ok:                 0
Expected Fail:      0
Fail:               1
Unexpected Pass:    0
Skipped:            0
Timeout:            0

Full log written to /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/build/meson-logs/testlog.txt
==== End log output ====

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

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

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

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

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

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

Fedora 38 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.3

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-02-28 14:52 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240228113301.934291-1-brian.dooley@intel.com>
2024-02-28 11:10 ` |SUCCESS| pw137426 [PATCH v4] crypto/ipsec_mb: unified IPsec MB interface qemudev
2024-02-28 11:14 ` qemudev
2024-02-28 11:33 ` checkpatch
2024-02-28 12:25 ` 0-day Robot
2024-02-28 13:12 ` |SUCCESS| pw137426 [PATCH] [v4] crypto/ipsec_mb: unified IPsec MB in dpdklab
2024-02-28 13:18 ` dpdklab
2024-02-28 13:26 ` dpdklab
2024-02-28 13:42 ` dpdklab
2024-02-28 13:44 ` dpdklab
2024-02-28 13:45 ` dpdklab
2024-02-28 13:45 ` dpdklab
2024-02-28 13:45 ` dpdklab
2024-02-28 13:46 ` dpdklab
2024-02-28 13:49 ` dpdklab
2024-02-28 13:49 ` dpdklab
2024-02-28 13:50 ` dpdklab
2024-02-28 13:50 ` dpdklab
2024-02-28 13:51 ` dpdklab
2024-02-28 13:51 ` dpdklab
2024-02-28 14:08 ` dpdklab
2024-02-28 14:23 ` dpdklab
2024-02-28 14:28 ` dpdklab
2024-02-28 14:28 ` dpdklab
2024-02-28 14:30 ` |WARNING| " dpdklab
2024-02-28 14:31 ` |SUCCESS| " dpdklab
2024-02-28 14:31 ` |WARNING| " dpdklab
2024-02-28 14:32 ` |SUCCESS| " dpdklab
2024-02-28 14:32 ` dpdklab
2024-02-28 14:32 ` dpdklab
2024-02-28 14:33 ` |WARNING| " dpdklab
2024-02-28 14:33 ` |SUCCESS| " dpdklab
2024-02-28 14:34 ` dpdklab
2024-02-28 14:34 ` dpdklab
2024-02-28 14:34 ` |WARNING| " dpdklab
2024-02-28 14:34 ` |SUCCESS| " dpdklab
2024-02-28 14:35 ` dpdklab
2024-02-28 14:35 ` dpdklab
2024-02-28 14:35 ` dpdklab
2024-02-28 14:35 ` dpdklab
2024-02-28 14:36 ` dpdklab
2024-02-28 14:36 ` dpdklab
2024-02-28 14:36 ` |WARNING| " dpdklab
2024-02-28 14:36 ` dpdklab
2024-02-28 14:37 ` dpdklab
2024-02-28 14:37 ` |SUCCESS| " dpdklab
2024-02-28 14:37 ` dpdklab
2024-02-28 14:38 ` dpdklab
2024-02-28 14:38 ` dpdklab
2024-02-28 14:38 ` dpdklab
2024-02-28 14:38 ` dpdklab
2024-02-28 14:38 ` dpdklab
2024-02-28 14:42 ` |WARNING| " dpdklab
2024-02-28 14:42 ` |SUCCESS| " dpdklab
2024-02-28 14:43 ` dpdklab
2024-02-28 14:43 ` dpdklab
2024-02-28 14:43 ` dpdklab
2024-02-28 14:44 ` dpdklab
2024-02-28 14:44 ` dpdklab
2024-02-28 14:44 ` dpdklab
2024-02-28 14:45 ` dpdklab
2024-02-28 14:45 ` dpdklab
2024-02-28 14:51 ` |WARNING| " dpdklab
2024-02-28 14:52 ` dpdklab [this message]
2024-02-28 15:56 ` |SUCCESS| " dpdklab
2024-02-28 18:03 ` dpdklab
2024-02-28 19:52 ` dpdklab
2024-02-28 20:34 ` dpdklab
2024-02-29 11:01 ` dpdklab
2024-02-29 22:36 ` |FAILURE| " dpdklab
2024-02-29 22:40 ` |SUCCESS| " dpdklab
2024-02-29 22:50 ` dpdklab
2024-02-29 22:53 ` dpdklab
2024-03-01 17:37 ` dpdklab
2024-03-01 18:05 ` |FAILURE| " dpdklab
2024-03-01 18:39 ` |SUCCESS| " dpdklab
2024-03-05 20:07 ` dpdklab
2024-03-06  4:05 ` |FAILURE| " 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=65df489e.810a0220.7e8c8.4e1bSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=brian.dooley@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).