From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw148214-148216 [PATCH] [v3,3/3] dts: add l2fwd test suite
Date: Fri, 08 Nov 2024 13:12:44 -0800 (PST) [thread overview]
Message-ID: <672e7ecc.050a0220.15ad2c.ce37SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241108170138.203096-4-luca.vizzarro@arm.com>
Test-Label: iol-unit-arm64-testing
Test-Status: PENDING
http://dpdk.org/patch/148216
_Testing pending_
Submitter: Luca Vizzarro <luca.vizzarro@arm.com>
Date: Friday, November 08 2024 17:01:38
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:84c91d93da7a0e537f95cf17dde026564f35a3b7
148214-148216 --> testing pending
Upstream job id: Generic-Unit-Test-DPDK#289670
Test environment and result as below:
+----------------------+--------------+---------------------------+------------------------------+
| Environment | lpm_autotest | cryptodev_sw_zuc_autotest | cryptodev_sw_snow3g_autotest |
+======================+==============+===========================+==============================+
| Ubuntu 20.04 ARM SVE | PEND | SKIPPED | SKIPPED |
+----------------------+--------------+---------------------------+------------------------------+
| Debian 12 (arm) | SKIPPED | PASS | PEND |
+----------------------+--------------+---------------------------+------------------------------+
Ubuntu 20.04 ARM SVE
Kernel: Depends on container host
Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0
Debian 12 (arm)
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31867/
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-11-08 21:12 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241108170138.203096-4-luca.vizzarro@arm.com>
2024-11-08 16:31 ` |SUCCESS| pw148214-148216 [PATCH v3 3/3] " qemudev
2024-11-08 16:36 ` qemudev
2024-11-08 17:03 ` |WARNING| pw148216 " checkpatch
2024-11-08 18:02 ` |SUCCESS| " 0-day Robot
2024-11-08 19:55 ` |SUCCESS| pw148214-148216 [PATCH] [v3,3/3] " dpdklab
2024-11-08 19:57 ` dpdklab
2024-11-08 20:02 ` dpdklab
2024-11-08 20:06 ` dpdklab
2024-11-08 20:14 ` dpdklab
2024-11-08 20:22 ` dpdklab
2024-11-08 20:33 ` dpdklab
2024-11-08 20:47 ` dpdklab
2024-11-08 21:08 ` |PENDING| " dpdklab
2024-11-08 21:12 ` dpdklab [this message]
2024-11-08 21:29 ` |SUCCESS| " dpdklab
2024-11-08 21:29 ` dpdklab
2024-11-08 21:30 ` dpdklab
2024-11-08 21:38 ` |PENDING| " dpdklab
2024-11-08 22:01 ` |SUCCESS| " dpdklab
2024-11-08 22:05 ` |PENDING| " dpdklab
2024-11-08 22:09 ` |SUCCESS| " dpdklab
2024-11-08 22:17 ` |PENDING| " dpdklab
2024-11-08 22:19 ` |SUCCESS| " dpdklab
2024-11-08 22:37 ` dpdklab
2024-11-08 22:46 ` dpdklab
2024-11-08 22:49 ` dpdklab
2024-11-08 22:49 ` dpdklab
2024-11-08 23:00 ` dpdklab
2024-11-08 23:10 ` dpdklab
2024-11-08 23:13 ` dpdklab
2024-11-08 23:38 ` dpdklab
2024-11-08 23:39 ` dpdklab
2024-11-08 23:45 ` dpdklab
2024-11-08 23:57 ` dpdklab
2024-11-08 23:58 ` dpdklab
2024-11-09 0:02 ` dpdklab
2024-11-09 0:04 ` dpdklab
2024-11-09 0:07 ` dpdklab
2024-11-09 0:08 ` dpdklab
2024-11-09 0:14 ` dpdklab
2024-11-09 0:19 ` dpdklab
2024-11-09 0:31 ` dpdklab
2024-11-09 0:39 ` dpdklab
2024-11-09 0:41 ` 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=672e7ecc.050a0220.15ad2c.ce37SMTPIN_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).