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| pw151691-151705 [PATCH] [v9,15/15] devtools/cocci: add scr
Date: Thu, 20 Feb 2025 12:11:57 -0800 (PST)	[thread overview]
Message-ID: <67b78c8d.050a0220.eb5d1.82e5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250220164151.9606-16-stephen@networkplumber.org>

Test-Label: iol-unit-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/151705

_Testing pending_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, February 20 2025 16:27:21 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fab31a03ba98e7457284df95dd9eef2223a4ccaa

151691-151705 --> testing pending

Upstream job id: Generic-Unit-Test-DPDK#316697

Test environment and result as below:

+-------------------+----------------+
|    Environment    | dpdk_unit_test |
+===================+================+
| Debian Bullseye   | PASS           |
+-------------------+----------------+
| Fedora 41 (Clang) | PEND           |
+-------------------+----------------+
| Fedora 40         | PEND           |
+-------------------+----------------+
| CentOS Stream 9   | PEND           |
+-------------------+----------------+
| RHEL9             | PEND           |
+-------------------+----------------+


Debian Bullseye
	Kernel: Depends on container host
	Compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110

Fedora 41 (Clang)
	Kernel: Depends on container host
	Compiler: clang 19.1.5 (Fedora 19.1.5-1.fc41)

Fedora 40
	Kernel: Depends on container host
	Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)

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

RHEL9
	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/32624/

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-20 20:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250220164151.9606-16-stephen@networkplumber.org>
2025-02-20 16:09 ` |SUCCESS| pw151691-151705 [PATCH v9 15/15] devtools/cocci: add script to find problematic memset qemudev
2025-02-20 16:14 ` qemudev
2025-02-20 16:44 ` |SUCCESS| pw151705 " checkpatch
2025-02-20 17:44 ` 0-day Robot
2025-02-20 18:47 ` |SUCCESS| pw151691-151705 [PATCH] [v9,15/15] devtools/cocci: add scr dpdklab
2025-02-20 18:49 ` dpdklab
2025-02-20 19:03 ` |PENDING| " dpdklab
2025-02-20 19:05 ` |SUCCESS| " dpdklab
2025-02-20 19:08 ` dpdklab
2025-02-20 19:09 ` dpdklab
2025-02-20 19:28 ` |PENDING| " dpdklab
2025-02-20 19:37 ` |SUCCESS| " dpdklab
2025-02-20 19:45 ` dpdklab
2025-02-20 20:11 ` dpdklab [this message]
2025-02-20 21:05 ` |PENDING| " dpdklab
2025-02-21  0:38 ` |SUCCESS| " dpdklab
2025-02-21  4:20 ` 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=67b78c8d.050a0220.eb5d1.82e5SMTPIN_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).