automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Xing@dpdk.org, Beilei <beilei.xing@intel.com>,
	dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135881 [PATCH] maintainers: update for i40e/iavf/idpf/cp
Date: Mon, 15 Jan 2024 23:51:25 -0800 (PST)	[thread overview]
Message-ID: <65a6357d.0c0a0220.287fc.0c77SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135881

_Testing PASS_

Submitter: Xing, Beilei <beilei.xing@intel.com>
Date: Tuesday, January 16 2024 13:32:18 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:d4af9a82063e4c39568191eaa12955d3ca39581a

135881 --> testing pass

Test environment and result as below:

+--------------------------+----------------+---------------------------+
|       Environment        | dpdk_unit_test | cryptodev_sw_zuc_autotest |
+==========================+================+===========================+
| Debian 11 (Buster) (ARM) | PASS           | SKIPPED                   |
+--------------------------+----------------+---------------------------+
| Fedora 38 (ARM)          | PASS           | SKIPPED                   |
+--------------------------+----------------+---------------------------+
| CentOS Stream 9 (ARM)    | PASS           | SKIPPED                   |
+--------------------------+----------------+---------------------------+
| Debian 11 (arm)          | SKIPPED        | PASS                      |
+--------------------------+----------------+---------------------------+


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

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

Debian 11 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-16  7:51 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-16  7:51 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-16 10:25 dpdklab
2024-01-16  9:53 dpdklab
2024-01-16  9:19 dpdklab
2024-01-16  8:22 dpdklab
2024-01-16  8:21 dpdklab
2024-01-16  8:21 dpdklab
2024-01-16  8:19 dpdklab
2024-01-16  8:19 dpdklab
2024-01-16  8:17 dpdklab
2024-01-16  8:15 dpdklab
2024-01-16  8:14 dpdklab
2024-01-16  8:14 dpdklab
2024-01-16  8:13 dpdklab
2024-01-16  8:11 dpdklab
2024-01-16  8:10 dpdklab
2024-01-16  8:08 dpdklab
2024-01-16  8:07 dpdklab
2024-01-16  8:05 dpdklab
2024-01-16  8:05 dpdklab
2024-01-16  8:05 dpdklab
2024-01-16  8:04 dpdklab
2024-01-16  8:03 dpdklab
2024-01-16  8:01 dpdklab
2024-01-16  8:01 dpdklab
2024-01-16  8:00 dpdklab
2024-01-16  7:57 dpdklab
2024-01-16  7:56 dpdklab
2024-01-16  7:56 dpdklab
2024-01-16  7:56 dpdklab
2024-01-16  7:55 dpdklab
2024-01-16  7:55 dpdklab
2024-01-16  7:55 dpdklab
2024-01-16  7:53 dpdklab
2024-01-16  7:53 dpdklab
2024-01-16  7:53 dpdklab
2024-01-16  7:53 dpdklab
2024-01-16  7:52 dpdklab
2024-01-16  7:52 dpdklab
2024-01-16  7:52 dpdklab
2024-01-16  7:51 dpdklab
2024-01-16  7:51 dpdklab
2024-01-16  7:51 dpdklab
2024-01-16  7:50 dpdklab
2024-01-16  7:50 dpdklab
2024-01-16  7:49 dpdklab
2024-01-16  7:49 dpdklab
2024-01-16  7:49 dpdklab
2024-01-16  7:49 dpdklab
2024-01-16  7:49 dpdklab
2024-01-16  7:49 dpdklab
2024-01-16  7:48 dpdklab
2024-01-16  7:48 dpdklab
2024-01-16  7:48 dpdklab
2024-01-16  7:48 dpdklab
2024-01-16  7:47 dpdklab
2024-01-16  7:46 dpdklab
2024-01-16  7:45 dpdklab
2024-01-16  7:45 dpdklab
2024-01-16  7:43 dpdklab
2024-01-16  7:42 dpdklab
2024-01-16  7:25 dpdklab
2024-01-16  7:21 dpdklab
2024-01-16  7:19 dpdklab
2024-01-16  7:19 dpdklab
2024-01-16  7:17 dpdklab
2024-01-16  7:13 dpdklab
2024-01-16  7:12 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=65a6357d.0c0a0220.287fc.0c77SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=Xing@dpdk.org \
    --cc=beilei.xing@intel.com \
    --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).