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] 510b460e02594a70d4ce19e2d29df3ade8af36d7
Date: Tue, 26 Nov 2024 22:56:30 -0800 (PST)	[thread overview]
Message-ID: <6746c29e.050a0220.6d796.7a46SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing pending_

Branch: dpdk-next-virtio

510b460e02594a70d4ce19e2d29df3ade8af36d7 --> testing pending

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

Test environment and result as below:

+---------------------+-------------------+--------------------+
|     Environment     | dpdk_msvc_compile | dpdk_meson_compile |
+=====================+===================+====================+
| Windows Server 2022 | PEND              | SKIPPED            |
+---------------------+-------------------+--------------------+
| FreeBSD 13.4        | SKIPPED           | PASS               |
+---------------------+-------------------+--------------------+
| FreeBSD 14.1        | 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.4
	Kernel: 13.4-RELEASE-p1
	Compiler: clang 18.1.6

FreeBSD 14.1
	Kernel: 14.1-RELEASE-p3
	Compiler: clang 18.1.5

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-11-27  6:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-27  6:56 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-27  7:41 dpdklab
2024-11-27  6:49 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=6746c29e.050a0220.6d796.7a46SMTPIN_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).