From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Nicholas Pratte <npratte@iol.unh.edu>
Subject: |FAILURE| pw139495 [PATCH] [v4] dts: Change hugepage runtime config
Date: Thu, 18 Apr 2024 10:25:10 -0700 (PDT) [thread overview]
Message-ID: <66215776.810a0220.640e.8283SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240418161026.2839-1-npratte@iol.unh.edu>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/139495
_Testing issues_
Submitter: Nicholas Pratte <npratte@iol.unh.edu>
Date: Thursday, April 18 2024 16:10:26
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139495 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| Fedora 39 | PASS |
+---------------------+----------------+
| Debian 12 | FAIL |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
==== 20 line log output for Debian 12 (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
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 39
Kernel: Depends on container host
Compiler: gcc 13.2.1
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
RHEL8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)
Ubuntu 22.04
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.0
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
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/29819/
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-04-18 17:25 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240418161026.2839-1-npratte@iol.unh.edu>
2024-04-18 15:47 ` |SUCCESS| pw139495 [PATCH v4] dts: Change hugepage runtime config to 2MB Exclusively qemudev
2024-04-18 15:51 ` qemudev
2024-04-18 16:11 ` checkpatch
2024-04-18 17:05 ` |SUCCESS| pw139495 [PATCH] [v4] dts: Change hugepage runtime config dpdklab
2024-04-18 17:05 ` |SUCCESS| pw139495 [PATCH v4] dts: Change hugepage runtime config to 2MB Exclusively 0-day Robot
2024-04-18 17:06 ` |SUCCESS| pw139495 [PATCH] [v4] dts: Change hugepage runtime config dpdklab
2024-04-18 17:06 ` dpdklab
2024-04-18 17:06 ` dpdklab
2024-04-18 17:07 ` dpdklab
2024-04-18 17:07 ` dpdklab
2024-04-18 17:07 ` dpdklab
2024-04-18 17:07 ` dpdklab
2024-04-18 17:07 ` dpdklab
2024-04-18 17:07 ` dpdklab
2024-04-18 17:08 ` dpdklab
2024-04-18 17:08 ` dpdklab
2024-04-18 17:08 ` dpdklab
2024-04-18 17:09 ` dpdklab
2024-04-18 17:09 ` dpdklab
2024-04-18 17:09 ` dpdklab
2024-04-18 17:09 ` dpdklab
2024-04-18 17:09 ` dpdklab
2024-04-18 17:10 ` dpdklab
2024-04-18 17:10 ` dpdklab
2024-04-18 17:10 ` dpdklab
2024-04-18 17:10 ` dpdklab
2024-04-18 17:11 ` dpdklab
2024-04-18 17:11 ` dpdklab
2024-04-18 17:11 ` dpdklab
2024-04-18 17:12 ` dpdklab
2024-04-18 17:12 ` dpdklab
2024-04-18 17:12 ` dpdklab
2024-04-18 17:13 ` dpdklab
2024-04-18 17:13 ` dpdklab
2024-04-18 17:13 ` dpdklab
2024-04-18 17:13 ` dpdklab
2024-04-18 17:14 ` dpdklab
2024-04-18 17:14 ` dpdklab
2024-04-18 17:15 ` dpdklab
2024-04-18 17:15 ` dpdklab
2024-04-18 17:15 ` dpdklab
2024-04-18 17:15 ` dpdklab
2024-04-18 17:15 ` dpdklab
2024-04-18 17:16 ` |FAILURE| " dpdklab
2024-04-18 17:16 ` |SUCCESS| " dpdklab
2024-04-18 17:16 ` dpdklab
2024-04-18 17:16 ` dpdklab
2024-04-18 17:16 ` |FAILURE| " dpdklab
2024-04-18 17:17 ` |SUCCESS| " dpdklab
2024-04-18 17:17 ` dpdklab
2024-04-18 17:17 ` dpdklab
2024-04-18 17:17 ` |FAILURE| " dpdklab
2024-04-18 17:18 ` |SUCCESS| " dpdklab
2024-04-18 17:18 ` dpdklab
2024-04-18 17:18 ` |FAILURE| " dpdklab
2024-04-18 17:18 ` |SUCCESS| " dpdklab
2024-04-18 17:19 ` |FAILURE| " dpdklab
2024-04-18 17:19 ` |SUCCESS| " dpdklab
2024-04-18 17:19 ` dpdklab
2024-04-18 17:20 ` |FAILURE| " dpdklab
2024-04-18 17:20 ` |SUCCESS| " dpdklab
2024-04-18 17:20 ` |FAILURE| " dpdklab
2024-04-18 17:21 ` |SUCCESS| " dpdklab
2024-04-18 17:21 ` dpdklab
2024-04-18 17:21 ` |FAILURE| " dpdklab
2024-04-18 17:22 ` dpdklab
2024-04-18 17:22 ` |SUCCESS| " dpdklab
2024-04-18 17:22 ` dpdklab
2024-04-18 17:23 ` |FAILURE| " dpdklab
2024-04-18 17:24 ` dpdklab
2024-04-18 17:24 ` dpdklab
2024-04-18 17:25 ` dpdklab [this message]
2024-04-18 17:25 ` dpdklab
2024-04-18 17:27 ` |SUCCESS| " dpdklab
2024-04-18 17:28 ` dpdklab
2024-04-18 17:31 ` dpdklab
2024-04-18 17:34 ` dpdklab
2024-04-18 17:38 ` |FAILURE| " dpdklab
2024-04-18 17:48 ` |SUCCESS| " dpdklab
2024-04-18 18:01 ` dpdklab
2024-04-18 18:01 ` dpdklab
2024-04-18 18:05 ` dpdklab
2024-04-18 18:09 ` dpdklab
2024-04-18 18:16 ` dpdklab
2024-04-18 18:17 ` dpdklab
2024-04-18 18:29 ` dpdklab
2024-04-18 18:33 ` dpdklab
2024-04-18 22:16 ` dpdklab
2024-04-18 22:32 ` 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=66215776.810a0220.640e.8283SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=npratte@iol.unh.edu \
--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).