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,
	Bruce Richardson <bruce.richardson@intel.com>
Subject: |SUCCESS| pw158777-158778 [PATCH] [2/2] net/iavf: check Rx timestamp
Date: Fri, 14 Nov 2025 04:27:24 -0800 (PST)	[thread overview]
Message-ID: <6917202c.050a0220.3d471e.bf69SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251113-jk-dpdk-iavf-rx-timestamping-improvements-v1-2-3d9a0168087b@intel.com>

Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/158778

_Testing PASS_

Submitter: Jacob Keller <jacob.e.keller@intel.com>
Date: Thursday, November 13 2025 21:33:45 
DPDK git baseline: Repo:dpdk-next-net-intel
  Branch: master
  CommitID:e5357d609907d504f4705e4899f3dad43cb4b70f

158777-158778 --> testing pass

Upstream job id: Generic-DPDK-Compile-Meson#444239

Test environment and result as below:

+-------------------------------+--------------------+-------------------------+------------------+
|          Environment          | dpdk_meson_compile | dpdk_llvm_clang_compile | dpdk_compile_ovs |
+===============================+====================+=========================+==================+
| Ubuntu 20.04                  | PASS               | SKIPPED                 | SKIPPED          |
+-------------------------------+--------------------+-------------------------+------------------+
| FreeBSD 14.2                  | PASS               | SKIPPED                 | SKIPPED          |
+-------------------------------+--------------------+-------------------------+------------------+
| Red Hat Enterprise Linux 8.10 | PASS               | SKIPPED                 | SKIPPED          |
+-------------------------------+--------------------+-------------------------+------------------+
| Fedora Linux 42               | PASS               | SKIPPED                 | PASS             |
+-------------------------------+--------------------+-------------------------+------------------+
| Windows Server 2022           | SKIPPED            | PASS                    | SKIPPED          |
+-------------------------------+--------------------+-------------------------+------------------+


Ubuntu 20.04
	Kernel: 4.19
	Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

FreeBSD 14.2
	Kernel: 14.2-RELEASE
	Compiler: clang 18.1.6

Red Hat Enterprise Linux 8.10
	Kernel: 5.15
	Compiler: gcc gcc (GCC) 8.5.0 20210514 (Red Hat 8.5.0-22)

Fedora Linux 42
	Kernel: 5.15
	Compiler: gcc gcc (GCC) 15.2.1 20250808 (Red Hat 15.2.1-1)

Windows Server 2022
	Kernel: 10.0.20348.2031
	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/34584/

UNH-IOL DPDK Community Lab

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

      parent reply	other threads:[~2025-11-14 12:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251113-jk-dpdk-iavf-rx-timestamping-improvements-v1-2-3d9a0168087b@intel.com>
2025-11-13 20:59 ` |SUCCESS| pw158777-158778 [PATCH 2/2] net/iavf: check Rx timestamp validity bit qemudev
2025-11-13 21:04 ` qemudev
2025-11-13 21:33 ` |SUCCESS| pw158778 " checkpatch
2025-11-13 22:21 ` 0-day Robot
2025-11-13 22:21 ` 0-day Robot
2025-11-13 22:22 ` |PENDING| pw158777-158778 [PATCH] [2/2] net/iavf: check Rx timestamp dpdklab
2025-11-13 22:26 ` |SUCCESS| " dpdklab
2025-11-13 22:26 ` dpdklab
2025-11-13 22:29 ` dpdklab
2025-11-13 22:33 ` dpdklab
2025-11-13 22:36 ` |PENDING| " dpdklab
2025-11-13 22:43 ` dpdklab
2025-11-13 23:04 ` |SUCCESS| " dpdklab
2025-11-14  0:21 ` dpdklab
2025-11-14  0:22 ` dpdklab
2025-11-14  2:38 ` dpdklab
2025-11-14  3:45 ` dpdklab
2025-11-14  3:46 ` dpdklab
2025-11-14  4:05 ` dpdklab
2025-11-14  4:16 ` dpdklab
2025-11-14  8:03 ` dpdklab
2025-11-14 12:27 ` dpdklab [this message]

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=6917202c.050a0220.3d471e.bf69SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=bruce.richardson@intel.com \
    --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).