From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Soumyadeep Hore <soumyadeep.hore@intel.com>
Subject: |FAILURE| pw140357-140381 [PATCH] [25/25] net/cpfl: updating idpf vc
Date: Tue, 28 May 2024 05:50:38 -0700 (PDT) [thread overview]
Message-ID: <6655d31e.050a0220.4dbac.e0b2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240528073630.867131-6-soumyadeep.hore@intel.com>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/140381
_Testing issues_
Submitter: Soumyadeep Hore <soumyadeep.hore@intel.com>
Date: Tuesday, May 28 2024 07:36:30
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:19be1a0ba8af8a513adb011a3017d583d6312fc9
140357-140381 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Fedora 39 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian 12 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
| Windows Server 2019 | FAIL |
+---------------------+----------------+
==== 20 line log output for Windows Server 2019 (dpdk_unit_test): ====
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Fedora 39
Kernel: Depends on container host
Compiler: gcc 13.2.1
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
Debian 12
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.6
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
RHEL8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30032/
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-05-28 12:50 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240528073630.867131-6-soumyadeep.hore@intel.com>
2024-05-28 7:53 ` |SUCCESS| pw140357-140381 [PATCH 25/25] net/cpfl: updating idpf vc queue switch in cpfl qemudev
2024-05-28 7:58 ` qemudev
2024-05-28 8:20 ` |WARNING| pw140381 " checkpatch
2024-05-28 9:23 ` |FAILURE| " 0-day Robot
2024-05-28 10:00 ` |SUCCESS| pw140357-140381 [PATCH] [25/25] net/cpfl: updating idpf vc dpdklab
2024-05-28 10:00 ` dpdklab
2024-05-28 10:41 ` dpdklab
2024-05-28 10:42 ` dpdklab
2024-05-28 10:48 ` dpdklab
2024-05-28 10:48 ` dpdklab
2024-05-28 10:48 ` dpdklab
2024-05-28 10:49 ` dpdklab
2024-05-28 10:49 ` dpdklab
2024-05-28 10:50 ` dpdklab
2024-05-28 10:50 ` dpdklab
2024-05-28 10:54 ` dpdklab
2024-05-28 10:56 ` dpdklab
2024-05-28 10:57 ` dpdklab
2024-05-28 10:58 ` dpdklab
2024-05-28 10:59 ` dpdklab
2024-05-28 10:59 ` dpdklab
2024-05-28 11:00 ` dpdklab
2024-05-28 11:00 ` dpdklab
2024-05-28 11:02 ` dpdklab
2024-05-28 11:02 ` dpdklab
2024-05-28 11:15 ` dpdklab
2024-05-28 11:36 ` dpdklab
2024-05-28 12:00 ` |FAILURE| " dpdklab
2024-05-28 12:01 ` dpdklab
2024-05-28 12:01 ` dpdklab
2024-05-28 12:07 ` dpdklab
2024-05-28 12:24 ` dpdklab
2024-05-28 12:32 ` |SUCCESS| " dpdklab
2024-05-28 12:32 ` dpdklab
2024-05-28 12:33 ` dpdklab
2024-05-28 12:35 ` dpdklab
2024-05-28 12:36 ` |FAILURE| " dpdklab
2024-05-28 12:37 ` dpdklab
2024-05-28 12:42 ` dpdklab
2024-05-28 12:42 ` dpdklab
2024-05-28 12:44 ` dpdklab
2024-05-28 12:45 ` |SUCCESS| " dpdklab
2024-05-28 12:45 ` dpdklab
2024-05-28 12:46 ` dpdklab
2024-05-28 12:46 ` |FAILURE| " dpdklab
2024-05-28 12:47 ` |SUCCESS| " dpdklab
2024-05-28 12:48 ` dpdklab
2024-05-28 12:49 ` |FAILURE| " dpdklab
2024-05-28 12:49 ` dpdklab
2024-05-28 12:50 ` dpdklab
2024-05-28 12:50 ` dpdklab [this message]
2024-05-28 12:51 ` |SUCCESS| " dpdklab
2024-05-28 12:52 ` dpdklab
2024-05-28 12:53 ` dpdklab
2024-05-28 12:54 ` dpdklab
2024-05-28 12:55 ` |FAILURE| " dpdklab
2024-05-28 12:55 ` dpdklab
2024-05-28 12:55 ` |SUCCESS| " dpdklab
2024-05-28 12:56 ` dpdklab
2024-05-28 12:56 ` |FAILURE| " dpdklab
2024-05-28 12:57 ` dpdklab
2024-05-28 12:57 ` |SUCCESS| " dpdklab
2024-05-28 12:57 ` |FAILURE| " dpdklab
2024-05-28 12:58 ` dpdklab
2024-05-28 12:58 ` dpdklab
2024-05-28 12:59 ` |SUCCESS| " dpdklab
2024-05-28 12:59 ` |FAILURE| " dpdklab
2024-05-28 13:00 ` dpdklab
2024-05-28 13:00 ` |SUCCESS| " dpdklab
2024-05-28 13:01 ` dpdklab
2024-05-28 13:02 ` |FAILURE| " dpdklab
2024-05-28 13:02 ` dpdklab
2024-05-28 13:03 ` dpdklab
2024-05-28 13:05 ` |SUCCESS| " dpdklab
2024-05-28 13:06 ` |FAILURE| " dpdklab
2024-05-28 13:07 ` dpdklab
2024-05-28 13:09 ` dpdklab
2024-05-28 13:10 ` |SUCCESS| " dpdklab
2024-05-28 13:19 ` dpdklab
2024-05-28 13:20 ` dpdklab
2024-05-28 13:20 ` |FAILURE| " dpdklab
2024-05-28 13:23 ` |SUCCESS| " dpdklab
2024-05-28 13:25 ` dpdklab
2024-05-28 14:17 ` dpdklab
2024-05-28 14:19 ` |FAILURE| " dpdklab
2024-05-28 14:46 ` |SUCCESS| " dpdklab
2024-05-30 2:21 ` dpdklab
2024-05-30 2:21 ` dpdklab
2024-05-30 2:24 ` 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=6655d31e.050a0220.4dbac.e0b2SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=soumyadeep.hore@intel.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).