From: dpdklab@iol.unh.edu
To: Georgii Tkachuk <georgii.tkachuk@intel.com>,
Qian Xu <qian.q.xu@intel.com>, Lijuan Tu <lijuan.tu@intel.com>,
Test Report <test-report@dpdk.org>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dpdk-test-reports@iol.unh.edu,
Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Subject: |FAILURE| pw148083 [PATCH] [v2] test/fib: clarify FIB RCU negative t
Date: Thu, 07 Nov 2024 09:50:49 -0800 (PST) [thread overview]
Message-ID: <672cfdf9.050a0220.16814c.46f8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241107170408.214488-1-vladimir.medvedkin@intel.com>
Test-Label: iol-intel-Functional
Test-Status: FAILURE
http://dpdk.org/patch/148083
_Functional Testing issues_
Submitter: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Date: Thursday, November 07 2024 17:04:08
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:9bbd44d63846cf0771ec0f1c7e1b5a63ec5e9603
148083 --> functional testing issues
Upstream job id: Template-DTS-Pipeline#194575
Test environment and result as below:
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Aggregate Results by Test Suite
+-----------------------------+--------+
| Test Suite | Result |
+=============================+========+
| unit_tests_mbuf | PASS |
+-----------------------------+--------+
| vhost_virtio_user_interrupt | PASS |
+-----------------------------+--------+
| virtio_smoke | PASS |
+-----------------------------+--------+
Arm Ampere Altra - Ubuntu 22.04
Kernel: 5.15.83+
Compiler: gcc 11.4
NIC: Intel Corporation QAT 8970 0 Mbps
Aggregate Results by Test Suite
+----------------------------+--------+
| Test Suite | Result |
+============================+========+
| crypto_perf_cryptodev_perf | FAIL |
+----------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31849/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-11-07 17:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241107170408.214488-1-vladimir.medvedkin@intel.com>
2024-11-07 16:39 ` |SUCCESS| pw148083 [PATCH v2] test/fib: clarify FIB RCU negative tests qemudev
2024-11-07 16:43 ` qemudev
2024-11-07 17:04 ` checkpatch
2024-11-07 17:40 ` |PENDING| pw148083 [PATCH] [v2] test/fib: clarify FIB RCU negative t dpdklab
2024-11-07 17:44 ` |SUCCESS| " dpdklab
2024-11-07 17:45 ` dpdklab
2024-11-07 17:46 ` |PENDING| " dpdklab
2024-11-07 17:50 ` dpdklab [this message]
2024-11-07 17:51 ` dpdklab
2024-11-07 18:05 ` |FAILURE| " dpdklab
2024-11-07 18:06 ` |SUCCESS| " dpdklab
2024-11-07 18:07 ` |SUCCESS| pw148083 [PATCH v2] test/fib: clarify FIB RCU negative tests 0-day Robot
2024-11-07 18:22 ` |SUCCESS| pw148083 [PATCH] [v2] test/fib: clarify FIB RCU negative t dpdklab
2024-11-07 18:24 ` dpdklab
2024-11-07 18:37 ` dpdklab
2024-11-07 19:36 ` dpdklab
2024-11-07 19:41 ` dpdklab
2024-11-07 20:05 ` 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=672cfdf9.050a0220.16814c.46f8SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ferruh.yigit@intel.com \
--cc=georgii.tkachuk@intel.com \
--cc=lijuan.tu@intel.com \
--cc=qian.q.xu@intel.com \
--cc=test-report@dpdk.org \
--cc=vladimir.medvedkin@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).