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,
	Sivaramakrishnan Venkat <venkatx.sivaramakrishnan@intel.com>
Subject: |FAILURE| pw136132 [PATCH] [v1] doc: update guideline for fix commit
Date: Thu, 25 Jan 2024 06:58:07 -0800 (PST)	[thread overview]
Message-ID: <65b276ff.050a0220.cd546.018dSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing issues_

Submitter: Sivaramakrishnan Venkat <venkatx.sivaramakrishnan@intel.com>
Date: Thursday, January 25 2024 03:39:00 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2ecc673e5e9a19850ba76d6a976596890f2dade1

136132 --> testing fail

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Fedora 37           | FAIL           |
+---------------------+----------------+
| Debian Buster       | PASS           |
+---------------------+----------------+
| openSUSE Leap 15    | PASS           |
+---------------------+----------------+
| RHEL8               | PASS           |
+---------------------+----------------+
| Fedora 38           | PASS           |
+---------------------+----------------+

==== 20 line log output for Fedora 37 (dpdk_unit_test): ====
100/110 DPDK:fast-tests / telemetry_data_autotest  OK       0.22 s
101/110 DPDK:fast-tests / telemetry_json_autotest  OK       0.25 s
102/110 DPDK:fast-tests / thash_autotest        OK       0.22 s
103/110 DPDK:fast-tests / threads_autotest      OK       0.37 s
104/110 DPDK:fast-tests / ticketlock_autotest   OK       0.30 s
105/110 DPDK:fast-tests / timer_autotest        OK       2.56 s
106/110 DPDK:fast-tests / trace_autotest        OK       0.25 s
107/110 DPDK:fast-tests / trace_autotest_with_traces  OK       0.24 s
108/110 DPDK:fast-tests / vdev_autotest         OK       0.22 s
109/110 DPDK:fast-tests / version_autotest      OK       0.22 s
110/110 DPDK:fast-tests / telemetry_all         SKIP     0.01 s

Ok:                   99
Expected Fail:         0
Fail:                  1
Unexpected Pass:       0
Skipped:              10
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)

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

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

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

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

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

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

Fedora 38
	Kernel: Depends on container host
	Compiler: clang 16.0.3

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-25 14:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-25 14:58 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-25 15:17 dpdklab
2024-01-25 15:15 dpdklab
2024-01-25 15:00 dpdklab
2024-01-25 14:58 dpdklab
2024-01-25 14:55 dpdklab
2024-01-25 14:51 dpdklab
2024-01-25 14:41 dpdklab
2024-01-25 14:40 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=65b276ff.050a0220.cd546.018dSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=venkatx.sivaramakrishnan@intel.com \
    /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).