From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138455-138457 [PATCH] [v2,3/3] dts: store stderr in Remo
Date: Mon, 18 Mar 2024 10:51:58 -0700 (PDT) [thread overview]
Message-ID: <65f87f3e.050a0220.1e413.a713SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240318171704.798634-4-luca.vizzarro@arm.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138457
_Functional Testing PASS_
Submitter: Luca Vizzarro <luca.vizzarro@arm.com>
Date: Monday, March 18 2024 17:17:04
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2
138455-138457 --> 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: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29583/
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-18 17:52 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240318171704.798634-4-luca.vizzarro@arm.com>
2024-03-18 16:55 ` |SUCCESS| pw138455-138457 [PATCH v2 3/3] dts: store stderr in RemoteCommandExecutionError qemudev
2024-03-18 16:59 ` qemudev
2024-03-18 17:19 ` |SUCCESS| pw138457 " checkpatch
2024-03-18 17:51 ` |SUCCESS| pw138455-138457 [PATCH] [v2,3/3] dts: store stderr in Remo dpdklab
2024-03-18 17:51 ` dpdklab
2024-03-18 17:51 ` dpdklab
2024-03-18 17:51 ` dpdklab [this message]
2024-03-18 17:52 ` dpdklab
2024-03-18 17:52 ` dpdklab
2024-03-18 17:52 ` dpdklab
2024-03-18 17:53 ` dpdklab
2024-03-18 17:54 ` dpdklab
2024-03-18 17:54 ` dpdklab
2024-03-18 17:54 ` dpdklab
2024-03-18 17:55 ` dpdklab
2024-03-18 17:55 ` dpdklab
2024-03-18 17:55 ` dpdklab
2024-03-18 17:55 ` dpdklab
2024-03-18 17:56 ` dpdklab
2024-03-18 17:56 ` dpdklab
2024-03-18 17:56 ` dpdklab
2024-03-18 17:57 ` dpdklab
2024-03-18 17:57 ` dpdklab
2024-03-18 17:58 ` dpdklab
2024-03-18 17:58 ` dpdklab
2024-03-18 17:59 ` dpdklab
2024-03-18 17:59 ` dpdklab
2024-03-18 17:59 ` dpdklab
2024-03-18 17:59 ` dpdklab
2024-03-18 18:00 ` dpdklab
2024-03-18 18:00 ` dpdklab
2024-03-18 18:01 ` dpdklab
2024-03-18 18:03 ` |SUCCESS| pw138457 [PATCH v2 3/3] dts: store stderr in RemoteCommandExecutionError 0-day Robot
2024-03-18 18:04 ` |SUCCESS| pw138455-138457 [PATCH] [v2,3/3] dts: store stderr in Remo dpdklab
2024-03-18 18:04 ` dpdklab
2024-03-18 18:05 ` dpdklab
2024-03-18 18:06 ` dpdklab
2024-03-18 18:06 ` dpdklab
2024-03-18 18:06 ` dpdklab
2024-03-18 18:07 ` dpdklab
2024-03-18 18:07 ` dpdklab
2024-03-18 18:07 ` dpdklab
2024-03-18 18:07 ` dpdklab
2024-03-18 18:08 ` dpdklab
2024-03-18 18:08 ` dpdklab
2024-03-18 18:09 ` dpdklab
2024-03-18 18:09 ` dpdklab
2024-03-18 18:10 ` dpdklab
2024-03-18 18:10 ` dpdklab
2024-03-18 18:10 ` dpdklab
2024-03-18 18:11 ` dpdklab
2024-03-18 18:11 ` dpdklab
2024-03-18 18:12 ` dpdklab
2024-03-18 18:12 ` dpdklab
2024-03-18 18:12 ` dpdklab
2024-03-18 18:13 ` dpdklab
2024-03-18 18:13 ` dpdklab
2024-03-18 18:14 ` dpdklab
2024-03-18 18:15 ` dpdklab
2024-03-18 18:16 ` dpdklab
2024-03-18 18:16 ` dpdklab
2024-03-18 18:22 ` dpdklab
2024-03-18 18:23 ` dpdklab
2024-03-18 18:24 ` dpdklab
2024-03-18 18:24 ` dpdklab
2024-03-18 18:24 ` dpdklab
2024-03-18 18:24 ` dpdklab
2024-03-18 18:24 ` dpdklab
2024-03-18 18:27 ` dpdklab
2024-03-18 18:27 ` dpdklab
2024-03-18 18:27 ` dpdklab
2024-03-18 18:29 ` dpdklab
2024-03-18 18:30 ` dpdklab
2024-03-18 18:33 ` dpdklab
2024-03-18 19:15 ` dpdklab
2024-03-18 20:50 ` dpdklab
2024-03-18 21:26 ` dpdklab
2024-03-20 15:50 ` dpdklab
2024-03-20 16:22 ` 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=65f87f3e.050a0220.1e413.a713SMTPIN_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).