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| pw131210 [PATCH] [v2] net/iavf: fix port stats not cleared
Date: Thu, 07 Sep 2023 08:00:31 -0700 (PDT)	[thread overview]
Message-ID: <64f9e58f.170a0220.33527.777fSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/131210

_Testing PASS_

Submitter: Yiding Zhou <yidingx.zhou@intel.com>
Date: Thursday, September 07 2023 02:39:42 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e92ba1426914db1d224dd5e9a1743657681b8814

131210 --> testing pass

Test environment and result as below:

+--------------------------+--------------------+
|       Environment        | dpdk_meson_compile |
+==========================+====================+
| Ubuntu 20.04 ARM SVE     | PASS               |
+--------------------------+--------------------+
| Ubuntu 20.04 (ARM)       | PASS               |
+--------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS               |
+--------------------------+--------------------+
| Fedora 38 (ARM)          | PASS               |
+--------------------------+--------------------+
| Fedora 37 (ARM)          | PASS               |
+--------------------------+--------------------+
| CentOS Stream 9 (ARM)    | PASS               |
+--------------------------+--------------------+


Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-80-generic
	Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)

Ubuntu 20.04 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 9.4.0

Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.3.1

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-09-07 15:00 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-07 15:00 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-09-07 16:44 dpdklab
2023-09-07 16:37 dpdklab
2023-09-07 16:36 dpdklab
2023-09-07 16:33 dpdklab
2023-09-07 16:31 dpdklab
2023-09-07 16:25 dpdklab
2023-09-07 16:22 dpdklab
2023-09-07 16:22 dpdklab
2023-09-07 16:16 dpdklab
2023-09-07 16:16 dpdklab
2023-09-07 16:12 dpdklab
2023-09-07 16:10 dpdklab
2023-09-07 16:05 dpdklab
2023-09-07 16:04 dpdklab
2023-09-07 16:01 dpdklab
2023-09-07 15:58 dpdklab
2023-09-07 15:55 dpdklab
2023-09-07 15:55 dpdklab
2023-09-07 15:54 dpdklab
2023-09-07 15:39 dpdklab
2023-09-07 15:34 dpdklab
2023-09-07 15:33 dpdklab
2023-09-07 15:29 dpdklab
2023-09-07 15:29 dpdklab
2023-09-07 15:26 dpdklab
2023-09-07 15:23 dpdklab
2023-09-07 15:17 dpdklab
2023-09-07 15:16 dpdklab
2023-09-07 15:15 dpdklab
2023-09-07 15:14 dpdklab
2023-09-07 15:14 dpdklab
2023-09-07 15:14 dpdklab
2023-09-07 15:09 dpdklab
2023-09-07 15:06 dpdklab
2023-09-07 15:05 dpdklab
2023-09-07 15:01 dpdklab
2023-09-07 15:01 dpdklab
2023-09-07 15:00 dpdklab
2023-09-07 15:00 dpdklab
2023-09-07 14:59 dpdklab
2023-09-07 14:59 dpdklab
2023-09-07 14:58 dpdklab
2023-09-07 14:57 dpdklab
2023-09-07 14:55 dpdklab
2023-09-07 14:55 dpdklab
2023-09-07 14:52 dpdklab
2023-09-07 14:52 dpdklab
2023-09-07 14:52 dpdklab
2023-09-07 14:52 dpdklab
2023-09-07 14:52 dpdklab
2023-09-07 14:51 dpdklab
     [not found] <20230907023942.3150495-1-yidingx.zhou@intel.com>
2023-09-07  2:18 ` |SUCCESS| pw131210 [PATCH v2] " qemudev
2023-09-07  2:22 ` qemudev
2023-09-07  3: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=64f9e58f.170a0220.33527.777fSMTPIN_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).