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,
	Rahul Gupta <rahulgupt@linux.microsoft.com>
Subject: |FAILURE| pw135991 [PATCH] [v3] eal: refactor rte_eal_init into sub-
Date: Fri, 19 Jan 2024 16:43:01 -0800 (PST)	[thread overview]
Message-ID: <65ab1715.920a0220.3606.2ce2SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing issues_

Submitter: Rahul Gupta <rahulgupt@linux.microsoft.com>
Date: Friday, January 19 2024 16:58:17 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:515e1a4f4cddd33fcb35328a73449d30a8edfaf6

135991 --> testing fail

Test environment and result as below:

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

==== 20 line log output for RHEL8 (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.26 s
102/110 DPDK:fast-tests / thash_autotest        OK       0.25 s
103/110 DPDK:fast-tests / threads_autotest      OK       0.37 s
104/110 DPDK:fast-tests / ticketlock_autotest   OK       0.22 s
105/110 DPDK:fast-tests / timer_autotest        OK       1.58 s
106/110 DPDK:fast-tests / trace_autotest        OK       0.23 s
107/110 DPDK:fast-tests / trace_autotest_with_traces  OK       0.22 s
108/110 DPDK:fast-tests / vdev_autotest         OK       0.29 s
109/110 DPDK:fast-tests / version_autotest      OK       0.22 s
110/110 DPDK:fast-tests / telemetry_all         SKIP     0.01 s

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

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 Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

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 Bullseye
	Kernel: 5.4.0-122-generic
	Compiler: gcc 10.2.1-6

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

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-20  0:43 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-20  0:43 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-22 17:25 dpdklab
2024-01-20  1:08 dpdklab
2024-01-20  1:08 dpdklab
2024-01-20  0:55 dpdklab
2024-01-20  0:43 dpdklab
2024-01-20  0:40 dpdklab
2024-01-20  0:27 dpdklab
2024-01-20  0:23 dpdklab
2024-01-20  0:16 dpdklab
2024-01-20  0:15 dpdklab
2024-01-20  0:14 dpdklab
2024-01-20  0:13 dpdklab
2024-01-20  0:11 dpdklab
2024-01-20  0:11 dpdklab
2024-01-20  0:10 dpdklab
2024-01-20  0:10 dpdklab
2024-01-20  0:10 dpdklab
2024-01-20  0:09 dpdklab
2024-01-20  0:09 dpdklab
2024-01-19 23:55 dpdklab
2024-01-19 23:54 dpdklab
2024-01-19 23:45 dpdklab
2024-01-19 23:44 dpdklab
2024-01-19 23:44 dpdklab
2024-01-19 23:43 dpdklab
2024-01-19 23:40 dpdklab
2024-01-19 23:31 dpdklab
2024-01-19 23:30 dpdklab
2024-01-19 23:30 dpdklab
2024-01-19 23:29 dpdklab
2024-01-19 23:20 dpdklab
2024-01-19 23:20 dpdklab
2024-01-19 23:18 dpdklab
2024-01-19 22:53 dpdklab
2024-01-19 22:50 dpdklab
2024-01-19 22:49 dpdklab
2024-01-19 22:28 dpdklab
2024-01-19 22:19 dpdklab
2024-01-19 22:19 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=65ab1715.920a0220.3606.2ce2SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=rahulgupt@linux.microsoft.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).