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| pw155367-155368 [PATCH] [v3,2/2] crypto/ipsec_mb: fix QP r
Date: Sat, 19 Jul 2025 10:29:01 -0700 (PDT)	[thread overview]
Message-ID: <687bd5dd.050a0220.17c7ff.ace7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250719153227.1980-2-mosesyyoung@gmail.com>

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

_Testing pending_

Submitter: Yang Ming <mosesyyoung@gmail.com>
Date: Saturday, July 19 2025 15:32:26 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:f6e3473724e7ce31103fa0ecad62b282ec8e7090

155367-155368 --> testing pending

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

Test environment and result as below:

+---------------------+-------------------+--------------------+-------------------------+
|     Environment     | dpdk_msvc_compile | dpdk_meson_compile | dpdk_llvm_clang_compile |
+=====================+===================+====================+=========================+
| Windows Server 2022 | PEND              | SKIPPED            | PEND                    |
+---------------------+-------------------+--------------------+-------------------------+
| Ubuntu 20.04        | SKIPPED           | PASS               | SKIPPED                 |
+---------------------+-------------------+--------------------+-------------------------+
| FreeBSD 14.2        | SKIPPED           | PEND               | SKIPPED                 |
+---------------------+-------------------+--------------------+-------------------------+


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

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-07-19 17:29 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250719153227.1980-2-mosesyyoung@gmail.com>
2025-07-19 15:07 ` |SUCCESS| pw155367-155368 [PATCH v3 2/2] crypto/ipsec_mb: fix QP release in secondary qemudev
2025-07-19 15:12 ` qemudev
2025-07-19 15:31 ` |SUCCESS| pw155368 " checkpatch
2025-07-19 16:43 ` 0-day Robot
2025-07-19 16:45 ` |SUCCESS| pw155367-155368 [PATCH] [v3,2/2] crypto/ipsec_mb: fix QP r dpdklab
2025-07-19 16:53 ` dpdklab
2025-07-19 16:55 ` dpdklab
2025-07-19 17:01 ` dpdklab
2025-07-19 17:25 ` dpdklab
2025-07-19 17:29 ` dpdklab [this message]
2025-07-19 17:29 ` dpdklab
2025-07-19 17:47 ` dpdklab
2025-07-19 17:57 ` |PENDING| " dpdklab
2025-07-19 17:58 ` |SUCCESS| " dpdklab
2025-07-19 18:03 ` dpdklab
2025-07-19 18:04 ` |PENDING| " dpdklab
2025-07-19 18:38 ` dpdklab
2025-07-19 19:23 ` |SUCCESS| " dpdklab
2025-07-19 19:24 ` |PENDING| " dpdklab
2025-07-19 19:56 ` |SUCCESS| " dpdklab
2025-07-19 19:57 ` dpdklab
2025-07-19 20:04 ` dpdklab
2025-07-19 20:06 ` dpdklab
2025-07-19 21:46 ` 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=687bd5dd.050a0220.17c7ff.ace7SMTPIN_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).