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: |SUCCESS| pw153228 [PATCH] net/ice: update log message
Date: Sun, 04 May 2025 00:10:22 -0700 (PDT)	[thread overview]
Message-ID: <681712de.050a0220.24aa2f.de24SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250502152601.699443-1-dhanya.r.pillai@intel.com>

Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/153228

_Testing PASS_

Submitter: Pillai, Dhanya R <dhanya.r.pillai@intel.com>
Date: Friday, May 02 2025 15:25:59 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2665bfb9838fec7ea6c3b2be5831f93ee087b288

153228 --> testing pass

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

Test environment and result as below:

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


Ubuntu 20.04
	Kernel: 4.19.325-0419325-generic
	Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

FreeBSD 13.5
	Kernel: 13.5-RELEASE
	Compiler: clang 19.1.7

FreeBSD 14.2
	Kernel: 14.2-RELEASE
	Compiler: clang 18.1.6

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-05-04  7:10 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250502152601.699443-1-dhanya.r.pillai@intel.com>
2025-05-02 14:52 ` qemudev
2025-05-02 14:57 ` qemudev
2025-05-02 15:27 ` checkpatch
2025-05-02 16:46 ` 0-day Robot
2025-05-04  6:29 ` dpdklab
2025-05-04  6:46 ` dpdklab
2025-05-04  6:48 ` dpdklab
2025-05-04  6:49 ` dpdklab
2025-05-04  6:52 ` dpdklab
2025-05-04  6:57 ` |PENDING| " dpdklab
2025-05-04  6:59 ` |SUCCESS| " dpdklab
2025-05-04  7:02 ` dpdklab
2025-05-04  7:08 ` dpdklab
2025-05-04  7:10 ` dpdklab [this message]
2025-05-04  7:16 ` dpdklab
2025-05-04  7:18 ` dpdklab
2025-05-04  7:22 ` dpdklab
2025-05-04  7:25 ` |PENDING| " dpdklab
2025-05-04  7:33 ` |SUCCESS| " dpdklab
2025-05-04  7:45 ` |PENDING| " dpdklab
2025-05-04  7:46 ` |SUCCESS| " dpdklab
2025-05-04  7:51 ` dpdklab
2025-05-04  7:55 ` dpdklab
2025-05-04  7:58 ` dpdklab
2025-05-04  8:00 ` |PENDING| " dpdklab
2025-05-04  8:01 ` |SUCCESS| " dpdklab
2025-05-04  8:05 ` |PENDING| " dpdklab
2025-05-04  8:08 ` |SUCCESS| " dpdklab
2025-05-04  8:14 ` dpdklab
2025-05-04  8:39 ` dpdklab
2025-05-04  8:42 ` dpdklab
2025-05-04  8:42 ` dpdklab
2025-05-04  8:46 ` dpdklab
2025-05-04  8:54 ` dpdklab
2025-05-04  9:03 ` |PENDING| " dpdklab
2025-05-04  9:06 ` |SUCCESS| " dpdklab
2025-05-04  9:43 ` |PENDING| " dpdklab
2025-05-04 10:07 ` dpdklab
2025-05-04 10:21 ` |SUCCESS| " dpdklab
2025-05-04 11:12 ` dpdklab
2025-05-04 11:16 ` dpdklab
2025-05-04 11:40 ` |FAILURE| " dpdklab
2025-05-04 11:50 ` |SUCCESS| " dpdklab
2025-05-04 12:32 ` dpdklab
2025-05-04 12:52 ` dpdklab
2025-05-04 13:28 ` dpdklab
2025-05-04 13:29 ` dpdklab
2025-05-04 13:36 ` dpdklab
2025-05-04 14:07 ` dpdklab
2025-05-04 14:33 ` 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=681712de.050a0220.24aa2f.de24SMTPIN_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).