automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Michael Baum <michaelba@nvidia.com>,
	dpdk-test-reports@iol.unh.edu,
	Michael Baum <michaelba@nvidia.com>
Subject: |FAILURE| pw134735-134736 [PATCH] [v3,2/2] app/testpmd: add random i
Date: Thu, 30 Nov 2023 15:52:56 -0800 (PST)	[thread overview]
Message-ID: <65692058.650a0220.9a511.1c23SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing issues_

Submitter: Michael Baum <michaelba@nvidia.com>
Date: Thursday, November 30 2023 16:32:15 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:eeb0605f118dae66e80faa44f7b3e88748032353

134735-134736 --> testing fail

Test environment and result as below:

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

==== 20 line log output for Fedora 38 (ARM) (dpdk_unit_test): ====
100/110 DPDK:fast-tests / telemetry_data_autotest  OK       0.29 s
101/110 DPDK:fast-tests / telemetry_json_autotest  OK       0.29 s
102/110 DPDK:fast-tests / thash_autotest        OK       0.29 s
103/110 DPDK:fast-tests / threads_autotest      OK       0.44 s
104/110 DPDK:fast-tests / ticketlock_autotest   OK       0.34 s
105/110 DPDK:fast-tests / timer_autotest        OK       3.34 s
106/110 DPDK:fast-tests / trace_autotest        OK       0.34 s
107/110 DPDK:fast-tests / trace_autotest_with_traces  OK       0.28 s
108/110 DPDK:fast-tests / vdev_autotest         OK       0.29 s
109/110 DPDK:fast-tests / version_autotest      OK       0.29 s
110/110 DPDK:fast-tests / telemetry_all         SKIP     0.02 s

Ok:                  102
Expected Fail:         0
Fail:                  1
Unexpected Pass:       0
Skipped:               7
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 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

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

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

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-11-30 23:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-30 23:52 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-30 23:45 dpdklab
2023-11-30 23:24 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=65692058.650a0220.9a511.1c23SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=michaelba@nvidia.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).