From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>, Li Zhang <lizh@nvidia.com>
Subject: |FAILURE| pw112375-112391 [PATCH] [v1, 17/17] vdpa/mlx5: prepare virtqueue resource creation
Date: Tue, 7 Jun 2022 03:24:26 +0000 (UTC) [thread overview]
Message-ID: <20220607032426.B3CB560093@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2306 bytes --]
Test-Label: iol-x86_64-unit-testing
Test-Status: FAILURE
http://dpdk.org/patch/112391
_Testing issues_
Submitter: Li Zhang <lizh@nvidia.com>
Date: Monday, June 06 2022 11:46:50
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c98600d4bed6d15599e448990f2ba117ca938a2d
112375-112391 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | FAIL |
+---------------------+----------------+
| Ubuntu 18.04 | PASS |
+---------------------+----------------+
==== 20 line log output for openSUSE Leap 15 (dpdk_unit_test): ====
90/100 DPDK:fast-tests / metrics_autotest OK 0.17 s
91/100 DPDK:fast-tests / telemetry_json_autotest OK 0.17 s
92/100 DPDK:fast-tests / telemetry_data_autotest OK 0.17 s
93/100 DPDK:fast-tests / table_autotest OK 6.03 s
94/100 DPDK:fast-tests / ring_pmd_autotest OK 0.17 s
95/100 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 0.52 s
96/100 DPDK:fast-tests / bitratestats_autotest OK 0.17 s
97/100 DPDK:fast-tests / latencystats_autotest OK 0.17 s
98/100 DPDK:fast-tests / pdump_autotest FAIL 5.78 s (killed by signal 11 SIGSEGV)
99/100 DPDK:fast-tests / vdev_autotest OK 0.17 s
100/100 DPDK:fast-tests / compressdev_autotest SKIP 0.17 s
Ok: 93
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 6
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)
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Ubuntu 18.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0-3ubuntu1~18.04
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/22459/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
reply other threads:[~2022-06-07 3:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220607032426.B3CB560093@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=lizh@nvidia.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).