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| pw143118 [PATCH] [v1] dts: correct typos in conf.yaml
Date: Tue, 13 Aug 2024 11:13:30 -0700 (PDT)	[thread overview]
Message-ID: <66bba24a.250a0220.548bf.a106SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240813171745.24049-1-dmarx@iol.unh.edu>

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

_Testing pending_

Submitter: Dean Marx <dmarx@iol.unh.edu>
Date: Tuesday, August 13 2024 17:17:45 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:cb9187bc5c2b4bab0ad80194ac3b60491de14e8c

143118 --> testing pending

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

Test environment and result as below:

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


Windows Server 2019
	Kernel: 10.0.17763
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

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

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

Debian Bullseye
	Kernel: 5.4.0-167-generic
	Compiler: gcc 10.2.1-6

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 38 (Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.6

Fedora 39
	Kernel: Depends on container host
	Compiler: gcc 13.2.1

Fedora 39 (Clang)
	Kernel: Depends on container host
	Compiler: clang 17.0.6

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-08-13 18:13 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240813171745.24049-1-dmarx@iol.unh.edu>
2024-08-13 16:53 ` |SUCCESS| pw143118 [PATCH v1] " qemudev
2024-08-13 16:57 ` qemudev
2024-08-13 17:17 ` checkpatch
2024-08-13 17:49 ` |SUCCESS| pw143118 [PATCH] [v1] " dpdklab
2024-08-13 17:50 ` |PENDING| " dpdklab
2024-08-13 17:50 ` dpdklab
2024-08-13 17:51 ` |SUCCESS| " dpdklab
2024-08-13 17:52 ` dpdklab
2024-08-13 17:56 ` |PENDING| " dpdklab
2024-08-13 17:56 ` |SUCCESS| " dpdklab
2024-08-13 17:58 ` |PENDING| " dpdklab
2024-08-13 18:00 ` |SUCCESS| " dpdklab
2024-08-13 18:00 ` dpdklab
2024-08-13 18:01 ` dpdklab
2024-08-13 18:01 ` |PENDING| " dpdklab
2024-08-13 18:02 ` dpdklab
2024-08-13 18:02 ` |SUCCESS| pw143118 [PATCH v1] " 0-day Robot
2024-08-13 18:02 ` |PENDING| pw143118 [PATCH] [v1] " dpdklab
2024-08-13 18:03 ` dpdklab
2024-08-13 18:03 ` dpdklab
2024-08-13 18:04 ` dpdklab
2024-08-13 18:04 ` dpdklab
2024-08-13 18:06 ` dpdklab
2024-08-13 18:06 ` dpdklab
2024-08-13 18:06 ` dpdklab
2024-08-13 18:07 ` dpdklab
2024-08-13 18:09 ` dpdklab
2024-08-13 18:09 ` dpdklab
2024-08-13 18:10 ` dpdklab
2024-08-13 18:10 ` dpdklab
2024-08-13 18:10 ` |SUCCESS| " dpdklab
2024-08-13 18:10 ` |PENDING| " dpdklab
2024-08-13 18:10 ` dpdklab
2024-08-13 18:11 ` dpdklab
2024-08-13 18:11 ` dpdklab
2024-08-13 18:11 ` dpdklab
2024-08-13 18:11 ` dpdklab
2024-08-13 18:12 ` dpdklab
2024-08-13 18:12 ` dpdklab
2024-08-13 18:12 ` dpdklab
2024-08-13 18:13 ` dpdklab
2024-08-13 18:13 ` |SUCCESS| " dpdklab
2024-08-13 18:13 ` dpdklab [this message]
2024-08-13 18:13 ` |PENDING| " dpdklab
2024-08-13 18:14 ` |SUCCESS| " dpdklab
2024-08-13 18:14 ` |PENDING| " dpdklab
2024-08-13 18:14 ` |SUCCESS| " dpdklab
2024-08-13 18:15 ` |PENDING| " dpdklab
2024-08-13 18:16 ` dpdklab
2024-08-13 18:17 ` dpdklab
2024-08-13 18:18 ` dpdklab
2024-08-13 18:18 ` |SUCCESS| " dpdklab
2024-08-13 18:19 ` |PENDING| " dpdklab
2024-08-13 18:19 ` dpdklab
2024-08-13 18:21 ` dpdklab
2024-08-13 18:21 ` |SUCCESS| " dpdklab
2024-08-13 18:21 ` |PENDING| " dpdklab
2024-08-13 18:22 ` dpdklab
2024-08-13 18:23 ` dpdklab
2024-08-13 18:23 ` |SUCCESS| " dpdklab
2024-08-13 18:23 ` |PENDING| " dpdklab
2024-08-13 18:24 ` dpdklab
2024-08-13 18:24 ` dpdklab
2024-08-13 18:25 ` dpdklab
2024-08-13 18:26 ` dpdklab
2024-08-13 18:26 ` dpdklab
2024-08-13 18:26 ` dpdklab
2024-08-13 18:27 ` dpdklab
2024-08-13 18:27 ` dpdklab
2024-08-13 18:28 ` dpdklab
2024-08-13 18:29 ` dpdklab
2024-08-13 18:29 ` dpdklab
2024-08-13 18:30 ` dpdklab
2024-08-13 18:31 ` dpdklab
2024-08-13 18:32 ` dpdklab
2024-08-13 18:33 ` dpdklab
2024-08-13 18:34 ` |SUCCESS| " dpdklab
2024-08-13 18:35 ` dpdklab
2024-08-13 18:39 ` |PENDING| " dpdklab
2024-08-13 18:39 ` dpdklab
2024-08-13 18:41 ` dpdklab
2024-08-13 18:43 ` |SUCCESS| " dpdklab
2024-08-13 18:48 ` dpdklab
2024-08-13 18:49 ` dpdklab
2024-08-13 18:50 ` dpdklab
2024-08-13 18:52 ` dpdklab
2024-08-13 18:55 ` dpdklab
2024-08-13 18:56 ` dpdklab
2024-08-13 19:33 ` |PENDING| " dpdklab
2024-08-13 19:36 ` dpdklab
2024-08-13 19:40 ` |SUCCESS| " dpdklab
2024-08-13 19:50 ` 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=66bba24a.250a0220.548bf.a106SMTPIN_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).