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| pw150483 [PATCH] buildtools/check-git-log: print expected
Date: Fri, 24 Jan 2025 18:32:03 -0800 (PST)	[thread overview]
Message-ID: <67944d23.170a0220.104623.7146SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250124172434.1422621-1-bruce.richardson@intel.com>

Test-Label: iol-compile-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/150483

_Testing pending_

Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Friday, January 24 2025 17:24:34 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:5b856206c74bbcf19e12cafa15382a7e15b0a1b5

150483 --> testing pending

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

Test environment and result as below:

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


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

FreeBSD 14.2
	Kernel: 14.2-RELEASE
	Compiler: clang 18.1.6

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32418/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-01-25  2:32 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250124172434.1422621-1-bruce.richardson@intel.com>
2025-01-24 16:51 ` |SUCCESS| pw150483 [PATCH] buildtools/check-git-log: print expected driver prefix qemudev
2025-01-24 16:55 ` qemudev
2025-01-24 17:25 ` checkpatch
2025-01-24 18:23 ` 0-day Robot
2025-01-25  1:41 ` |SUCCESS| pw150483 [PATCH] buildtools/check-git-log: print expected dpdklab
2025-01-25  1:42 ` dpdklab
2025-01-25  1:49 ` dpdklab
2025-01-25  1:53 ` dpdklab
2025-01-25  1:58 ` dpdklab
2025-01-25  2:32 ` dpdklab [this message]
2025-01-25  2:36 ` dpdklab
2025-01-25  2:42 ` |PENDING| " dpdklab
2025-01-25  2:45 ` dpdklab
2025-01-25  2:46 ` |SUCCESS| " dpdklab
2025-01-25  2:47 ` dpdklab
2025-01-25  3:59 ` dpdklab
2025-01-25  4:20 ` |PENDING| " dpdklab
2025-01-25  6:00 ` |SUCCESS| " dpdklab
2025-01-25  6:25 ` dpdklab
2025-01-25  6:30 ` dpdklab
2025-01-25  7:54 ` |WARNING| " dpdklab
2025-01-25  7:55 ` dpdklab
2025-01-25  8:10 ` dpdklab
2025-01-25  8:16 ` dpdklab
2025-01-25  8:22 ` dpdklab
2025-01-25  9:57 ` |SUCCESS| " dpdklab
2025-01-25 15:09 ` 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=67944d23.170a0220.104623.7146SMTPIN_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).