From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133435 [PATCH] testpmd: fix early exit from signal
Date: Thu, 26 Oct 2023 13:08:47 -0700 (PDT) [thread overview]
Message-ID: <653ac74f.250a0220.6f1bb.04b0SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/133435
_Functional Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, October 26 2023 17:11:33
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2a0557d1ea21c3f63a212385348c97c414970e81
133435 --> functional testing pass
Test environment and result as below:
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28098/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-26 20:08 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 20:08 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-28 12:26 dpdklab
2023-10-27 3:40 dpdklab
2023-10-27 3:34 dpdklab
2023-10-27 3:21 dpdklab
2023-10-26 22:11 dpdklab
2023-10-26 21:48 dpdklab
2023-10-26 21:47 dpdklab
2023-10-26 21:20 dpdklab
2023-10-26 20:54 dpdklab
2023-10-26 20:51 dpdklab
2023-10-26 20:51 dpdklab
2023-10-26 20:50 dpdklab
2023-10-26 20:50 dpdklab
2023-10-26 20:49 dpdklab
2023-10-26 20:49 dpdklab
2023-10-26 20:48 dpdklab
2023-10-26 20:48 dpdklab
2023-10-26 20:48 dpdklab
2023-10-26 20:48 dpdklab
2023-10-26 20:47 dpdklab
2023-10-26 20:47 dpdklab
2023-10-26 20:46 dpdklab
2023-10-26 20:45 dpdklab
2023-10-26 20:44 dpdklab
2023-10-26 20:43 dpdklab
2023-10-26 20:43 dpdklab
2023-10-26 20:42 dpdklab
2023-10-26 20:42 dpdklab
2023-10-26 20:42 dpdklab
2023-10-26 20:41 dpdklab
2023-10-26 20:41 dpdklab
2023-10-26 20:41 dpdklab
2023-10-26 20:41 dpdklab
2023-10-26 20:41 dpdklab
2023-10-26 20:36 dpdklab
2023-10-26 20:29 dpdklab
2023-10-26 20:29 dpdklab
2023-10-26 20:28 dpdklab
2023-10-26 20:28 dpdklab
2023-10-26 20:27 dpdklab
2023-10-26 20:27 dpdklab
2023-10-26 20:27 dpdklab
2023-10-26 20:27 dpdklab
2023-10-26 20:26 dpdklab
2023-10-26 20:26 dpdklab
2023-10-26 20:25 dpdklab
2023-10-26 20:23 dpdklab
2023-10-26 20:18 dpdklab
2023-10-26 19:58 dpdklab
2023-10-26 19:57 dpdklab
2023-10-26 19:54 dpdklab
[not found] <20231026171133.250715-1-stephen@networkplumber.org>
2023-10-26 16:56 ` qemudev
2023-10-26 17:00 ` qemudev
2023-10-26 17:11 ` checkpatch
2023-10-26 18:19 ` 0-day Robot
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=653ac74f.250a0220.6f1bb.04b0SMTPIN_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).