automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw146334-146337 [PATCH] [v6,5/5] maintainers: update for d
Date: Sun, 20 Oct 2024 03:56:38 -0700 (PDT)	[thread overview]
Message-ID: <6714e1e6.050a0220.185c53.3920SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241020092233.2906612-6-sivaprasad.tummala@amd.com>

Test-Label: iol-unit-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/146337

_Testing pending_

Submitter: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
Date: Sunday, October 20 2024 09:22:32 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e609858b480ca0d646e5f05f2c7fd6bbf35a4140

146334-146337 --> testing pending

Upstream job id: Generic-VM-Unit-Test-DPDK#25777

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2022 | PASS           |
+---------------------+----------------+
| Debian 12           | PEND           |
+---------------------+----------------+


Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521

Debian 12
	Kernel: Depends on container host
	Compiler: gcc (Debian 12.2.0-14) 12.2.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-10-20 10:56 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241020092233.2906612-6-sivaprasad.tummala@amd.com>
2024-10-20  9:25 ` |SUCCESS| pw146337 [PATCH v6 5/5] maintainers: update for drivers/power checkpatch
2024-10-20 10:24 ` |FAILURE| " 0-day Robot
2024-10-20 10:31 ` |SUCCESS| pw146334-146337 [PATCH] [v6,5/5] maintainers: update for d dpdklab
2024-10-20 10:39 ` dpdklab
2024-10-20 10:44 ` dpdklab
2024-10-20 10:44 ` dpdklab
2024-10-20 10:47 ` dpdklab
2024-10-20 10:47 ` dpdklab
2024-10-20 10:48 ` dpdklab
2024-10-20 10:51 ` dpdklab
2024-10-20 10:56 ` dpdklab [this message]
2024-10-20 10:58 ` dpdklab
2024-10-20 11:22 ` |FAILURE| " dpdklab
2024-10-20 11:24 ` |SUCCESS| " dpdklab
2024-10-20 11:42 ` |FAILURE| " dpdklab
2024-10-20 11:47 ` |SUCCESS| " dpdklab
2024-10-20 14:49 ` |PENDING| " dpdklab
2024-10-20 15:39 ` |FAILURE| " dpdklab
2024-10-20 15:50 ` dpdklab
2024-10-20 15:52 ` dpdklab
2024-10-20 15:53 ` dpdklab
2024-10-20 15:54 ` dpdklab
2024-10-20 15:57 ` |WARNING| " dpdklab
2024-10-20 16:06 ` |FAILURE| " dpdklab
2024-10-20 16:12 ` dpdklab
2024-10-20 16:14 ` dpdklab
2024-10-20 16:50 ` dpdklab
2024-10-20 16:53 ` dpdklab
2024-10-20 16:58 ` dpdklab
2024-10-20 17:01 ` dpdklab
2024-10-20 17:07 ` dpdklab
2024-10-20 17:29 ` dpdklab
2024-10-20 17:33 ` |WARNING| " dpdklab
2024-10-20 18:10 ` |FAILURE| " dpdklab
2024-10-20 22:36 ` |WARNING| " dpdklab
2024-10-21  3:05 ` |FAILURE| pw146334-146337 [PATCH v6 5/5] maintainers: update for drivers/power qemudev
2024-10-22  3:14 ` qemudev

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=6714e1e6.050a0220.185c53.3920SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@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).