From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, "Zhang, Yuying" <yuying.zhang@intel.com>
Subject: |FAILURE| pw132073 [PATCH] [v1] net/idpf: fix incorrect status calcu
Date: Thu, 28 Sep 2023 02:56:54 -0700 (PDT) [thread overview]
Message-ID: <65154de6.920a0220.183ae.7638SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/132073
_Testing issues_
Submitter: Zhang, Yuying <yuying.zhang@intel.com>
Date: Thursday, September 28 2023 05:05:20
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c56185fc183fc0532d2f03aaf04bbf0989ea91a5
132073 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Fedora 38 | FAIL |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
==== 20 line log output for Fedora 38 (dpdk_unit_test): ====
97/107 DPDK:fast-tests / telemetry_data_autotest OK 0.22 s
98/107 DPDK:fast-tests / telemetry_json_autotest OK 0.22 s
99/107 DPDK:fast-tests / thash_autotest OK 0.22 s
100/107 DPDK:fast-tests / threads_autotest OK 0.37 s
101/107 DPDK:fast-tests / ticketlock_autotest OK 0.22 s
102/107 DPDK:fast-tests / timer_autotest OK 2.52 s
103/107 DPDK:fast-tests / trace_autotest OK 0.22 s
104/107 DPDK:fast-tests / trace_autotest_with_traces OK 0.22 s
105/107 DPDK:fast-tests / vdev_autotest OK 0.22 s
106/107 DPDK:fast-tests / version_autotest OK 0.22 s
107/107 DPDK:fast-tests / telemetry_all SKIP 0.01 s
Ok: 97
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 9
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)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27757/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-28 9:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 9:56 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-28 10:15 dpdklab
2023-09-28 10:12 dpdklab
2023-09-28 10:12 dpdklab
2023-09-28 10:07 dpdklab
2023-09-28 9:55 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=65154de6.920a0220.183ae.7638SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=yuying.zhang@intel.com \
/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).