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] 077a7044cc5b2533410f691c8db6fb4f6667b1ca
Date: Fri, 06 Dec 2024 17:45:57 -0800 (PST)	[thread overview]
Message-ID: <6753a8d5.170a0220.34d36f.bf7fSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing pending_

Branch: tags/v22.11

077a7044cc5b2533410f691c8db6fb4f6667b1ca --> testing pending

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

Test environment and result as below:

+--------------+--------------------+
| Environment  | dpdk_meson_compile |
+==============+====================+
| FreeBSD 14.1 | PEND               |
+--------------+--------------------+
| FreeBSD 13.4 | PASS               |
+--------------+--------------------+


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

FreeBSD 13.4
	Kernel: 13.4-RELEASE-p1
	Compiler: clang 18.1.6

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-12-07  1:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-07  1:45 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-09  6:10 dpdklab
2024-12-09  6:05 dpdklab
2024-12-09  5:42 dpdklab
2024-12-08  6:11 dpdklab
2024-12-08  5:37 dpdklab
2024-12-07  6:24 dpdklab
2024-12-07  6:21 dpdklab
2024-12-07  6:10 dpdklab
2024-12-07  5:12 dpdklab
2024-12-07  1:39 dpdklab
2024-12-07  1:17 dpdklab
2024-12-06 23:37 dpdklab
2024-12-06  5:55 dpdklab
2024-12-06  5:49 dpdklab
2024-12-05  6:57 dpdklab
2024-12-05  6:49 dpdklab
2024-12-05  6:19 dpdklab
2024-12-04  6:30 dpdklab
2024-12-04  6:18 dpdklab
2024-12-04  6:13 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=6753a8d5.170a0220.34d36f.bf7fSMTPIN_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).