automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw148421-148423 [PATCH] [v5,3/3] dts: add l2fwd test suite
Date: Wed, 13 Nov 2024 17:16:29 -0800 (PST)	[thread overview]
Message-ID: <67354f6d.050a0220.1b6c63.0246SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241113163128.645878-4-luca.vizzarro@arm.com>

Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/148423

_Testing PASS_

Submitter: Luca Vizzarro <luca.vizzarro@arm.com>
Date: Wednesday, November 13 2024 16:31:28 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:78383e9816a8efe2ba16ec2ce65d51b94e6114e7

148421-148423 --> testing pass

Upstream job id: Generic-Unit-Test-DPDK#291173

Test environment and result as below:

+----------------------+------------------------------+--------------+---------------------------+
|     Environment      | cryptodev_sw_snow3g_autotest | lpm_autotest | cryptodev_sw_zuc_autotest |
+======================+==============================+==============+===========================+
| Debian 12 (arm)      | PASS                         | SKIPPED      | PASS                      |
+----------------------+------------------------------+--------------+---------------------------+
| Ubuntu 20.04 ARM SVE | SKIPPED                      | PASS         | SKIPPED                   |
+----------------------+------------------------------+--------------+---------------------------+


Debian 12 (arm)
	Kernel: Depends on container host
	Compiler: gcc (Debian 12.2.0-14) 12.2.0

Ubuntu 20.04 ARM SVE
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31917/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2024-11-14  1:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241113163128.645878-4-luca.vizzarro@arm.com>
2024-11-13 16:02 ` |SUCCESS| pw148421-148423 [PATCH v5 3/3] " qemudev
2024-11-13 16:06 ` qemudev
2024-11-13 16:32 ` |WARNING| pw148423 " checkpatch
2024-11-13 17:45 ` |SUCCESS| " 0-day Robot
2024-11-13 22:34 ` |SUCCESS| pw148421-148423 [PATCH] [v5,3/3] " dpdklab
2024-11-13 23:10 ` dpdklab
2024-11-14  0:01 ` dpdklab
2024-11-14  0:31 ` dpdklab
2024-11-14  0:49 ` dpdklab
2024-11-14  0:49 ` |PENDING| " dpdklab
2024-11-14  1:16 ` dpdklab [this message]
2024-11-14  1:35 ` |SUCCESS| " dpdklab
2024-11-14  1:47 ` |WARNING| " dpdklab
2024-11-14  2:11 ` |PENDING| " dpdklab
2024-11-14  2:11 ` |SUCCESS| " dpdklab
2024-11-14  2:28 ` dpdklab
2024-11-14  2:30 ` |WARNING| " dpdklab
2024-11-14  3:30 ` dpdklab
2024-11-14  3:32 ` dpdklab
2024-11-14  5:14 ` |SUCCESS| " dpdklab
2024-11-14  5:25 ` dpdklab
2024-11-14  9:05 ` dpdklab
2024-11-14  9:48 ` 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=67354f6d.050a0220.1b6c63.0246SMTPIN_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).