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| pw144888 [PATCH] net/gve: always attempt Rx refill on DQ
Date: Tue, 01 Oct 2024 19:37:43 -0700 (PDT)	[thread overview]
Message-ID: <66fcb1f7.050a0220.17f69f.3dd6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241001234533.3308368-1-joshwash@google.com>

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

_Testing pending_

Submitter: Joshua Washington <joshwash@google.com>
Date: Tuesday, October 01 2024 23:45:33 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:aafa5ec4fcb4f9ac166cdbda2b1555f66e9ab188

144888 --> testing pending

Upstream job id: Generic-VM-DPDK-Compile-Meson#29871

Test environment and result as below:

+---------------------+-----------------------+-------------------+----------------------+--------------------+
|     Environment     | dpdk_win_llvm_compile | dpdk_msvc_compile | dpdk_mingw64_compile | dpdk_meson_compile |
+=====================+=======================+===================+======================+====================+
| Windows Server 2022 | PEND                  | PEND              | PEND                 | SKIPPED            |
+---------------------+-----------------------+-------------------+----------------------+--------------------+
| FreeBSD 13.4        | SKIPPED               | SKIPPED           | SKIPPED              | PASS               |
+---------------------+-----------------------+-------------------+----------------------+--------------------+
| FreeBSD 14.1        | SKIPPED               | SKIPPED           | SKIPPED              | PEND               |
+---------------------+-----------------------+-------------------+----------------------+--------------------+


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

FreeBSD 13.4
	Kernel: 13.4-RELEASE-p1
	Compiler: clang 18.1.6

FreeBSD 14.1
	Kernel: 14.1-RELEASE-p3
	Compiler: clang 18.1.5

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-10-02  2:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241001234533.3308368-1-joshwash@google.com>
2024-10-01 23:21 ` |SUCCESS| " qemudev
2024-10-01 23:25 ` qemudev
2024-10-01 23:45 ` checkpatch
2024-10-02  0:44 ` 0-day Robot
2024-10-02  2:37 ` dpdklab [this message]
2024-10-02  2:43 ` dpdklab
2024-10-02  2:51 ` dpdklab
2024-10-02  2:53 ` dpdklab
2024-10-02  2:55 ` dpdklab
2024-10-02  2:58 ` dpdklab
2024-10-02  3:00 ` |PENDING| " dpdklab
2024-10-02  3:06 ` |SUCCESS| " dpdklab
2024-10-02  3:10 ` |PENDING| " dpdklab
2024-10-02  3:20 ` |SUCCESS| " dpdklab
2024-10-02  3:40 ` dpdklab
2024-10-02  5:18 ` dpdklab
2024-10-02  5:44 ` dpdklab
2024-10-02  5:50 ` dpdklab
2024-10-02  6:13 ` dpdklab
2024-10-02  6:51 ` dpdklab
2024-10-02 10:14 ` |PENDING| " dpdklab
2024-10-02 11:00 ` |SUCCESS| " dpdklab
2024-10-02 13:27 ` dpdklab
2024-10-02 14:02 ` 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=66fcb1f7.050a0220.17f69f.3dd6SMTPIN_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).