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,
	Stephen Hemminger <stephen@networkplumber.org>
Subject: |SUCCESS| [GIT MASTER] 535c49b6264f1df239703b8250b070e4c4cda2e9
Date: Thu, 16 Oct 2025 23:32:46 -0700 (PDT)	[thread overview]
Message-ID: <68f1e30e.050a0220.1840c1.6423SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk-next-net

535c49b6264f1df239703b8250b070e4c4cda2e9 --> testing pass

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

Test environment and result as below:

+--------------+--------------------+
| Environment  | dpdk_meson_compile |
+==============+====================+
| Ubuntu 20.04 | PASS               |
+--------------+--------------------+
| FreeBSD 14.2 | PASS               |
+--------------+--------------------+


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/tarballs/35248/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2025-10-17  6:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-17  6:32 dpdklab [this message]
2025-10-17  6:41 dpdklab
2025-10-17  6:48 dpdklab
2025-10-17  6:59 dpdklab
2025-10-17  7:03 dpdklab
2025-10-17  7:03 dpdklab
2025-10-17  7:42 dpdklab
2025-10-17  8:04 dpdklab
2025-10-17  8:12 dpdklab
2025-10-17  8:14 dpdklab
2025-10-17  8:28 dpdklab
2025-10-17  8:30 dpdklab
2025-10-17  8:39 dpdklab
2025-10-17  9:02 dpdklab
2025-10-17 12:03 dpdklab
2025-10-17 21:48 dpdklab
2025-10-17 21: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=68f1e30e.050a0220.1840c1.6423SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=stephen@networkplumber.org \
    --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).