automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Amit Prakash Shukla <amitprakashs@marvell.com>
Subject: |FAILURE| pw121037 [PATCH] eventdev: add trace points
Date: Mon, 19 Dec 2022 15:52:37 +0000 (UTC)	[thread overview]
Message-ID: <20221219155237.3CD3B6008E@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 2735 bytes --]

Test-Label: iol-aarch64-unit-testing
Test-Status: FAILURE
http://dpdk.org/patch/121037

_Testing issues_

Submitter: Amit Prakash Shukla <amitprakashs@marvell.com>
Date: Monday, December 19 2022 14:11:14 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c581c49cd3fcaff596fbe566e270b442e6326c79

121037 --> testing fail

Test environment and result as below:

+-------------------------------+----------------+--------------+
|          Environment          | dpdk_unit_test | lpm_autotest |
+===============================+================+==============+
| Ubuntu 20.04 ARM GCC Native   | FAIL           | SKIPPED      |
+-------------------------------+----------------+--------------+
| Ubuntu 20.04 ARM Clang Native | FAIL           | SKIPPED      |
+-------------------------------+----------------+--------------+
| Ubuntu 20.04 ARM SVE          | SKIPPED        | PASS         |
+-------------------------------+----------------+--------------+

==== 20 line log output for Ubuntu 20.04 ARM Clang Native (dpdk_unit_test): ====
96/103 DPDK:fast-tests / ring_pmd_autotest              OK               0.14s
97/103 DPDK:fast-tests / event_eth_tx_adapter_autotest  FAIL             0.45s   killed by signal 11 SIGSEGV
>>> DPDK_TEST=event_eth_tx_adapter_autotest MALLOC_PERTURB_=44 /home-local/jenkins-local/jenkins-agent/workspace/Generic-VM-Unit-Test-DPDK/dpdk/build/app/test/dpdk-test --file-prefix=event_eth_tx_adapter_autotest '-l 0-3'

98/103 DPDK:fast-tests / bitratestats_autotest          OK               0.14s
99/103 DPDK:fast-tests / latencystats_autotest          OK               0.14s
100/103 DPDK:fast-tests / pdump_autotest                 OK               5.23s
101/103 DPDK:fast-tests / vdev_autotest                  OK               0.14s
102/103 DPDK:fast-tests / compressdev_autotest           SKIP             0.24s   exit status 77
103/103 DPDK:fast-tests / telemetry_all                  OK              13.21s


Ok:                 95
Expected Fail:      0
Fail:               2
Unexpected Pass:    0
Skipped:            6
Timeout:            0

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

Ubuntu 20.04 ARM GCC Native
	Kernel: 5.4.0-53-generic
	Compiler: gcc 9.3

Ubuntu 20.04 ARM Clang Native
	Kernel: 5.4.0-53-generic
	Compiler: clang 10.0.0-4ubuntu1

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/24770/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2022-12-19 15:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 15:52 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-12-19 16:25 dpdklab
2022-12-19 16:25 dpdklab
2022-12-19 16:22 dpdklab
2022-12-19 16:18 dpdklab
2022-12-19 16:17 dpdklab
2022-12-19 16:13 dpdklab
2022-12-19 16:12 dpdklab
2022-12-19 16:11 dpdklab
2022-12-19 16:10 dpdklab
2022-12-19 16:08 dpdklab
2022-12-19 16:03 dpdklab
2022-12-19 15:51 dpdklab
2022-12-19 15:36 dpdklab
     [not found] <20221219141114.1687608-1-amitprakashs@marvell.com>
2022-12-19 14:07 ` qemudev
2022-12-19 14:58 ` 0-day Robot

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=20221219155237.3CD3B6008E@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=amitprakashs@marvell.com \
    --cc=david.marchand@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).