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| pw142511-142512 [PATCH] [2/2] doc: remove use of -n 4 opti
Date: Fri, 19 Jul 2024 06:32:14 -0700 (PDT)	[thread overview]
Message-ID: <669a6ade.050a0220.fa03e.36c7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240718184326.21375-2-stephen@networkplumber.org>

Test-Label: iol-compile-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/142512

_Testing pending_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, July 18 2024 18:43:26 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fa8d2f7f28524a6c8defa3dcd94f5aa131aae084

142511-142512 --> testing pending

Upstream job id: Windows-Compile-DPDK-Mingw64#20847

Test environment and result as below:

+---------------------+--------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2019 | PASS               | PASS                 |
+---------------------+--------------------+----------------------+
| Windows Server 2022 | PASS               | PEND                 |
+---------------------+--------------------+----------------------+
| FreeBSD 13.3        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| FreeBSD 14.1        | PEND               | SKIPPED              |
+---------------------+--------------------+----------------------+


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

FreeBSD 13.3
	Kernel: 13.3-RELEASE-p1
	Compiler: clang 17.0.6

FreeBSD 14.1
	Kernel: 14.1
	Compiler: clang 18.1.5

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-07-19 13:32 UTC|newest]

Thread overview: 116+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240718184326.21375-2-stephen@networkplumber.org>
2024-07-18 18:17 ` |SUCCESS| pw142511-142512 [PATCH 2/2] doc: remove use of -n 4 option in documentation qemudev
2024-07-18 18:22 ` qemudev
2024-07-18 18:44 ` |WARNING| pw142512 " checkpatch
2024-07-18 19:43 ` |SUCCESS| " 0-day Robot
2024-07-19 11:16 ` |SUCCESS| pw142511-142512 [PATCH] [2/2] doc: remove use of -n 4 opti dpdklab
2024-07-19 11:20 ` dpdklab
2024-07-19 11:24 ` dpdklab
2024-07-19 11:24 ` dpdklab
2024-07-19 11:37 ` dpdklab
2024-07-19 11:37 ` dpdklab
2024-07-19 11:39 ` dpdklab
2024-07-19 11:50 ` dpdklab
2024-07-19 12:27 ` |PENDING| " dpdklab
2024-07-19 12:35 ` |SUCCESS| " dpdklab
2024-07-19 12:39 ` dpdklab
2024-07-19 13:10 ` dpdklab
2024-07-19 13:14 ` |PENDING| " dpdklab
2024-07-19 13:26 ` dpdklab
2024-07-19 13:26 ` dpdklab
2024-07-19 13:27 ` dpdklab
2024-07-19 13:28 ` dpdklab
2024-07-19 13:31 ` dpdklab
2024-07-19 13:32 ` dpdklab [this message]
2024-07-19 13:34 ` dpdklab
2024-07-19 13:34 ` dpdklab
2024-07-19 13:36 ` dpdklab
2024-07-19 13:36 ` dpdklab
2024-07-19 13:36 ` dpdklab
2024-07-19 13:40 ` dpdklab
2024-07-19 13:40 ` dpdklab
2024-07-19 13:41 ` dpdklab
2024-07-19 13:42 ` |SUCCESS| " dpdklab
2024-07-19 13:43 ` |PENDING| " dpdklab
2024-07-19 13:44 ` dpdklab
2024-07-19 13:45 ` dpdklab
2024-07-19 13:47 ` dpdklab
2024-07-19 13:48 ` dpdklab
2024-07-19 13:49 ` dpdklab
2024-07-19 13:50 ` dpdklab
2024-07-19 13:50 ` dpdklab
2024-07-19 13:50 ` dpdklab
2024-07-19 13:52 ` dpdklab
2024-07-19 13:54 ` dpdklab
2024-07-19 14:01 ` dpdklab
2024-07-19 14:02 ` dpdklab
2024-07-19 14:02 ` dpdklab
2024-07-19 14:06 ` |SUCCESS| " dpdklab
2024-07-19 14:08 ` |PENDING| " dpdklab
2024-07-19 14:13 ` dpdklab
2024-07-19 14:14 ` dpdklab
2024-07-19 14:14 ` dpdklab
2024-07-19 14:15 ` dpdklab
2024-07-19 14:15 ` dpdklab
2024-07-19 14:16 ` dpdklab
2024-07-19 14:18 ` dpdklab
2024-07-19 14:19 ` dpdklab
2024-07-19 14:19 ` dpdklab
2024-07-19 14:21 ` dpdklab
2024-07-19 14:23 ` dpdklab
2024-07-19 14:23 ` dpdklab
2024-07-19 14:24 ` dpdklab
2024-07-19 14:24 ` dpdklab
2024-07-19 14:26 ` dpdklab
2024-07-19 14:28 ` dpdklab
2024-07-19 14:28 ` dpdklab
2024-07-19 14:28 ` dpdklab
2024-07-19 14:28 ` dpdklab
2024-07-19 14:29 ` dpdklab
2024-07-19 14:29 ` dpdklab
2024-07-19 14:30 ` dpdklab
2024-07-19 14:30 ` dpdklab
2024-07-19 14:30 ` |SUCCESS| " dpdklab
2024-07-19 14:31 ` |PENDING| " dpdklab
2024-07-19 14:31 ` dpdklab
2024-07-19 14:32 ` dpdklab
2024-07-19 14:32 ` dpdklab
2024-07-19 14:33 ` dpdklab
2024-07-19 14:33 ` dpdklab
2024-07-19 14:35 ` |SUCCESS| " dpdklab
2024-07-19 14:36 ` |PENDING| " dpdklab
2024-07-19 14:37 ` dpdklab
2024-07-19 14:38 ` dpdklab
2024-07-19 14:39 ` |SUCCESS| " dpdklab
2024-07-19 14:40 ` |PENDING| " dpdklab
2024-07-19 14:40 ` dpdklab
2024-07-19 14:42 ` dpdklab
2024-07-19 14:42 ` dpdklab
2024-07-19 14:46 ` dpdklab
2024-07-19 14:51 ` |SUCCESS| " dpdklab
2024-07-19 14:58 ` dpdklab
2024-07-19 15:29 ` dpdklab
2024-07-19 15:31 ` |PENDING| " dpdklab
2024-07-19 15:32 ` dpdklab
2024-07-19 15:32 ` dpdklab
2024-07-19 15:33 ` dpdklab
2024-07-19 15:34 ` dpdklab
2024-07-19 15:35 ` dpdklab
2024-07-19 15:36 ` dpdklab
2024-07-19 15:38 ` dpdklab
2024-07-19 15:38 ` dpdklab
2024-07-19 15:39 ` dpdklab
2024-07-19 15:41 ` |SUCCESS| " dpdklab
2024-07-19 15:42 ` |PENDING| " dpdklab
2024-07-19 15:48 ` dpdklab
2024-07-19 15:49 ` dpdklab
2024-07-19 15:49 ` dpdklab
2024-07-19 15:50 ` dpdklab
2024-07-19 15:51 ` dpdklab
2024-07-19 15:52 ` dpdklab
2024-07-19 15:52 ` dpdklab
2024-07-19 15:55 ` dpdklab
2024-07-19 16:01 ` dpdklab
2024-07-19 16:04 ` |SUCCESS| " dpdklab
2024-07-19 16:05 ` |PENDING| " dpdklab
2024-07-19 16:12 ` |SUCCESS| " dpdklab
2024-07-19 22:25 ` 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=669a6ade.050a0220.fa03e.36c7SMTPIN_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).