From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw149776-149777 [PATCH] [v4,2/2] dts: add dual VLAN test s
Date: Thu, 09 Jan 2025 12:09:52 -0800 (PST) [thread overview]
Message-ID: <67802d10.050a0220.24f2cc.7877SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250109180124.1678253-2-paul.szczepanek@arm.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/149777
_Functional Testing PASS_
Submitter: Paul Szczepanek <paul.szczepanek@arm.com>
Date: Thursday, January 09 2025 18:01:24
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fd51012de5369679e807be1d6a81d63ef15015ce
149776-149777 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#206126
Test environment and result as below:
Arm Ampere Altra - Ubuntu 22.04
Kernel: 5.15.83+
Compiler: gcc 11.4
NIC: Intel Corporation QAT 8970 0 Mbps
Aggregate Results by Test Suite
+----------------------------+--------+
| Test Suite | Result |
+============================+========+
| crypto_perf_cryptodev_perf | PASS |
+----------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32286/
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:[~2025-01-09 20:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250109180124.1678253-2-paul.szczepanek@arm.com>
2025-01-09 17:31 ` |SUCCESS| pw149776-149777 [PATCH v4 2/2] dts: add dual VLAN test suite qemudev
2025-01-09 17:35 ` qemudev
2025-01-09 18:02 ` |SUCCESS| pw149777 " checkpatch
2025-01-09 19:15 ` 0-day Robot
2025-01-09 19:42 ` |SUCCESS| pw149776-149777 [PATCH] [v4,2/2] dts: add dual VLAN test s dpdklab
2025-01-09 19:43 ` dpdklab
2025-01-09 19:45 ` dpdklab
2025-01-09 19:56 ` dpdklab
2025-01-09 19:56 ` |PENDING| " dpdklab
2025-01-09 20:08 ` |SUCCESS| " dpdklab
2025-01-09 20:09 ` dpdklab [this message]
2025-01-09 20:14 ` dpdklab
2025-01-09 20:15 ` dpdklab
2025-01-09 20:17 ` dpdklab
2025-01-09 20:18 ` |PENDING| " dpdklab
2025-01-09 20:18 ` dpdklab
2025-01-09 20:53 ` |SUCCESS| " dpdklab
2025-01-09 21:01 ` |PENDING| " dpdklab
2025-01-09 21:02 ` |SUCCESS| " dpdklab
2025-01-09 21:24 ` dpdklab
2025-01-09 22:10 ` |WARNING| " dpdklab
2025-01-09 22:32 ` |SUCCESS| " dpdklab
2025-01-09 23:23 ` dpdklab
2025-01-09 23:35 ` dpdklab
2025-01-10 7:11 ` 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=67802d10.050a0220.24f2cc.7877SMTPIN_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).