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| pw151959 [PATCH] net: fix IPv4 compat and mapped checks
Date: Mon, 24 Feb 2025 14:47:34 -0800 (PST)	[thread overview]
Message-ID: <67bcf706.630a0220.324781.0ff8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250224144725.271975-2-rjarry@redhat.com>

Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/151959

_Testing PASS_

Submitter: Robin Jarry <rjarry@redhat.com>
Date: Monday, February 24 2025 14:47:26 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fab31a03ba98e7457284df95dd9eef2223a4ccaa

151959 --> testing pass

Upstream job id: Generic-DPDK-Compile-Meson#364781

Test environment and result as below:

+-----------------------+--------------------+
|      Environment      | dpdk_meson_compile |
+=======================+====================+
| CentOS Stream 9 (ARM) | PASS               |
+-----------------------+--------------------+


CentOS Stream 9 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)

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

UNH-IOL DPDK Community Lab

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

      parent reply	other threads:[~2025-02-24 22:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250224144725.271975-2-rjarry@redhat.com>
2025-02-24 14:13 ` |SUCCESS| pw151959 [PATCH dpdk] " qemudev
2025-02-24 14:17 ` qemudev
2025-02-24 14:47 ` checkpatch
2025-02-24 16:04 ` 0-day Robot
2025-02-24 19:05 ` |FAILURE| pw151959 [PATCH] " dpdklab
2025-02-24 19:06 ` dpdklab
2025-02-24 19:24 ` |SUCCESS| " dpdklab
2025-02-24 19:53 ` |PENDING| " dpdklab
2025-02-24 19:58 ` |SUCCESS| " dpdklab
2025-02-24 22:29 ` dpdklab
2025-02-24 22:47 ` dpdklab [this message]

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=67bcf706.630a0220.324781.0ff8SMTPIN_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).