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 16:25:39 +0000 (UTC)	[thread overview]
Message-ID: <20221219162539.549FC6008E@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

Test-Label: iol-x86_64-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 |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| Ubuntu 22.04        | FAIL           |
+---------------------+----------------+
| openSUSE Leap 15    | FAIL           |
+---------------------+----------------+
| RHEL 7              | FAIL           |
+---------------------+----------------+
| CentOS Stream 8     | FAIL           |
+---------------------+----------------+
| Ubuntu 20.04        | FAIL           |
+---------------------+----------------+
| CentOS Stream 9     | FAIL           |
+---------------------+----------------+
| Debian Buster       | FAIL           |
+---------------------+----------------+
| Debian Bullseye     | FAIL           |
+---------------------+----------------+
| RHEL8               | FAIL           |
+---------------------+----------------+

==== 20 line log output for RHEL8 (dpdk_unit_test): ====
60/70 DPDK:fast-tests / trace_autotest_with_traces  OK       0.30 s
61/70 DPDK:fast-tests / metrics_autotest      OK       0.43 s
62/70 DPDK:fast-tests / telemetry_json_autotest  OK       0.48 s
63/70 DPDK:fast-tests / telemetry_data_autotest  OK       0.55 s
64/70 DPDK:fast-tests / table_autotest        OK      18.41 s
65/70 DPDK:fast-tests / ring_pmd_autotest     OK       0.45 s
66/70 DPDK:fast-tests / bitratestats_autotest  OK       0.86 s
67/70 DPDK:fast-tests / latencystats_autotest  OK       0.41 s
68/70 DPDK:fast-tests / pdump_autotest        OK       1.78 s
69/70 DPDK:fast-tests / vdev_autotest         OK       0.43 s
70/70 DPDK:fast-tests / telemetry_all         SKIP     0.01 s

Ok:                   65
Expected Fail:         0
Fail:                  1
Unexpected Pass:       0
Skipped:               4
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 ====

Windows Server 2019
	Kernel: 10.0
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

Ubuntu 22.04
	Kernel: Container Host Kernel
	Compiler: gcc 11.3.1-2

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

RHEL 7
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)

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

Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

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

Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

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

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

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 16:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 16:25 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
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:52 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=20221219162539.549FC6008E@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).