From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>,
Jie Wang <jie1x.wang@intel.com>
Subject: |FAILURE| pw114861-114865 [PATCH] [v2, 5/5] net/iavf: support priority of flow rule
Date: Mon, 15 Aug 2022 17:16:41 +0000 (UTC) [thread overview]
Message-ID: <20220815171641.CD8906043F@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 3605 bytes --]
Test-Label: iol-x86_64-unit-testing
Test-Status: FAILURE
http://dpdk.org/patch/114865
_Testing issues_
Submitter: Jie Wang <jie1x.wang@intel.com>
Date: Friday, August 12 2022 17:04:47
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:72206323a5dd3182b13f61b25a64abdddfee595c
114861-114865 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| RHEL 7 | PASS |
+---------------------+----------------+
| Fedora 33 | FAIL |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| Fedora 34 | PASS |
+---------------------+----------------+
| Fedora 32 | PASS |
+---------------------+----------------+
| Fedora 31 | PASS |
+---------------------+----------------+
| Ubuntu 18.04 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| Fedora 34 clang | PASS |
+---------------------+----------------+
==== 20 line log output for Fedora 33 (dpdk_unit_test): ====
58/68 DPDK:fast-tests / trace_autotest OK 0.25 s
59/68 DPDK:fast-tests / trace_autotest_with_traces OK 0.18 s
60/68 DPDK:fast-tests / metrics_autotest OK 0.35 s
61/68 DPDK:fast-tests / telemetry_json_autotest OK 0.18 s
62/68 DPDK:fast-tests / telemetry_data_autotest OK 0.21 s
63/68 DPDK:fast-tests / table_autotest OK 7.02 s
64/68 DPDK:fast-tests / ring_pmd_autotest OK 0.17 s
65/68 DPDK:fast-tests / bitratestats_autotest OK 0.31 s
66/68 DPDK:fast-tests / latencystats_autotest OK 0.18 s
67/68 DPDK:fast-tests / pdump_autotest OK 0.33 s
68/68 DPDK:fast-tests / vdev_autotest OK 0.17 s
Ok: 65
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 2
Timeout: 0
Full log written to /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/build/meson-logs/testlog.txt
==== End log output ====
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
Fedora 33
Kernel: 5.4.0-72-generic
Compiler: gcc 10.3.1 20210422 (Red Hat 10.3.1-1)
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
Fedora 34
Kernel: 5.4.0-72-generic
Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-1)
Fedora 32
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 10.2.1
Fedora 31
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.1
Ubuntu 18.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0-3ubuntu1~18.04
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Fedora 34 clang
Kernel: 5.4.0-72-generic
Compiler: clang 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/23211/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
reply other threads:[~2022-08-15 17:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220815171641.CD8906043F@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=jie1x.wang@intel.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).