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: [dpdk-test-report] |SUCCESS| pw84653 [PATCH] [v1] net/iavf: support FDIR TCP/UDP pattern without input set
Date: Tue,  1 Dec 2020 04:44:42 -0500 (EST)	[thread overview]
Message-ID: <20201201094442.C65C5B0FB@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 2333 bytes --]

Test-Label: iol-testing
Test-Status: SUCCESS
http://dpdk.org/patch/84653

_Testing PASS_

Submitter: Yuying Zhang <yuying.zhang@intel.com>
Date: Tuesday, December 01 2020 08:32:07 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:d3fa7b89f0b893f051cb4cef1cbc961cb59f5721

84653 --> testing pass

Test environment and result as below:

+---------------------+--------------------+-------------------+----------------+
|     Environment     | dpdk_meson_compile | dpdk_compile_spdk | dpdk_unit_test |
+=====================+====================+===================+================+
| Windows Server 2019 | PASS               | SKIPPED           | SKIPPED        |
+---------------------+--------------------+-------------------+----------------+
| FreeBSD 11.2        | PASS               | SKIPPED           | SKIPPED        |
+---------------------+--------------------+-------------------+----------------+
| CentOS 8            | PASS               | SKIPPED           | SKIPPED        |
+---------------------+--------------------+-------------------+----------------+
| Fedora 31           | PASS               | SKIPPED           | SKIPPED        |
+---------------------+--------------------+-------------------+----------------+
| Ubuntu 18.04        | PASS               | PASS              | PASS           |
+---------------------+--------------------+-------------------+----------------+
| openSUSE Leap 15    | PASS               | SKIPPED           | SKIPPED        |
+---------------------+--------------------+-------------------+----------------+
| Arch Linux          | PASS               | SKIPPED           | SKIPPED        |
+---------------------+--------------------+-------------------+----------------+

Windows Server 2019
	Kernel: 10.0
	Compiler: clang 9.0

FreeBSD 11.2
	Kernel: 11.2
	Compiler: gcc 8.3

CentOS 8
	Kernel: 4.18.0.el8_0
	Compiler: gcc 8.3.1

Fedora 31
	Kernel: 5.3.16
	Compiler: gcc 9.2.1

Ubuntu 18.04
	Kernel: 4.15.0-generic
	Compiler: gcc 7.5

openSUSE Leap 15
	Kernel: 4.12.14
	Compiler: gcc 7.4.1

Arch Linux
	Kernel: latest
	Compiler: gcc latest

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2020-12-01  9:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-01  9:44 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-12-01 11:18 dpdklab
2020-12-01  9:55 dpdklab
2020-12-01  9:45 dpdklab
2020-12-01  9:35 dpdklab
2020-12-01  9:28 dpdklab
     [not found] <20201201083207.70668-1-yuying.zhang@intel.com>
2020-12-01  8:38 ` [dpdk-test-report] |SUCCESS| pw84653 [PATCH v1] " checkpatch

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=20201201094442.C65C5B0FB@noxus.dpdklab.iol.unh.edu \
    --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).