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| pw159616-159617 [PATCH] [v2,2/2] net/null: revise info_get
Date: Wed, 07 Jan 2026 09:07:18 -0800 (PST)	[thread overview]
Message-ID: <695e92c6.050a0220.2fe741.0176SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20260106164815.158430-3-stephen@networkplumber.org>

Test-Label: iol-compile-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/159617

_Testing pending_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, January 06 2026 16:47:15 
DPDK git baseline: Repo:dpdk-next-net
  Branch: master
  CommitID:986a1b63892f24df8928216daeec53f034f1e0a4

159616-159617 --> testing pending

Upstream job id: Generic-VM-DPDK-Compile-Meson#40528

Test environment and result as below:

+---------------------+--------------------+-------------------------+
|     Environment     | dpdk_meson_compile | dpdk_llvm_clang_compile |
+=====================+====================+=========================+
| FreeBSD 14.2        | PASS               | SKIPPED                 |
+---------------------+--------------------+-------------------------+
| Windows Server 2025 | SKIPPED            | PEND                    |
+---------------------+--------------------+-------------------------+


FreeBSD 14.2
	Kernel: 14.2-RELEASE
	Compiler: clang 18.1.6

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2026-01-07 17:07 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260106164815.158430-3-stephen@networkplumber.org>
2026-01-06 16:49 ` |SUCCESS| pw159617 [PATCH v2 2/2] " checkpatch
2026-01-06 17:01 ` |SUCCESS| pw159616-159617 " qemudev
2026-01-06 17:06 ` qemudev
2026-01-06 18:09 ` |SUCCESS| pw159617 " 0-day Robot
2026-01-06 18:09 ` 0-day Robot
2026-01-07 16:58 ` |SUCCESS| pw159616-159617 [PATCH] [v2,2/2] " dpdklab
2026-01-07 17:06 ` dpdklab
2026-01-07 17:07 ` dpdklab [this message]
2026-01-07 17:12 ` dpdklab
2026-01-07 17:15 ` dpdklab
2026-01-07 17:17 ` dpdklab
2026-01-07 17:38 ` dpdklab
2026-01-07 17:48 ` dpdklab
2026-01-07 21:08 ` |PENDING| " dpdklab
2026-01-08  1:40 ` |SUCCESS| " dpdklab
2026-01-08 10:14 ` dpdklab
2026-01-08 10:24 ` dpdklab
2026-01-08 10:25 ` dpdklab
2026-01-08 10:26 ` dpdklab
2026-01-08 10:27 ` dpdklab
2026-01-08 20:43 ` dpdklab
2026-01-08 21:37 ` dpdklab
2026-01-08 21:41 ` dpdklab
2026-01-08 21:49 ` dpdklab
2026-01-08 21:53 ` dpdklab
2026-01-08 21:59 ` dpdklab
2026-01-08 22:04 ` dpdklab
2026-01-08 22:05 ` dpdklab
2026-01-08 22:10 ` dpdklab
2026-01-08 22:49 ` dpdklab
2026-01-08 23:31 ` dpdklab
2026-01-08 23:48 ` dpdklab
2026-01-09  0:08 ` 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=695e92c6.050a0220.2fe741.0176SMTPIN_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).