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: |SUCCESS| pw133867 [PATCH] net/bnxt: fix deadlock in mgr timer cb
Date: Fri, 03 Nov 2023 22:30:41 -0700 (PDT)	[thread overview]
Message-ID: <6545d701.920a0220.47e2.7859SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/133867

_Testing PASS_

Submitter: Weiguo Li <liwg06@foxmail.com>
Date: Saturday, November 04 2023 04:06:58 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:34c0c38ab772e8eea5243f530866d5b68519e7c7

133867 --> testing pass

Test environment and result as below:

+---------------------+--------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13          | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS               | PASS                 |
+---------------------+--------------------+----------------------+


FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-11-04  5:30 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-04  5:30 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-06 15:26 dpdklab
2023-11-04 11:01 dpdklab
2023-11-04 10:58 dpdklab
2023-11-04  9:09 dpdklab
2023-11-04  9:07 dpdklab
2023-11-04  9:04 dpdklab
2023-11-04  9:03 dpdklab
2023-11-04  9:03 dpdklab
2023-11-04  9:02 dpdklab
2023-11-04  9:02 dpdklab
2023-11-04  9:02 dpdklab
2023-11-04  9:02 dpdklab
2023-11-04  9:01 dpdklab
2023-11-04  8:58 dpdklab
2023-11-04  8:57 dpdklab
2023-11-04  8:53 dpdklab
2023-11-04  8:52 dpdklab
2023-11-04  8:52 dpdklab
2023-11-04  8:52 dpdklab
2023-11-04  8:51 dpdklab
2023-11-04  8:51 dpdklab
2023-11-04  8:50 dpdklab
2023-11-04  8:50 dpdklab
2023-11-04  8:49 dpdklab
2023-11-04  8:48 dpdklab
2023-11-04  8:47 dpdklab
2023-11-04  8:37 dpdklab
2023-11-04  8:25 dpdklab
2023-11-04  8:17 dpdklab
2023-11-04  8:01 dpdklab
2023-11-04  7:56 dpdklab
2023-11-04  7:55 dpdklab
2023-11-04  7:55 dpdklab
2023-11-04  7:55 dpdklab
2023-11-04  6:29 dpdklab
2023-11-04  6:10 dpdklab
2023-11-04  5:59 dpdklab
2023-11-04  5:55 dpdklab
2023-11-04  5:55 dpdklab
2023-11-04  5:55 dpdklab
2023-11-04  5:49 dpdklab
2023-11-04  5:49 dpdklab
2023-11-04  5:42 dpdklab
2023-11-04  5:40 dpdklab
2023-11-04  5:39 dpdklab
2023-11-04  5:39 dpdklab
2023-11-04  5:38 dpdklab
2023-11-04  5:38 dpdklab
2023-11-04  5:37 dpdklab
2023-11-04  5:36 dpdklab
2023-11-04  5:35 dpdklab
2023-11-04  5:35 dpdklab
2023-11-04  5:32 dpdklab
2023-11-04  5:32 dpdklab
     [not found] <tencent_7B6D2301220A31DB3CA9A701112E3A47DF08@qq.com>
2023-11-04  3:59 ` qemudev
2023-11-04  4:03 ` qemudev
2023-11-04  5:19 ` 0-day Robot

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=6545d701.920a0220.47e2.7859SMTPIN_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).