From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Gavin Li <gavinl@nvidia.com>
Subject: |FAILURE| pw140429 [PATCH] net/mlx5: fix flow discover IPv6 traffic
Date: Thu, 30 May 2024 00:24:13 -0700 (PDT) [thread overview]
Message-ID: <6658299d.050a0220.45941.c1dbSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240530034252.198797-1-gavinl@nvidia.com>
Test-Label: iol-compile-arm64-testing
Test-Status: FAILURE
http://dpdk.org/patch/140429
_Testing issues_
Submitter: Gavin Li <gavinl@nvidia.com>
Date: Thursday, May 30 2024 03:42:52
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:5d185b9afaca3c98d8fd779e97d83e571660f4cf
140429 --> testing issues
Test environment and result as below:
+---------------------+--------------------+----------------------+------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_compile_ovs |
+=====================+====================+======================+==================+
| FreeBSD 13.3 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+------------------+
| Windows Server 2022 | PASS | PASS | SKIPPED |
+---------------------+--------------------+----------------------+------------------+
| FreeBSD 14.0 | PASS | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+------------------+
| Windows Server 2019 | PASS | PASS | SKIPPED |
+---------------------+--------------------+----------------------+------------------+
| CentOS Stream 8 | PASS | SKIPPED | PASS |
+---------------------+--------------------+----------------------+------------------+
| Ubuntu 24.04 | FAIL | SKIPPED | SKIPPED |
+---------------------+--------------------+----------------------+------------------+
| Debian Bullseye | PASS | SKIPPED | PASS |
+---------------------+--------------------+----------------------+------------------+
| CentOS Stream 9 | PASS | SKIPPED | PASS |
+---------------------+--------------------+----------------------+------------------+
| RHEL8 | PASS | SKIPPED | PASS |
+---------------------+--------------------+----------------------+------------------+
==== 20 line log output for Ubuntu 24.04 (dpdk_meson_compile): ====
--- Failed to get log output ---
==== End log output ====
FreeBSD 13.3
Kernel: 13.3-RELEASE-p1
Compiler: clang 17.0.6
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
FreeBSD 14.0
Kernel: 14.0
Compiler: clang 16.0.6
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
Ubuntu 24.04
Kernel: 5.4.0-167-generic
Compiler: gcc 13.2.0
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
RHEL8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30045/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-05-30 7:24 UTC|newest]
Thread overview: 158+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240530034252.198797-1-gavinl@nvidia.com>
2024-05-30 3:16 ` |SUCCESS| pw140429 [PATCH] net/mlx5: fix flow discover IPv6 traffic class support issue qemudev
2024-05-30 3:21 ` qemudev
2024-05-30 3:44 ` checkpatch
2024-05-30 4:44 ` 0-day Robot
2024-05-30 6:21 ` |SUCCESS| pw140429 [PATCH] net/mlx5: fix flow discover IPv6 traffic dpdklab
2024-05-30 6:23 ` dpdklab
2024-05-30 6:23 ` dpdklab
2024-05-30 6:24 ` dpdklab
2024-05-30 6:27 ` dpdklab
2024-05-30 6:28 ` dpdklab
2024-05-30 6:28 ` dpdklab
2024-05-30 6:29 ` dpdklab
2024-05-30 6:30 ` dpdklab
2024-05-30 6:30 ` dpdklab
2024-05-30 6:31 ` dpdklab
2024-05-30 6:32 ` dpdklab
2024-05-30 6:33 ` dpdklab
2024-05-30 6:34 ` dpdklab
2024-05-30 6:42 ` dpdklab
2024-05-30 7:09 ` dpdklab
2024-05-30 7:12 ` dpdklab
2024-05-30 7:17 ` dpdklab
2024-05-30 7:19 ` dpdklab
2024-05-30 7:21 ` dpdklab
2024-05-30 7:22 ` |FAILURE| " dpdklab
2024-05-30 7:24 ` dpdklab [this message]
2024-05-30 7:26 ` |SUCCESS| " dpdklab
2024-05-30 7:27 ` dpdklab
2024-05-30 7:27 ` |FAILURE| " dpdklab
2024-05-30 7:27 ` |SUCCESS| " dpdklab
2024-05-30 7:28 ` dpdklab
2024-05-30 7:30 ` dpdklab
2024-05-30 7:35 ` dpdklab
2024-05-30 7:36 ` dpdklab
2024-05-30 7:37 ` dpdklab
2024-05-30 7:42 ` dpdklab
2024-05-30 7:44 ` dpdklab
2024-05-30 7:47 ` dpdklab
2024-05-30 7:51 ` dpdklab
2024-05-30 7:51 ` dpdklab
2024-05-30 7:53 ` dpdklab
2024-05-30 7:53 ` dpdklab
2024-05-30 7:56 ` |FAILURE| " dpdklab
2024-05-30 7:56 ` |SUCCESS| " dpdklab
2024-05-30 7:58 ` dpdklab
2024-05-30 8:00 ` dpdklab
2024-05-30 8:03 ` dpdklab
2024-05-30 8:04 ` dpdklab
2024-05-30 8:06 ` dpdklab
2024-05-30 8:07 ` dpdklab
2024-05-30 8:07 ` dpdklab
2024-05-30 8:12 ` dpdklab
2024-05-30 8:23 ` dpdklab
2024-05-30 8:23 ` dpdklab
2024-05-30 8:24 ` dpdklab
2024-05-30 8:26 ` dpdklab
2024-05-30 8:29 ` dpdklab
2024-05-30 8:30 ` |FAILURE| " dpdklab
2024-05-30 8:31 ` |SUCCESS| " dpdklab
2024-05-30 8:49 ` |FAILURE| " dpdklab
2024-05-30 9:24 ` |SUCCESS| " dpdklab
2024-05-30 9:31 ` dpdklab
2024-05-30 17:32 ` dpdklab
2024-05-30 17:32 ` dpdklab
2024-05-30 17:54 ` dpdklab
2024-05-30 17:54 ` dpdklab
2024-05-30 18:09 ` dpdklab
2024-06-01 6:11 ` dpdklab
2024-06-01 6:11 ` dpdklab
2024-06-01 6:36 ` dpdklab
2024-06-01 6:44 ` dpdklab
2024-06-01 6:58 ` dpdklab
2024-06-01 9:25 ` dpdklab
2024-06-01 9:28 ` dpdklab
2024-06-01 9:39 ` dpdklab
2024-06-01 9:43 ` dpdklab
2024-06-01 9:43 ` dpdklab
2024-06-01 10:02 ` dpdklab
2024-06-01 10:08 ` dpdklab
2024-06-01 10:09 ` dpdklab
2024-06-01 10:09 ` dpdklab
2024-06-01 10:09 ` dpdklab
2024-06-01 10:11 ` dpdklab
2024-06-01 10:13 ` dpdklab
2024-06-01 10:16 ` dpdklab
2024-06-01 11:15 ` dpdklab
2024-06-01 11:16 ` dpdklab
2024-06-01 11:16 ` dpdklab
2024-06-01 11:17 ` dpdklab
2024-06-01 11:40 ` dpdklab
2024-06-01 11:54 ` dpdklab
2024-06-01 12:06 ` dpdklab
2024-06-01 12:09 ` dpdklab
2024-06-01 12:11 ` dpdklab
2024-06-01 12:11 ` dpdklab
2024-06-01 12:12 ` dpdklab
2024-06-01 12:17 ` dpdklab
2024-06-01 13:36 ` dpdklab
2024-06-01 13:40 ` |FAILURE| " dpdklab
2024-06-01 13:41 ` dpdklab
2024-06-01 13:42 ` dpdklab
2024-06-01 13:43 ` dpdklab
2024-06-01 13:44 ` dpdklab
2024-06-01 13:47 ` dpdklab
2024-06-01 13:47 ` dpdklab
2024-06-01 13:48 ` dpdklab
2024-06-01 13:50 ` dpdklab
2024-06-01 13:51 ` dpdklab
2024-06-01 13:52 ` dpdklab
2024-06-01 13:54 ` dpdklab
2024-06-01 13:54 ` dpdklab
2024-06-01 13:57 ` dpdklab
2024-06-01 13:58 ` dpdklab
2024-06-01 13:58 ` dpdklab
2024-06-01 13:59 ` dpdklab
2024-06-01 13:59 ` dpdklab
2024-06-01 14:00 ` dpdklab
2024-06-01 14:02 ` dpdklab
2024-06-01 14:02 ` dpdklab
2024-06-01 14:04 ` dpdklab
2024-06-01 14:09 ` dpdklab
2024-06-01 14:09 ` dpdklab
2024-06-01 14:15 ` dpdklab
2024-06-01 14:15 ` dpdklab
2024-06-01 14:15 ` dpdklab
2024-06-01 14:16 ` |SUCCESS| " dpdklab
2024-06-01 14:16 ` dpdklab
2024-06-01 14:16 ` |FAILURE| " dpdklab
2024-06-01 14:18 ` dpdklab
2024-06-01 14:19 ` |SUCCESS| " dpdklab
2024-06-01 14:20 ` |FAILURE| " dpdklab
2024-06-01 14:22 ` dpdklab
2024-06-01 14:22 ` dpdklab
2024-06-01 14:24 ` dpdklab
2024-06-01 14:28 ` dpdklab
2024-06-01 14:31 ` dpdklab
2024-06-01 14:31 ` |SUCCESS| " dpdklab
2024-06-01 14:33 ` |FAILURE| " dpdklab
2024-06-01 14:35 ` dpdklab
2024-06-01 14:35 ` dpdklab
2024-06-01 14:37 ` dpdklab
2024-06-01 14:41 ` dpdklab
2024-06-01 14:43 ` dpdklab
2024-06-01 14:45 ` dpdklab
2024-06-01 14:46 ` dpdklab
2024-06-01 14:52 ` dpdklab
2024-06-01 14:53 ` dpdklab
2024-06-01 14:56 ` dpdklab
2024-06-01 14:57 ` dpdklab
2024-06-01 14:58 ` dpdklab
2024-06-01 15:06 ` dpdklab
2024-06-01 15:07 ` dpdklab
2024-06-01 15:07 ` dpdklab
2024-06-01 15:14 ` dpdklab
2024-06-01 15:23 ` dpdklab
2024-06-01 19:47 ` dpdklab
2024-06-01 20:02 ` dpdklab
2024-06-02 0:06 ` |SUCCESS| " 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=6658299d.050a0220.45941.c1dbSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=gavinl@nvidia.com \
--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).