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| pw142004-142006 [PATCH] [v5,3/3] bus/pci: fix secondary pr
Date: Mon, 01 Jul 2024 23:02:44 -0700 (PDT)	[thread overview]
Message-ID: <66839804.c80a0220.6b38b.c066SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240702021946.4194102-4-chaoyong.he@corigine.com>

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

_Testing pending_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Tuesday, July 02 2024 02:19:46 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c15902587b538ff02cfb0fbb4dd481f1503d936b

142004-142006 --> testing pending

Test environment and result as below:

+---------------------+--------------------+----------------------+-------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_msvc_compile |
+=====================+====================+======================+===================+
| Windows Server 2019 | PEND               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2022 | PASS               | PEND                 | PEND              |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 13.3        | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 14.1        | PEND               | SKIPPED              | 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/30367/

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-02  6:02 UTC|newest]

Thread overview: 109+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240702021946.4194102-4-chaoyong.he@corigine.com>
2024-07-02  1:53 ` |SUCCESS| pw142004-142006 [PATCH v5 3/3] bus/pci: fix secondary process save 'FD' problem qemudev
2024-07-02  1:58 ` qemudev
2024-07-02  2:21 ` |SUCCESS| pw142006 " checkpatch
2024-07-02  3:25 ` 0-day Robot
2024-07-02  4:51 ` |SUCCESS| pw142004-142006 [PATCH] [v5,3/3] bus/pci: fix secondary pr dpdklab
2024-07-02  4:53 ` dpdklab
2024-07-02  4:56 ` dpdklab
2024-07-02  4:56 ` dpdklab
2024-07-02  4:57 ` dpdklab
2024-07-02  5:01 ` dpdklab
2024-07-02  5:16 ` dpdklab
2024-07-02  5:20 ` dpdklab
2024-07-02  5:30 ` dpdklab
2024-07-02  6:02 ` dpdklab [this message]
2024-07-02  6:04 ` |PENDING| " dpdklab
2024-07-02  6:07 ` dpdklab
2024-07-02  6:08 ` dpdklab
2024-07-02  6:08 ` dpdklab
2024-07-02  6:09 ` dpdklab
2024-07-02  6:11 ` |SUCCESS| " dpdklab
2024-07-02  6:23 ` |PENDING| " dpdklab
2024-07-02  6:31 ` dpdklab
2024-07-02  6:44 ` dpdklab
2024-07-02  6:52 ` dpdklab
2024-07-02  7:03 ` dpdklab
2024-07-02  7:17 ` dpdklab
2024-07-02  7:20 ` dpdklab
2024-07-02  7:23 ` dpdklab
2024-07-02  7:24 ` dpdklab
2024-07-02  7:24 ` dpdklab
2024-07-02  7:28 ` dpdklab
2024-07-02  7:29 ` dpdklab
2024-07-02  7:29 ` dpdklab
2024-07-02  7:30 ` dpdklab
2024-07-02  7:30 ` dpdklab
2024-07-02  7:31 ` dpdklab
2024-07-02  7:31 ` dpdklab
2024-07-02  7:32 ` dpdklab
2024-07-02  7:33 ` dpdklab
2024-07-02  7:37 ` dpdklab
2024-07-02  7:38 ` dpdklab
2024-07-02  7:44 ` dpdklab
2024-07-02  7:44 ` dpdklab
2024-07-02  7:46 ` dpdklab
2024-07-02  7:47 ` dpdklab
2024-07-02  7:47 ` dpdklab
2024-07-02  7:49 ` dpdklab
2024-07-02  7:49 ` dpdklab
2024-07-02  7:50 ` dpdklab
2024-07-02  7:51 ` dpdklab
2024-07-02  7:54 ` dpdklab
2024-07-02  7:54 ` |SUCCESS| " dpdklab
2024-07-02  7:54 ` |PENDING| " dpdklab
2024-07-02  7:54 ` dpdklab
2024-07-02  7:58 ` dpdklab
2024-07-02  7:59 ` dpdklab
2024-07-02  8:01 ` |SUCCESS| " dpdklab
2024-07-02  8:50 ` |PENDING| " dpdklab
2024-07-02  8:53 ` dpdklab
2024-07-02  8:56 ` dpdklab
2024-07-02  9:02 ` dpdklab
2024-07-02  9:07 ` dpdklab
2024-07-02  9:07 ` dpdklab
2024-07-02  9:10 ` dpdklab
2024-07-02  9:12 ` dpdklab
2024-07-02  9:12 ` dpdklab
2024-07-02  9:14 ` dpdklab
2024-07-02  9:17 ` dpdklab
2024-07-02  9:17 ` dpdklab
2024-07-02  9:18 ` dpdklab
2024-07-02  9:22 ` dpdklab
2024-07-02  9:24 ` dpdklab
2024-07-02  9:25 ` dpdklab
2024-07-02  9:29 ` dpdklab
2024-07-02  9:29 ` dpdklab
2024-07-02  9:30 ` dpdklab
2024-07-02  9:36 ` dpdklab
2024-07-02  9:37 ` dpdklab
2024-07-02  9:42 ` dpdklab
2024-07-02  9:42 ` dpdklab
2024-07-02  9:43 ` dpdklab
2024-07-02  9:43 ` dpdklab
2024-07-02  9:44 ` dpdklab
2024-07-02  9:46 ` dpdklab
2024-07-02  9:50 ` |SUCCESS| " dpdklab
2024-07-02  9:51 ` dpdklab
2024-07-02 10:13 ` |PENDING| " dpdklab
2024-07-02 10:24 ` dpdklab
2024-07-02 10:26 ` dpdklab
2024-07-02 10:32 ` |SUCCESS| " dpdklab
2024-07-02 12:33 ` |PENDING| " dpdklab
2024-07-02 12:34 ` dpdklab
2024-07-02 12:39 ` dpdklab
2024-07-02 12:42 ` dpdklab
2024-07-02 12:45 ` dpdklab
2024-07-02 12:49 ` dpdklab
2024-07-02 12:54 ` dpdklab
2024-07-02 13:01 ` dpdklab
2024-07-02 13:19 ` dpdklab
2024-07-02 13:28 ` dpdklab
2024-07-02 13:30 ` dpdklab
2024-07-02 13:37 ` dpdklab
2024-07-02 13:44 ` dpdklab
2024-07-02 13:53 ` dpdklab
2024-07-02 14:02 ` |SUCCESS| " dpdklab
2024-07-02 14:19 ` dpdklab
2024-07-02 17:37 ` dpdklab
2024-07-02 17:51 ` dpdklab
2024-07-02 19:03 ` 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=66839804.c80a0220.6b38b.c066SMTPIN_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).