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| pw144273 [PATCH] net/gve: add ptype parsing to DQ format
Date: Thu, 19 Sep 2024 02:20:48 -0700 (PDT)	[thread overview]
Message-ID: <66ebecf0.050a0220.2ecec8.cf25SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240918203317.792867-1-joshwash@google.com>

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

_Testing pending_

Submitter: Joshua Washington <joshwash@google.com>
Date: Wednesday, September 18 2024 20:33:17 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:523fd7b3adfdf5a87651e8ca33bc69223b3211d5

144273 --> testing pending

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

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| Windows Server 2022 | PEND           |
+---------------------+----------------+
| Debian Bullseye     | PEND           |
+---------------------+----------------+
| Debian 12           | PEND           |
+---------------------+----------------+
| Fedora 37           | PEND           |
+---------------------+----------------+
| Fedora 38           | PEND           |
+---------------------+----------------+


CentOS Stream 9
	Kernel: Depends on container host
	Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521

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

Debian 12
	Kernel: Depends on container host
	Compiler: gcc (Debian 12.2.0-14) 12.2.0

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1 20230508 (Red Hat 12.3.1-1)

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.2.1 20240316 (Red Hat 13.2.1-7)

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-09-19  9:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240918203317.792867-1-joshwash@google.com>
2024-09-18 20:18 ` |SUCCESS| " qemudev
2024-09-18 20:22 ` qemudev
2024-09-18 20:34 ` checkpatch
2024-09-18 21:44 ` 0-day Robot
2024-09-19  2:19 ` dpdklab
2024-09-19  2:52 ` dpdklab
2024-09-19  3:38 ` dpdklab
2024-09-19  9:14 ` |PENDING| " dpdklab
2024-09-19  9:20 ` dpdklab [this message]
2024-09-19  9:27 ` |SUCCESS| " dpdklab
2024-09-19  9:28 ` dpdklab
2024-09-19  9:39 ` dpdklab
2024-09-19  9:46 ` dpdklab
2024-09-19  9:46 ` dpdklab
2024-09-19  9:55 ` |PENDING| " dpdklab
2024-09-19 10:09 ` |SUCCESS| " dpdklab
2024-09-19 10:33 ` dpdklab
2024-09-19 14:15 ` |WARNING| " dpdklab
2024-09-19 15:13 ` |SUCCESS| " dpdklab
2024-09-19 16:38 ` dpdklab
2024-09-19 18:17 ` |WARNING| " dpdklab
2024-09-20 18:21 ` |SUCCESS| " dpdklab
2024-09-22 23:35 ` dpdklab
2024-09-22 23:46 ` 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=66ebecf0.050a0220.2ecec8.cf25SMTPIN_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).