From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136955-136956 [PATCH] [v2,2/2] net/mlx5: add cross port
Date: Wed, 21 Feb 2024 11:03:56 -0800 (PST) [thread overview]
Message-ID: <65d6491c.b00a0220.a2e03.4e35SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136956
_Testing PASS_
Submitter: Dariusz Sosnowski <dsosnowski@nvidia.com>
Date: Wednesday, February 21 2024 10:21:30
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:ee45c93a16dd5e11b7779f18db9173fd8de8df74
136955-136956 --> testing pass
Test environment and result as below:
+------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+====================================+====================+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+------------------------------------+--------------------+
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29210/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-21 19:04 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 19:03 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-23 5:33 dpdklab
2024-02-23 5:25 dpdklab
2024-02-21 22:16 dpdklab
2024-02-21 22:00 dpdklab
2024-02-21 21:43 dpdklab
2024-02-21 21:35 dpdklab
2024-02-21 21:17 dpdklab
2024-02-21 21:14 dpdklab
2024-02-21 21:14 dpdklab
2024-02-21 21:13 dpdklab
2024-02-21 21:07 dpdklab
2024-02-21 21:01 dpdklab
2024-02-21 20:49 dpdklab
2024-02-21 20:43 dpdklab
2024-02-21 20:04 dpdklab
2024-02-21 20:04 dpdklab
2024-02-21 19:57 dpdklab
2024-02-21 19:49 dpdklab
2024-02-21 19:35 dpdklab
2024-02-21 19:30 dpdklab
2024-02-21 19:28 dpdklab
2024-02-21 19:20 dpdklab
2024-02-21 19:07 dpdklab
2024-02-21 19:03 dpdklab
2024-02-21 19:01 dpdklab
2024-02-21 19:01 dpdklab
2024-02-21 19:00 dpdklab
2024-02-21 18:59 dpdklab
2024-02-21 18:58 dpdklab
2024-02-21 18:56 dpdklab
2024-02-21 18:56 dpdklab
2024-02-21 18:54 dpdklab
2024-02-21 18:53 dpdklab
2024-02-21 18:52 dpdklab
2024-02-21 18:52 dpdklab
2024-02-21 18:51 dpdklab
2024-02-21 18:50 dpdklab
2024-02-21 18:48 dpdklab
2024-02-21 18:46 dpdklab
2024-02-21 18:45 dpdklab
2024-02-21 18:44 dpdklab
2024-02-21 18:42 dpdklab
2024-02-21 18:41 dpdklab
2024-02-21 18:40 dpdklab
2024-02-21 18:39 dpdklab
2024-02-21 18:36 dpdklab
2024-02-21 18:29 dpdklab
2024-02-21 18:28 dpdklab
2024-02-21 18:27 dpdklab
2024-02-21 18:25 dpdklab
2024-02-21 18:22 dpdklab
2024-02-21 18:22 dpdklab
2024-02-21 18:21 dpdklab
2024-02-21 18:20 dpdklab
2024-02-21 18:20 dpdklab
2024-02-21 18:18 dpdklab
2024-02-21 18:13 dpdklab
2024-02-21 18:08 dpdklab
2024-02-21 18:06 dpdklab
2024-02-21 18:03 dpdklab
2024-02-21 18:00 dpdklab
2024-02-21 17:59 dpdklab
2024-02-21 17:57 dpdklab
2024-02-21 17:56 dpdklab
2024-02-21 17:55 dpdklab
2024-02-21 17:54 dpdklab
2024-02-21 17:53 dpdklab
2024-02-21 17:51 dpdklab
2024-02-21 17:51 dpdklab
2024-02-21 17:51 dpdklab
2024-02-21 17:51 dpdklab
2024-02-21 17:47 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=65d6491c.b00a0220.a2e03.4e35SMTPIN_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).