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| [GIT MASTER] 3fa84cc95c2423cf582657eef0b67d6a4fd0d64a
Date: Fri, 27 Sep 2024 23:56:40 -0700 (PDT)	[thread overview]
Message-ID: <66f7a8a8.050a0220.38276e.afecSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing pending_

Branch: dpdk-next-net

3fa84cc95c2423cf582657eef0b67d6a4fd0d64a --> testing pending

Upstream job id: Windows-Compile-DPDK-VS#3234

Test environment and result as below:

+---------------------+-------------------+----------------------+-----------------------+--------------------+
|     Environment     | dpdk_msvc_compile | dpdk_mingw64_compile | dpdk_win_llvm_compile | dpdk_meson_compile |
+=====================+===================+======================+=======================+====================+
| Windows Server 2022 | PASS              | PEND                 | PEND                  | SKIPPED            |
+---------------------+-------------------+----------------------+-----------------------+--------------------+
| FreeBSD 13.3        | SKIPPED           | SKIPPED              | SKIPPED               | 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

FreeBSD 13.3
	Kernel: 13.3-RELEASE-p5
	Compiler: clang 17.0.6

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/30761/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-09-28  6:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-28  6:56 dpdklab [this message]
2024-09-28  7:23 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=66f7a8a8.050a0220.38276e.afecSMTPIN_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).