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] fcfb19cda4f6439f260cdeabb6c44d3c6f0d5fc4
Date: Sat, 06 Jul 2024 01:02:33 -0700 (PDT)	[thread overview]
Message-ID: <6688fa19.050a0220.6321f.60abSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing pending_

Branch: dpdk

fcfb19cda4f6439f260cdeabb6c44d3c6f0d5fc4 --> testing pending

Test environment and result as below:

+---------------------+--------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2019 | PASS               | PEND                 |
+---------------------+--------------------+----------------------+
| Windows Server 2022 | PASS               | PEND                 |
+---------------------+--------------------+----------------------+
| FreeBSD 13.3        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| FreeBSD 14.1        | PEND               | SKIPPED              |
+---------------------+--------------------+----------------------+


Windows Server 2019
	Kernel: 10.0.17763
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

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

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

FreeBSD 14.1
	Kernel: 14.1
	Compiler: clang 18.1.5

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-07-06  8:02 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-06  8:02 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-06 22:14 dpdklab
2024-07-06 21:18 dpdklab
2024-07-06 21:18 dpdklab
2024-07-06 21:17 dpdklab
2024-07-06 21:10 dpdklab
2024-07-06 21:09 dpdklab
2024-07-06 21:05 dpdklab
2024-07-06 21:03 dpdklab
2024-07-06 21:02 dpdklab
2024-07-06 20:59 dpdklab
2024-07-06 20:43 dpdklab
2024-07-06 20:36 dpdklab
2024-07-06 20:33 dpdklab
2024-07-06 20:33 dpdklab
2024-07-06 20:29 dpdklab
2024-07-06 20:28 dpdklab
2024-07-06 20:27 dpdklab
2024-07-06 20:26 dpdklab
2024-07-06 20:25 dpdklab
2024-07-06 20:24 dpdklab
2024-07-06 20:23 dpdklab
2024-07-06 20:22 dpdklab
2024-07-06 20:22 dpdklab
2024-07-06 20:18 dpdklab
2024-07-06 20:15 dpdklab
2024-07-06 20:14 dpdklab
2024-07-06 20:12 dpdklab
2024-07-06 20:09 dpdklab
2024-07-06 20:09 dpdklab
2024-07-06 20:09 dpdklab
2024-07-06 20:08 dpdklab
2024-07-06 19:57 dpdklab
2024-07-06 19:55 dpdklab
2024-07-06 12:06 dpdklab
2024-07-06 12:05 dpdklab
2024-07-06 12:03 dpdklab
2024-07-06 12:02 dpdklab
2024-07-06 11:59 dpdklab
2024-07-06 11:57 dpdklab
2024-07-06 11:53 dpdklab
2024-07-06 11:53 dpdklab
2024-07-06 11:49 dpdklab
2024-07-06 11:33 dpdklab
2024-07-06 11:33 dpdklab
2024-07-06 11:32 dpdklab
2024-07-06 11:30 dpdklab
2024-07-06 11:29 dpdklab
2024-07-06 11:29 dpdklab
2024-07-06 10:49 dpdklab
2024-07-06 10:14 dpdklab
2024-07-06  9:00 dpdklab
2024-07-06  8:02 dpdklab
2024-07-06  8:01 dpdklab
2024-07-06  3:13 dpdklab
2024-07-06  1:32 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=6688fa19.050a0220.6321f.60abSMTPIN_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).