automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Rahul Gupta <rahulgupt@linux.microsoft.com>,
	dpdk-test-reports@iol.unh.edu,
	Rahul Gupta <rahulgupt@linux.microsoft.com>
Subject: |FAILURE| pw135939 [PATCH] [v2] eal: refactor rte_eal_init into sub-
Date: Wed, 17 Jan 2024 13:33:09 -0800 (PST)	[thread overview]
Message-ID: <65a84795.d40a0220.6848a.7ca7SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing issues_

Submitter: Rahul Gupta <rahulgupt@linux.microsoft.com>
Date: Wednesday, January 17 2024 19:25:02 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:d4af9a82063e4c39568191eaa12955d3ca39581a

135939 --> testing fail

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | FAIL           |
+---------------------+----------------+
| Debian Buster       | FAIL           |
+---------------------+----------------+

==== 20 line log output for Debian Buster (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.22 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.22 s
105/110 DPDK:fast-tests / timer_autotest        OK       1.54 s
106/110 DPDK:fast-tests / trace_autotest        OK       0.22 s
107/110 DPDK:fast-tests / trace_autotest_with_traces  OK       0.22 s
108/110 DPDK:fast-tests / vdev_autotest         OK       0.22 s
109/110 DPDK:fast-tests / version_autotest      OK       0.21 s
110/110 DPDK:fast-tests / telemetry_all         SKIP     0.02 s

Ok:                   97
Expected Fail:         0
Fail:                  2
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 ====

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-17 21:33 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-17 21:33 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-18  0:43 dpdklab
2024-01-17 23:07 dpdklab
2024-01-17 22:56 dpdklab
2024-01-17 22:54 dpdklab
2024-01-17 22:47 dpdklab
2024-01-17 22:43 dpdklab
2024-01-17 22:42 dpdklab
2024-01-17 22:42 dpdklab
2024-01-17 22:41 dpdklab
2024-01-17 22:41 dpdklab
2024-01-17 22:39 dpdklab
2024-01-17 22:38 dpdklab
2024-01-17 22:36 dpdklab
2024-01-17 22:11 dpdklab
2024-01-17 22:06 dpdklab
2024-01-17 22:00 dpdklab
2024-01-17 21:59 dpdklab
2024-01-17 21:56 dpdklab
2024-01-17 21:54 dpdklab
2024-01-17 21:54 dpdklab
2024-01-17 21:53 dpdklab
2024-01-17 21:53 dpdklab
2024-01-17 21:52 dpdklab
2024-01-17 21:51 dpdklab
2024-01-17 21:51 dpdklab
2024-01-17 21:50 dpdklab
2024-01-17 21:50 dpdklab
2024-01-17 21:49 dpdklab
2024-01-17 21:33 dpdklab
2024-01-17 21:32 dpdklab
2024-01-17 21:27 dpdklab
2024-01-17 21:27 dpdklab
2024-01-17 21:24 dpdklab
2024-01-17 21:18 dpdklab
2024-01-17 21:17 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=65a84795.d40a0220.6848a.7ca7SMTPIN_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).