From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137646 [PATCH] app/dumpcap:fix coredump problem because
Date: Fri, 01 Mar 2024 00:14:42 -0800 (PST) [thread overview]
Message-ID: <65e18e72.170a0220.1d1cc.49c5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240301104129.3725-1-laitianli@tom.com>
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137646
_Testing PASS_
Submitter: Tianli Lai <laitianli@tom.com>
Date: Friday, March 01 2024 10:41:29
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137646 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
| Fedora 37 (ARM) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 (ARM) | PASS |
+----------------------------------------+--------------------+
| Debian 12 (arm) | PASS |
+----------------------------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+----------------------------------------+--------------------+
| Debian 11 (Buster) (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM Clang) | PASS |
+----------------------------------------+--------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang version 10.0.0-4ubuntu1
Fedora 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
Fedora 38 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 16.0.3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29355/
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-03-01 8:14 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240301104129.3725-1-laitianli@tom.com>
2024-03-01 2:19 ` |SUCCESS| pw137646 [PATCH] app/dumpcap:fix coredump problem because pcap_dump 3th argument is null qemudev
2024-03-01 2:24 ` qemudev
2024-03-01 2:42 ` checkpatch
2024-03-01 3:45 ` 0-day Robot
2024-03-01 4:17 ` |SUCCESS| pw137646 [PATCH] app/dumpcap:fix coredump problem because dpdklab
2024-03-01 4:20 ` dpdklab
2024-03-01 4:20 ` dpdklab
2024-03-01 4:21 ` dpdklab
2024-03-01 4:31 ` dpdklab
2024-03-01 4:33 ` dpdklab
2024-03-01 4:34 ` dpdklab
2024-03-01 4:35 ` dpdklab
2024-03-01 4:36 ` dpdklab
2024-03-01 4:36 ` dpdklab
2024-03-01 4:37 ` dpdklab
2024-03-01 4:47 ` dpdklab
2024-03-01 4:47 ` dpdklab
2024-03-01 4:47 ` dpdklab
2024-03-01 4:48 ` dpdklab
2024-03-01 4:50 ` dpdklab
2024-03-01 4:50 ` dpdklab
2024-03-01 5:33 ` dpdklab
2024-03-01 5:33 ` dpdklab
2024-03-01 5:34 ` dpdklab
2024-03-01 5:34 ` dpdklab
2024-03-01 5:34 ` dpdklab
2024-03-01 5:35 ` dpdklab
2024-03-01 5:35 ` dpdklab
2024-03-01 5:35 ` dpdklab
2024-03-01 5:35 ` dpdklab
2024-03-01 5:35 ` dpdklab
2024-03-01 5:36 ` dpdklab
2024-03-01 5:36 ` dpdklab
2024-03-01 5:36 ` dpdklab
2024-03-01 5:36 ` dpdklab
2024-03-01 5:37 ` dpdklab
2024-03-01 5:37 ` dpdklab
2024-03-01 5:37 ` dpdklab
2024-03-01 5:37 ` dpdklab
2024-03-01 5:37 ` dpdklab
2024-03-01 5:38 ` dpdklab
2024-03-01 5:38 ` dpdklab
2024-03-01 5:38 ` dpdklab
2024-03-01 5:39 ` dpdklab
2024-03-01 5:39 ` dpdklab
2024-03-01 5:40 ` dpdklab
2024-03-01 5:40 ` dpdklab
2024-03-01 5:40 ` dpdklab
2024-03-01 5:40 ` dpdklab
2024-03-01 5:40 ` dpdklab
2024-03-01 5:41 ` dpdklab
2024-03-01 5:42 ` dpdklab
2024-03-01 5:42 ` dpdklab
2024-03-01 5:42 ` dpdklab
2024-03-01 5:42 ` dpdklab
2024-03-01 5:43 ` dpdklab
2024-03-01 5:43 ` dpdklab
2024-03-01 5:44 ` dpdklab
2024-03-01 5:44 ` dpdklab
2024-03-01 5:58 ` dpdklab
2024-03-01 5:58 ` dpdklab
2024-03-01 6:02 ` dpdklab
2024-03-01 6:15 ` dpdklab
2024-03-01 6:49 ` dpdklab
2024-03-01 8:14 ` dpdklab [this message]
2024-03-01 9:56 ` dpdklab
2024-03-01 16:01 ` dpdklab
2024-03-01 16:06 ` dpdklab
2024-03-01 16:08 ` dpdklab
2024-03-01 16:13 ` dpdklab
2024-03-02 4:18 ` dpdklab
2024-03-02 4:27 ` dpdklab
2024-03-02 15:40 ` dpdklab
2024-03-02 18:25 ` dpdklab
2024-03-02 18:33 ` dpdklab
2024-03-04 14:59 ` dpdklab
2024-03-04 15:31 ` dpdklab
2024-03-04 18:05 ` 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=65e18e72.170a0220.1d1cc.49c5SMTPIN_ADDED_MISSING@mx.google.com \
--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).