automatic DPDK test reports
 help / color / mirror / Atom feed
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>,
	Zhichao Zeng <zhichaox.zeng@intel.com>
Subject: |FAILURE| pw124096 [PATCH] [v3] net/iavf: enable Tx outer checksum offload on avx512
Date: Fri, 17 Feb 2023 04:54:46 +0000 (UTC)	[thread overview]
Message-ID: <20230217045446.98D14600AB@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

Test-Label: iol-testing
Test-Status: FAILURE
http://dpdk.org/patch/124096

_Testing issues_

Submitter: Zhichao Zeng <zhichaox.zeng@intel.com>
Date: Friday, February 17 2023 01:49:24 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:81cf20a25abfee8f09a52968e3846791b6029719

124096 --> testing fail

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | FAIL           |
+---------------------+----------------+
| RHEL8               | PASS           |
+---------------------+----------------+
| RHEL 7              | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| Ubuntu 22.04        | PASS           |
+---------------------+----------------+
| Ubuntu 20.04        | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| CentOS Stream 9     | FAIL           |
+---------------------+----------------+

==== 20 line log output for CentOS Stream 9 (dpdk_unit_test): ====
93/103 DPDK:fast-tests / telemetry_json_autotest  OK       0.22 s
94/103 DPDK:fast-tests / telemetry_data_autotest  OK       0.17 s
95/103 DPDK:fast-tests / table_autotest        OK      13.87 s
96/103 DPDK:fast-tests / ring_pmd_autotest     OK       0.27 s
97/103 DPDK:fast-tests / event_eth_tx_adapter_autotest  OK       0.77 s
98/103 DPDK:fast-tests / bitratestats_autotest  OK       0.22 s
99/103 DPDK:fast-tests / latencystats_autotest  OK       0.17 s
100/103 DPDK:fast-tests / pdump_autotest        OK       5.33 s
101/103 DPDK:fast-tests / vdev_autotest         OK       0.17 s
102/103 DPDK:fast-tests / compressdev_autotest  SKIP     0.17 s
103/103 DPDK:fast-tests / telemetry_all         SKIP     0.01 s

Ok:                   93
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)

RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

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)

Debian Bullseye
	Kernel: 5.4.0-122-generic
	Compiler: gcc 10.2.1-6

Ubuntu 22.04
	Kernel: Container Host Kernel
	Compiler: clang 14.0.5-1.fc36

Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-02-17  4:54 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17  4:54 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-17  9:55 dpdklab
2023-02-17  9:55 dpdklab
2023-02-17  9:49 dpdklab
2023-02-17  9:43 dpdklab
2023-02-17  9:39 dpdklab
2023-02-17  9:37 dpdklab
2023-02-17  9:37 dpdklab
2023-02-17  9:36 dpdklab
2023-02-17  9:33 dpdklab
2023-02-17  9:28 dpdklab
2023-02-17  9:25 dpdklab
2023-02-17  9:22 dpdklab
2023-02-17  9:16 dpdklab
2023-02-17  6:16 dpdklab
2023-02-17  6:16 dpdklab
2023-02-17  6:12 dpdklab
2023-02-17  6:08 dpdklab
2023-02-17  6:08 dpdklab
2023-02-17  6:05 dpdklab
2023-02-17  6:05 dpdklab
2023-02-17  6:02 dpdklab
2023-02-17  6:00 dpdklab
2023-02-17  5:58 dpdklab
2023-02-17  5:56 dpdklab
2023-02-17  5:55 dpdklab
2023-02-17  5:54 dpdklab
2023-02-17  5:52 dpdklab
2023-02-17  5:43 dpdklab
2023-02-17  5:42 dpdklab
2023-02-17  5:41 dpdklab
2023-02-17  5:37 dpdklab
2023-02-17  4:58 dpdklab
2023-02-17  4:57 dpdklab
2023-02-17  4:56 dpdklab
2023-02-17  4:52 dpdklab
2023-02-17  4:46 dpdklab
2023-02-17  4:45 dpdklab
2023-02-17  4:37 dpdklab
2023-02-17  4:36 dpdklab
2023-02-17  4:35 dpdklab
2023-02-17  4:34 dpdklab
2023-02-17  4:23 dpdklab
2023-02-17  4:22 dpdklab
2023-02-17  4:16 dpdklab
2023-02-17  4:16 dpdklab
2023-02-17  4:02 dpdklab
2023-02-17  4:00 dpdklab
     [not found] <20230217014924.385709-1-zhichaox.zeng@intel.com>
2023-02-17  3:59 ` |FAILURE| pw124096 [PATCH v3] " 0-day Robot
2023-02-17  3:58 |FAILURE| pw124096 [PATCH] [v3] " dpdklab
2023-02-17  3:54 dpdklab
2023-02-17  3:52 dpdklab
2023-02-17  3:47 dpdklab
2023-02-17  3:45 dpdklab
2023-02-17  3:34 dpdklab
2023-02-17  3:20 dpdklab
2023-02-17  3:16 dpdklab
2023-02-17  3:14 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=20230217045446.98D14600AB@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=zhichaox.zeng@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).